Bob Hinden will talk about how and why IPv6 was developed in the IETF, the state of the deployment of iPv6 on the Internet, and what he thinks the future looks like.
Bob Hinden is a Check Point Fellow at Check Point Software, and co-chairs the IPv6 working group in the IETF. He is the co-inventor of the Internet Protocol Version 6 Protocol (IPv6).
Bob Hinden was the Chair of the Internet Society Board of Trustees from 2013 to 2016, and a member of the Board of Trustees from 2010-2016. Previously at Nokia, he was a Nokia Fellow, Chief Internet Technologist at Nokia Networks, and Chief Technical Officer (CTO) at the Nokia IP Routing Group.Bob Hinden was one of the early employees (i.e., employee number 4) of Ipsilon Networks, Inc. Ipsilon was acquired by Nokia on December 31, 1997. He was previously employed at Sun Microsystems where he was responsible for the Internet Engineering group that implements internet protocols for Sun’s operating systems. Prior to this he worked at Bolt, Beranek, and Newman, Inc. on a variety of internetwork related projects including the first operational internet router and one of the first TCP/IP implementations.Bob Hinden was co-recipient of the 2008 IEEE Internet Award for pioneering work in the development of the first Internet routers.
Bob Hinden has been active in the IETF since 1985 and is the author of forty two RFCs, including three April 1 RFCs. He served as the chair of the IETF Administrative Oversight Committee (IAOC) from 2009 through 2013. Prior to this he served on the Internet Architecture Board (IAB), was Area Director for Routing in the Internet Engineering Steering group from 1987 to 1994, and chaired the IPv6, Virtual Router Redundancy Protocol, Simple Internet Protocol Plus, IPAE, the IP over ATM, and the Open Routing working groups. He is also a member of the RFC Editorial Board and the RFC Series Oversight Committee.Bob Hinden holds an B.S.E.E., and a M.S. in Computer Science from Union College, Schenectady, New York.
This session is funded with a grant from ARIN. It is a two-hour webinar consisting of IPv6 Fundamentals and Neighbor Discovery.
IPv6 Fundamentals: To be successful in implementing and understanding IPv6 networks, you need to first understand the IPv6 address methodology which is, in many ways, a fundamental change from the IPv4 paradigm. In this introduction, you will become familiar with what is different as well as what is the same with IPv6.
- Public and private addresses
- IPv6 Prefixes
- IPv6 Address Structure
- IPv6 Interface ID
- IPv6 Addressing and Address Allocation Methods (stateless, statefull)
- Address types, unicast, multicast, anycast
- Address categories: global, site local, link local
- Unique Local Unicast addresses
- Zero compression
- Special addresses (loopback, unspecified, IPv4 mapped IPv6)
- Broadcast address elimination
.Neighbor Discovery (SLAAC)Description: The Neighbor Discovery Protocol (NDP) is one of key building blocks of IPv6, though it creates an alphabet soup of acronyms (NDP, RA, RS, NS, NA, DAD, MLD, SLAAC, RDNSS). We will describe how NDP works and its basic functions, including addressing and routing. Network engineers and systems engineers who are familiar with IPv6 addresses are welcome.
- Neighbor Discovery Protocol (NDP)
- Router Advertisements (RA)
- Router Solicitation (RS)
- Neighbor Solicitation (NS)
- Neighbor Advertisement (NA)
- Duplicate Address Detection (DAD)
- Multicast Listener Discovery (MLD)
- Stateless Address Autoconfiguration (SLAAC)
- Router Advertisements for DNS (RDNSS)
Nalini Elkins is the President of the Industry Network Technology Council.
Drones and other Unmanned Aircraft Systems (UAS) are proliferating rapidly. What are the needs for regulation?
Civil Aviation Authorities (CAAs) worldwide have initiated rule making for Unmanned Aircraft Systems (UAS) Remote Identification (RID). There is a Working Group proposed for this activity at the IETF. Bob Moskowitz and Stu Card will discuss the history and rationale for this proposed standards activity.
Robert Moskowitz has been working with computers since 1966 when, in 11th grade, his high school became perhaps the first in the nation to have in-classroom computer access (a teletype in the back of the room). He entered the programming profession in 1974 shortly after receiving a Bachelor of Science in Computer Science from Michigan State University (1972) along with a Bachelor of Science in Botany. Robert worked 19 years Automotive, in IT technical support, and for 17 years at ICSAlabs (now a division of Verizon Business) in network security research and is now an independent security consultant. He informed the FCC on Internet technology 2013-2016. Additionally, he has written or edited 61 RFCs since 1989. He has been active in the IETF since 1993 and IEEE 802 since 2001. His contributions there include the private IPv4 address space, IPsec, PKIX, HIP, DOTS, 802.11i, 802.1(X, AE, and AR), and 802.15.9. He is currently investigating better ways to address IoT devices and networks. This included designing the network security for ZWAVE 2.0. He is currently working on communications security for Unmanned Aircraft Systems (UAS). In his spare time he works with armv7 boards, assisting development of Fedora and CentOS for these platforms.
Stu Card’s Navy training included brief experiences operating aircraft, ships and submarines. His SU PhD research applied information theory to evolutionary algorithm based machine learning. He has over 30 years experience, designing airborne radar and neural network hardware, a broadband cable modem, fault-tolerant storage, airborne network protocols, cryptocurrency/blockchain applications, etc., and cofounding Central NY’s first consumer ISP. He now focuses on existential threats involving complex interdependent networks and autonomous cyber-physical systems, and supports the NYUASTS.
The IETF has documented most of the protocols used in the Internet below the application layer. This brief overview in intended to inform the audience about the IETF – what it is, what it does, who it is composed of, and how it works. It will also point out the IETF’s deficiencies; specifically, that constituencies that don’t participate often don’t find their issues resolved in those specifications, which often works against them in one way or another. Ideally, those constituencies will be motivated and guided in making an impact on the technologies that their businesses depend on.
Fred Baker has worked in the software engineering of computer networks since 1978, including Internet technology starting in 1986. He has chaired several IETF working groups on various topics; since 2005, he has chaired or co-chaired the IPv6 Operations working group. In addition, he chaired the IETF 1996-2001, and served on the Internet Architecture Board 1996-2002. He has also been a member of the board of the Internet Software Consortium, which runs one of the DNS root services, since 2008, and represents them in ICANN’s Root Server System Advisory Committee – which he has also chaired 2018-present. He is currently also the chair and primary editor in ITU Focus Group on Quantum Technology in Networking, in the sub-group related to the Implications of Quantum IT on Networks. He represented Cisco in BITAG, writing or contributing to many documents intended to inform the FCC on Internet technology 2013-2016. Additionally, he has written or edited 61 RFCs since 1989.