IPNG (ipngwg) ------------- Charter Current status: active working group Chair(s): Bob Hinden Steve Deering Internet Area Director(s): Frank Kastenholz Jeffrey Burgan Mailing lists: General Discussion:ipng@sunroof.eng.sun.com To Subscribe: majordomo@sunroof.eng.sun.com In Body: subscribe ipng Archive: ftp://parcftp.xerox.com/pub/ipng Description of Working Group: Editor: Bob Hinden (hinden@eng.sun.com) The next generation of the Internet Protocol (IPv6) is intended to support Internet traffic for many years into the future by providing enhancements over the capabilities of the existing IPv4 service. This working group will produce specifications for the core functionality of that service. The working group shall carry out the recommendations of the IPng Area Directors as outlined at the July 1994 IETF and in ``The Recommendation for the IP Next Generation Protocol,'' Internet-Draft, (draft-ipng-recommendation-00.txt), September 1994. The working group shall use the following documents as the basis of its work: Simple Internet Protocol Plus (SIPP) Specfication (128 bit version) SIPP Addressing Architecture An Architecture for IPv6 Unicast Address Allocation Simple SIPP Transition (SST) Overview SIPP Program Interfaces for BSD Systems SIPP Security Architecture SIPP Authentication Header SDRP Routing Header for SIPP-16 IP Next Generation Overview ICMP and IGMP extensions for SIPP FTP Operation Over Big Address Records (FOOBAR) DNS Extensions to support SIPP Enhancements to be considered: Large Packets: Consider extensions for support of datagrams which are larger than 64K. Source Routing: The working group shall consider enhanced source routing capabilities for IPng. Tunneling: Complete specification of IPng in IPng tunneling. Address format and assignment plan: The working group shall review the details of address structure as specified in [SIPP-16] and shall repair any deficiencies with respect to current or near-term addressing requirements, assuming a fixed, 16-byte size. The specification shall provide a mechanism for supporting multiple additional formats, for possible enhancement to incorporate other popular addressing schemes. Routing Structure: In completing the addressing details, the working group shall ensure that routing according to current, CIDR-like schemes can be supported comfortably. Autoconfiguration: Coordinate with the IPng Address Autoconfiguration Working Group. Transition: The working group shall coordinate with the related transition and conversion efforts (ngtrans, tacit, nosi, etc.) to ensure that the base specification provides the facilities required for the transition from IPv4. Security: A set of base documents for IPng security shall be completed. This shall include algorithms for authentication and privacy carried as IPng extension headers and include an initial selection of required encryption and key management algorithms and a facility to support other optional algorithms. The working group should also examine IPng firewall issues and if necessary develop specific firewall frameworks. Minimum MTU: Consider a larger minimum MTU. Header Compression: Consider ways to abbreviate the IPng header in the contexts of native IPng, multiple IPng packets in a flow, and encapsulated IPng. TCP/UDP: The IPng Working Group will specify the procedures for hosts to compute and verify TCP/UDP pseudo-headers. Any other changes to TCP beyond making TCP work with IPng are out of scope of the working group and should be dealt with by a TCPng Working Group. The IPng Working Group will coordinate with other groups, including Mobile IP, IPng Address Autoconfiguration, OSPF, IS-IS, RIPv2, IDR, Security, Applications, Network Management, IP over ATM, etc. Goals and Milestones: Done Submit preliminary IPng core specifications, with required enhancements, as Internet-Drafts. Done Submit revised core IPng specifications as Internet-Drafts. Done Submit core IPng specifications to IESG for consideration as Proposed Standards. Feb 95 Submit extended IPng specifications as Internet-Drafts. Mar 95 Submit extended IPng specifications to IESG for consideration as Proposed Standards. Jul 95 Submit revised specifications to IESG based on implementation experience for consideration as Draft Standards. Oct 95 Submit revised IPng specifications as Internet-Drafts. Dec 95 Submit final IPng specifications to IESG for consideration as Standards. Internet-Drafts: Posted Revised I-D Title ------ ------- ------------------------------------------ Oct 94 Apr 96 Basic Socket Interface Extensions for IPv6 Nov 94 Apr 96 An IPv6 Provider-Based Unicast Address Format Jun 95 Mar 96 Neighbor Discovery for IP Version 6 (IPv6) Aug 95 Mar 96 A Method for the Transmission of IPv6 Packets over Ethernet Networks Aug 95 May 96 A Method for the Transmission of IPv6 Packets over FDDI Networks Aug 95 May 96 OSI NSAPs and IPv6 Sep 95 Jan 96 A Method for the Transmission of IPv6 Packets over Token Ring Networks Nov 95 May 96 Path MTU Discovery for IP version 6 Nov 95 Jun 96 Generic Packet Tunneling in IPv6 Specification Dec 95 May 96 IP Version 6 over PPP Feb 96 May 96 Identifying IPv6 Interfaces in Link-Local Addresses Jun 96 New Link Local Addressing and Name Resolution in IPv6 Request For Comments: RFC Stat Published Title ------- -- ---------- ----------------------------------------- RFC1884 PS Jan 96 IP Version 6 Addressing Architecture RFC1883 PS Jan 96 Internet Protocol, Version 6 (IPv6) Specification RFC1885 PS Jan 96 Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) RFC1887 I Jan 96 An Architecture for IPv6 Unicast Address Allocation RFC1886 PS Jan 96 DNS Extensions to support IP version 6 RFC1897 E Jan 96 IPv6 Testing Address Allocation