In this presentation Uma Chunduri talks about evolving 5G deployments in operator networks, in Multi-access Edge Clouds (MECs) as well as on-prem edges from requirements to network challenges. He talks about the ubiquitous and intelligent computing demands and usage of IPv6 in these deployments. He also talks about some of the unaddressed challenges in the network layer.
About Uma: Uma S. Chunduri is a 5G NW Architect at Next Generation and Standards Group, Intel and working on MEC NW architecture, intelligent compute scaling, edge strategy and solutions.
Uma is an IP routing and wireless expert with 20+ years of R&D background and expertise in SPs, CoSPs and Cloud networks. He previously worked at Futurewei (Huawei USA) as a Distinguished Engineer & Sr. Director of Technology at Future Networks CTO office providing solutions to enable various industry verticals with deterministic network services, 5G/B5G transport NW strategy and technology research & standardization. He is a technology contributor at ETSI, ITU-T FG2030 and at IETF with 10+ published RFCs and numerous Internet Drafts, as well as secured 50+ patents in his career. Uma was also with Intoto/Freescale Semiconductors, Kineto Wireless and was a Principal Systems Engineer at Ericsson R&D, USA. Uma is based in Santa Clara, California.
Concerned about adding a new protocol to your IP stack? Is someone in your company demanding that you have that capability on your mainframe? Don’t know what needs to be done and how much effort is involved? And what does it all mean?
Rob has done the hard work for you and can tell you what it takes to enable your mainframe systems for IPv6. This presentation will give you the few steps you need to get you going, to get IPv6 active on your z/OS system.
Rob started programming mainframe computers in 1971, and learned an exceptional array of languages, tools and techniques, all without internet assistance. He did some dazzling database work in the `80s, and wrote over half of the first online registration system for the University of Toledo. In the ‘90s he did contracts with three oil companies, a software company and a credit bureau, involving VM, MVS, VSE, OS/2, several flavors of Unix, and an equal variety of networking protocols. He is now with Chemical Abstracts Service, a division of the American Chemical Society, supporting z/OS, z/VM and Linux, along with proprietary networking software. He has been involved with and a fan of IPv6 since early this century, performing the configuration and software upgrades required to support it on the mainframe. He happily notes that the mainframe was the first platform configured for it, with applications using IPv6 sockets exclusively. Rob is also co-author of RFC8250.
Concerned about adding a new protocol to your IP stack? Is someone in your company demanding that you have that capability on your mainframe? Don’t know what needs to be done and how much effort is involved? And what does it all mean?
Rob has done the hard work for you and can tell you what it takes to enable your mainframe systems for IPv6. This presentation will give you the few steps you need to get you going, to get IPv6 active on your z/OS system.
Rob started programming mainframe computers in 1971, and learned an exceptional array of languages, tools and techniques, all without internet assistance. He did some dazzling database work in the `80s, and wrote over half of the first online registration system for the University of Toledo. In the ‘90s he did contracts with three oil companies, a software company and a credit bureau, involving VM, MVS, VSE, OS/2, several flavors of Unix, and an equal variety of networking protocols. He is now with Chemical Abstracts Service, a division of the American Chemical Society, supporting z/OS, z/VM and Linux, along with proprietary networking software. He has been involved with and a fan of IPv6 since early this century, performing the configuration and software upgrades required to support it on the mainframe. He happily notes that the mainframe was the first platform configured for it, with applications using IPv6 sockets exclusively. Rob is also co-author of RFC8250.
The IPv6 Trace Reading and Troubleshooting sessions cover the following:
- Introduction to Trace Reading
- IPv4 address structure
- IPv6 address structure
- IPv6 extension headers
- Security issues (header)
- Malformed packets
- Routing header
- Analyzing traces via Wireshark
Presented by Nalini Elkins & Michael Ackermann.
The IPv6 Trace Reading and Troubleshooting sessions cover the following:
- Introduction to Trace Reading
- IPv4 address structure
- IPv6 address structure
- IPv6 extension headers
- Security issues (header)
- Malformed packets
- Routing header
- Analyzing traces via Wireshark
Presented by Nalini Elkins & Michael Ackermann.
This session discusses the ways enterprises might want to think about migration to IPv6. Some vulnerabilities may be the same as IPv4 while other will be different. Vulnerabilities may be introduced by additional complexity, for example, transition mechanisms or dual-stacking.When many enterprises think about security, a number of areas are involved. These include:
- Audits/Compliance
- Threat detection
- Risk analysis
- Root cause determination
- Encryption
- Privacy
- Confidentiality
- Penetration testing
Presented by Nalini Elkins.
The agenda topics for these classes include:
- IPv4 address depletion status
- Will cloud providers charge for IPv4?
- AUnique Local Addresses (ULA)
- Can / should ULA be used in Cloud?
- Oracle cloud IPv6 addressing lab
- AWS cloud IPv6 addressing lab
Nalini Elkins, Shahreen Fredrich, Ajay Chhabria, Priyanka Sinha, Lee Howard & Mohit P. Tahiliani
Part 1 is not available.
The agenda topics for this class include:
- DHCPv6 Modes
- DHCPv6 Relay
- Address Allocation
- Basic commands: Client
- Basic commands: Server / Relay
- Prefix ‘Hints’
Nalini Elkins & Mohit P. Tahiliani
The agenda topics for this class include:
- DHCPv6 Modes
- DHCPv6 Relay
- Address Allocation
- Basic commands: Client
- Basic commands: Server / Relay
- Prefix ‘Hints’
Nalini Elkins & Mohit P. Tahiliani
Enterprises rarely switch over from IPv4 to IPv6 in one step. Generally, companies will run dual-stack for a time, where both IPv4 and IPv6 are available on devices. This doesn’t solve most of the problems IPv6 was designed to solve, so we will discuss the benefits and drawbacks of:
- Dual-stack
- NAT44
- Dual-stack Lite
- NAT64/DNS64
- 464xlat
- MAP-T
- MAP-E
- IPv6-Only
Nalini Elkins & Michael Ackermann