Last Modified: 2004-06-18
The IPv6 working group was originally chartered by the IESG as the IP Next Generation (IPng) working group to implement the recommendations of the IPng Area Directors as outlined at the July 1994 IETF meeting and in "The Recommendation for the IP Next Generation Protocol," RFC1752, January 1995.
The primary focus of the IPv6 w.g. is to complete the standardization of the IPv6 protocols, and to review and update the IPv6 specifications based on implementation and deployment experience, and advancing them on the standardization track as appropriate.
The working group's work items are as follows:
o Complete Prefix Delegation requirements and publish. Related remaining work is: - Develop Proxy Neighbor Discovery solution for prefix delegation and publish. This enables a simple site border router to re-advertise downstream a prefix it hears on its upstream link. o Complete revision of IPv6 MIBs (combined IPv4/IPv6 versions) and publish. o Complete "Default Router Preferences, More-Specific Routes, and "Load Sharing" and publish. o Update to ICMPv6 (RFC2463) and publish. o Complete "Node Information Queries" and publish. o Update Auto Configuration (RFC2462) and Neighbor Discovery (RFC2461) and publish. o Investigate approaches to optimize or eliminate Duplicate Address Detection (DAD) to make reduce the delays incurred by DAD when there is a change of network attachment points. Publish a document defining DAD optimizations. o Update "Privacy Extensions for Stateless Autoconfiguration" document (RFC3041) and publish. o Complete work on IPv6 Node Requirements and publish. o Complete work stemming from the working group decision to deprecate site-local addressing. This includes: - Publish document deprecating the usage of Site-Local addressing. - Publish revision of the IPv6 Address Architecture that includes the deprecation of site-local addressing. - Publish a replacement for site-local addresses that removes the major limitations and allows for local allocations. o Update the IPv6 Address Architecture to resolve the issues raised in the IAB response to the Robert Elz appeal and publish as a Draft Standard. o Complete work on Scoped Addressing Architecture and publish. o Update IPv6 over PPP (RFC2472) and publish. o Complete work on "Link Scoped IPv6 Multicast Addresses" and publish.
All new work items not listed above require the approval of the working group and IESG before they will be taken on by the working group.
|Done||Submit A Flexible method to manage the assignment of bits of an IPv6 address block to the IESG for Informational.|
|Done||Submit Flow Label specification to IESG for Proposed Standard.|
|Done||Submit Prefix Delegation requirements and submit to IESG for Informational.|
|Done||Revise Aggregatable Unicast Addresses (RFC2374) to remove TLA/NLA/SLA terminology.|
|Done||Draft on Proxy RA solution for prefix delegation.|
|Done||Submit IPv6 Node Requirements to IESG for Informational.|
|Done||Submit Site-Local Deprecation document to IESG for Informational.|
|Done||Submit Unique Local IPv6 Unicast Addresses to IESG for Proposed Standard|
|Apr 04||Submit Link Scoped IPv6 Multicast Addresses to IESG for Proposed Standard|
|Apr 04||Submit IPv6 Scoped Addressing Architecture to IESG for Proposed Standard|
|Apr 04||Submit TCP MIB to IESG for Proposed Standard|
|Apr 04||Submit Site-Local Deprecation document to IESG for Informational|
|Apr 04||Submit Unique Local IPv6 Unicast Addresses to IESG for Proposed Standard|
|May 04||Submit update to ICMPv6 (RFC2463) to be republished at Draft Standard|
|May 04||Submit Router Preferences, More-Specific Routes, and Load Sharing to IESG for Proposed Standard|
|Jun 04||Resubmit Node Information Queries to IESG for Proposed Standard|
|Jun 04||Submit updates to Auto Configuration (RFC2462) and Neighbor Discovery (RFC2461) to be republished at Draft Standard|
|Jun 04||Submit Proxy ND to IESG for Informational|
|Jun 04||Submit update to IPv6 over PPP (RFC2472) to IESG for Draft Standard|
|Jun 04||Submit update to IPv6 Address Architecture to the IESG for Draft Standard|
|Aug 04||Submit Update to Privacy Extensions for Stateless Autoconfiguration document (RFC3041) to the IESG for Draft Standard|
|Dec 04||Submit document defining DAD optimizations to the IESG for Proposed Standard|
|Jan 05||Re-charter or close working group.|
|RFC1887||I||An Architecture for IPv6 Unicast Address Allocation|
|RFC1883||PS||Internet Protocol, Version 6 (IPv6) Specification|
|RFC1885||PS||Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6)|
|RFC1886||PS||DNS Extensions to support IP version 6|
|RFC1884||PS||IP Version 6 Addressing Architecture|
|RFC1897||E||IPv6 Testing Address Allocation|
|RFC1981||PS||Path MTU Discovery for IP version 6|
|RFC1888||E||OSI NSAPs and IPv6|
|RFC1972||PS||A Method for the Transmission of IPv6 Packets over Ethernet Networks|
|RFC1970||PS||Neighbor Discovery for IP Version 6 (IPv6)|
|RFC2019||PS||Transmission of IPv6 Packets Over FDDI|
|RFC2023||PS||IP Version 6 over PPP|
|RFC2073||PS||An IPv6 Provider-Based Unicast Address Format|
|RFC2133||I||Basic Socket Interface Extensions for IPv6|
|RFC2147||PS||TCP and UDP over IPv6 Jumbograms|
|RFC2292||I||Advanced Sockets API for IPv6|
|RFC2373||PS||IP Version 6 Addressing Architecture|
|RFC2374||PS||An IPv6 Aggregatable Global Unicast Address Format|
|RFC2375||I||IPv6 Multicast Address Assignments|
|RFC2461||DS||Neighbor Discovery for IP Version 6 (IPv6)|
|RFC2462||DS||IPv6 Stateless Address Autoconfiguration|
|RFC2463||DS||Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification|
|RFC2464||PS||Transmission of IPv6 Packets over Ethernet Networks|
|RFC2460||DS||Internet Protocol, Version 6 (IPv6) Specification|
|RFC2452||PS||IP Version 6 Management Information Base for the Transmission Control Protocol|
|RFC2454||PS||IP Version 6 Management Information Base for the User Datagram Protocol|
|RFC2465||PS||Management Information Base for IP Version 6: Textual Conventions and General Group|
|RFC2466||PS||Management Information Base for IP Version 6: ICMPv6 Group|
|RFC2450||I||Proposed TLA and NLA Assignment Rules|
|RFC2467||PS||Transmission of IPv6 Packets over FDDI Networks|
|RFC2470||PS||Transmission of IPv6 Packets over Token Ring Networks|
|RFC2471||E||IPv6 Testing Address Allocation|
|RFC2472||PS||IP Version 6 over PPP|
|RFC2473||PS||Generic Packet Tunneling in IPv6 Specification|
|RFC2497||PS||Transmission of IPv6 Packets over ARCnet Networks|
|RFC2507||PS||IP Header Compression|
|RFC2526||PS||Reserved IPv6 Subnet Anycast Addresses|
|RFC2529||PS||Transmission of IPv6 over IPv4 Domains without Explicit Tunnels|
|RFC2553||I||Basic Socket Interface Extensions for IPv6|
|RFC2710||PS||Multicast Listener Discovery (MLD) for IPv6|
|RFC2711||PS||IPv6 Router Alert Option|
|RFC2732||PS||Format for Literal IPv6 Addresses in URL's|
|RFC2874||PS||DNS Extensions to Support IPv6 Address Aggregation and Renumbering|
|RFC2894||PS||Router Renumbering for IPv6|
|RFC2928||I||Initial IPv6 Sub-TLA ID Assignments|
|RFC3041||PS||Privacy Extensions for Stateless Address Autoconfiguration in IPv6|
|RFC3019||PS||IP Version 6 Management Information Base for the Multicast Listener Discovery Protocol|
|RFC3122||PS||Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification|
|RFC3178||I||IPv6 multihoming support at site exit routers|
|RFC3146||PS||Transmission of IPv6 Packets over IEEE 1394 Networks|
|RFC3306||PS||Unicast-Prefix-based IPv6 Multicast Addresses|
|RFC3314||I||Recommendations for IPv6 in 3GPP Standards|
|RFC3484||PS||Default Address Selection for Internet Protocol version 6 (IPv6)|
|RFC3493||I||Basic Socket Interface Extensions for IPv6|
|RFC3513||PS||IP Version 6 Addressing Architecture|
|RFC3531||I||A Flexible Method for Managing the Assignment of Bites of an IPv6 Address Block|
|RFC3316||I||IPv6 for Some Second and Third Generation Cellular Hosts|
|RFC3542||I||Advanced Sockets Application Program Interface (API) for IPv6|
|RFC3587||I||IPv6 Global Unicast Address Format|
|RFC3697||Standard||IPv6 Flow Label Specification|
|RFC3769||I||Requirements for IPv6 prefix delegation|
IPv6 Working Group Meeting Notes, San Diego IETF
Wednesday, August 4, 2004, 1530-1730
Chairs: Robert Hinden (email@example.com)
Brian Haberman (firstname.lastname@example.org)
Minutes taken by Karen O'Donoghue.
1. Introduction and Agenda Bashing
Brian Haberman presented the proposed agenda. There were no comments, changes, or additions. Brian also provided document status by providing a link for document status to save time during the meeting. Any questions or issues can be brought up at the end of the meeting. The summary of the current document status is provided at the end of these minutes. (http://www.innovationslab.net/~brian/IETF59/IPv6/IPv6DocumentStatus.html)
2. IPv6 Plugtest Announcement
Guillemin announced the 50th IPv6 plugtest. It will be October 11-15, 2004, in Cannes, France. Information is available at: www.etsi.org/plugtests/IPv6.htm. The IPv6Ready Logo Phase 1 testing will be held at this event.
3. IPv6 DNS Configuration Approaches
There is a draft on IPv6 DNS configuration options in DNSOPS. The options include a RA Option, a DHCP Option, and a Well-Known Addresses. The DNSOPS has been unable to reach consensus on moving forward. The document draft-jeong-dnsop-ipv6-dns-discovery-02.txt doesn't propose any solutions. It is informational input to IESG on a way forward.
A question was posed to the WG. Who thinks that we should not work on RA options for DNS Servers. The results were not conclusive. This information will be given to the IESG as input.
Brian substituted for Hesham Soliman providing a status update for draft-soliman-ipv6-2461-bis-01.txt. There are three unresolved issues including enabling forwarding per interface and prefix length limitations. There was a suggestion that the current text is sufficient. There were no objections to going to last call after the three issues are resolved.
Tatuya Jinmei provided a status update of draft-ietf-ipv6-rfc2462bis-02.txt. There are no blocking issues. Last call was completed on July 13 (4 responses during the last call). Issues identified include IFID length, DAD, and M/O flags. For the IFID length issue, the document was clarified regarding the dependency on addr-arch and link specific docs resulting in no behavior change.
There is a possible issue related to the IAB recommendation on prefix length. Bob Hinden doesn't see this as an issue. The document should be almost ready. The plan is to revise it once more and then submit it to the IESG.
6. ICMP Updates
Mukesh Gupta provided a status update of draft-ietf-ipngwg-icmp-v3-03.txt. This was a Draft Standard in 1998. The plan was to recycle it in Draft Standard. The WG last call was completed May 28th. Four comments were received.
One issue the removal of an unimplemented ICMP source address selection specification. The chairs didn't see enough consensus to remove the section, it will NOT be removed.
Some discussion was held on the process for reviewing single type value assignments received from outside the IETF. These should be sent to the IETF for review. Brian Carpenter indicated that there should be a more precise address provided. Bob Hinden indicated that there is some evidence that this process doesn't work well from outside the IETF.
An updated draft will be submitted soon after the end of this IETF. Brian Haberman asked for a one week WG last call after the text is ready.
7. Optimistic DAD
Nick Moore provided a status update on draft-ietf-ipv6-optimistic-dad-01.txt. An issue tracker has been set up at: http://www.ctie.monash.edu.au/ipv6/fastho/opti_data_issues.html
Brian Haberman requested that when the update is available, hold a one week WG last call.
8. M&O Flags in RA's
Daniel Park presented draft-daniel-ipv6-ra-mo-flags-00.txt to raise awareness of this work and to ask the question if it is ready for WG adoption. A number of questions were raised including: are there any existing statements that recommend against this, and how would you like the host to behave when there isn't a router?
Bob Hinden polled the WG on how many people had read this draft (a small number). A slightly higher number indicated that they think it is not ready for adoption. Based on that, the work will continue to mature independently prior to WG adoption.
9. DNS configuration (RA option)
The WG chairs asked if the WG should be doing something about draft-ietf-dnsop-ipv6-dns-configuration-01.txt and in particular the arrangement of IPv6 Hop by Hop options. The problem is that the HBH options are especially suitable for launching DoS. The question raised was if we should worry about this and where does this work belong. It seems a high price to pay for a problem that isn't going to occur often enough. There was no consensus within the WG to investigate the problem at this time.
10. Anycast Analysis
The WG chairs discussed what to do with draft-ietf-ipngwg-ipv6-anycast-analysis-02.txt. There are three options; drop the document, publish as-is, or start over. Dropping the document leaves a hole and no one felt this was the thing to do. To publish it as-is doesn't address issues in the current draft. A set of people are willing to participate in the work under the start over option.
11. IPv6 over PPP update
Alex Conta provided a status update of draft-ietf-ipv6-over-ppp-v2-01.txt. This document is ready for a working group last call.
12. Link-scoped Multicast
Shin discussed draft-ietf-ipv6-link-scoped-mcast-04.txt with a goal to resolve open issues from the WG Last Call. The general feeling was that there are more ways to solve this problem.
13. IPv6 over WLAN/802.11
Time ran out before this topic could really be addressed. Brian Haberman indicated that the chairs were putting together a small group to begin looking into this issue.
The meeting adjourned at 1730. The document status as of this meeting is provided below.