NOTE: This charter is a snapshot of the 48th IETF Meeting in Pittsburgh, Pennsylvania. It may now be out-of-date. Last Modified: 17-Jul-00
Chair(s):
Bob Fink <rlfink@lbl.gov>
Tony Hain <tonyhain@microsoft.com>
Alain Durand <alain.durand@eng.sun.com>
Operations and Management Area Director(s):
Randy Bush <randy@psg.com>
Bert Wijnen <bwijnen@lucent.com>
Operations and Management Area Advisor:
Randy Bush <randy@psg.com>
Mailing Lists:
General Discussion:ngtrans@sunroof.eng.sun.com
To Subscribe: majordomo@sunroof.eng.sun.com
In Body: subscribe ngtrans
Archive: ftp://ftp.ietf.org/ietf-mail-archive/ngtrans/
Description of Working Group:
1. Specify the tools and mechanisms that might be used for transition to IPv6.
2. Write documents outlining how the various transition tools and mechanisms might apply to various scenarios for a transition to IPv6.
3. Coordinate with the IPv6 6bone testbed, operating under the IPv6 Testing Address Allocation allocated in Experimental RFC 2471, to foster the development, testing, and deployment of IPv6.
4. Coordinate appropriately with other IPv6 related IETF activities and activities in other organizations.
Goals and Milestones:
Dec 94 |
|
Submit Internet-Draft on General Overview of Transition. |
Done |
|
Submit Internet-Draft on Specifications of Transition Mechanisms for IPv6 Hosts and Routers. |
Done |
|
Submit Internet-Draft of Transition Plan for the Internet. |
Done |
|
Submit Internet-Draft on Specification of mechanisms for header translating routers. |
Done |
|
Sunbmit Specification of Transition Mechanisms for IPv6 Hosts and Routers to IESG for consideration as a Proposed Standard. |
Apr 95 |
|
Submit Specifications for Header Translating Routers document to IESG for consideration as a Proposed Standard. |
Jul 95 |
|
Submit Specification of mechanisms for header translating routers to IESG for consideration as a Draft Standard. |
Mar 96 |
|
Submit Specifications of Transition Mechanisms for IPv6 Hosts and Routers to IESG for consideration as a Draft Standard. |
May 96 |
|
Register 6bone.net with InterNIC and establis dns support |
Jul 96 |
|
6bone startup with UNI-C/DK, G6/FR and WIDE/JP |
Aug 96 |
|
Establish ftp-based 6bone registry at RIPE-NCC |
Nov 96 |
|
Submit Internet-Draft on role of IPv4-compatible Addresses in IPv6 |
Dec 96 |
|
Start restructuring 6bone to a tiered backbone architecture |
Mar 97 |
|
Submit Internet-Draft for an IPv6 registry on site database objects. |
Done |
|
Convert 6bone registry from ftp-based to RIPE-based |
Done |
|
Start conversion of 6bone to Aggregatable Unicast Address Format |
Nov 97 |
|
Testing starts on new Aggregatable Unicast Address Format |
Done |
|
RFC 2471 formalizes IPv6 Testing Address Allocation |
Done |
|
Hold Interim meeting in Grenoble |
Done |
|
Submit update to RFC1933 to IESG for consideration as a Proposed Standard |
Jul 99 |
|
Submit modified RFC1933 to IESG for consideration as a Draft Standard |
Dec 99 |
|
Submit 6to4/AIIH-DTI/NAT-PT/BIS I-Ds for IESG processing |
Dec 99 |
|
Submit Roadmap I-Ds for IESG processing as Informational RFCs |
Mar 00 |
|
Evaluate state of roadmap, tool and mechanism docs for further work |
Internet-Drafts:
· Transition Mechanisms for IPv6 Hosts and Routers
· Overview of Transition Techniques for IPv6-only to Talk to IPv4-only Communication
· Connection of IPv6 Domains via IPv4 Clouds without Explicit Tunnels
· On overviewof the Introduction of IPv6 in the IPv4 Internet
· A SOCKS-based IPv6/IPv4 Gateway Mechanism
· 6BONE Pre-Qualification for Address Prefix Allocation (6PAPA)
· Dual Stack Transition Mechanism (DSTM)
· An IPv6-to-IPv4 transport relay translator
· 6BONE pTLA and pNLA Formats (pTLA)
· IPv6 over IPv4 tunnels for home to Internet access
· Survey of IPv4 Addresses in Currently Deployed IETF Standards
Request For Comments:
RFC |
Status |
Title |
RFC1933 |
PS |
Transition Mechanisms for IPv6 Hosts and Routers |
RFC2185 |
Routing Aspects of IPv6 Transition | |
RFC2765 |
PS |
Stateless IP/ICMP Translation Algorithm (SIIT) |
RFC2766 |
PS |
Network Address Translation - Protocol Translation (NAT-PT] |
RFC2767 |
Dual Stack Hosts using the Bump-In-the-Stack Technique (BIS) | |
RFC2772 |
6Bone Backbone Routing Guidelines | |
None received.