17 March 2001
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.
Mar 01 Progress 6to4-multicast to PS
Mar 01 Decide to either merge 6to4-DSTM with DSTM or move it separately to Informational
Mar 01 Decide fate of ipv4survey as it has been deleted from I-D registry
Mar 01 Progress tcpudp-relay back to IESG for Informational
Mar 01 Progress translator back to IESG for Informational
Mar 01 Decide what to do with personal draft hain-6to4-scaling
Mar 01 Decide what to do with personal draft itojun-ipv6-local-experiment
Mar 01 Decide what to do with personal draft templin-v6v4compat
Mar 01 Decide what to do with personal draft tsuchiya-mtp
Aug 01 Progress 6to4-dns to either Informational or PS
Aug 01 Progress DSTM to PS (keyed to DHCPv6 forwarding)
Aug 01 Progress mimetype to PS
Aug 01 Progress hometun to Informational
Aug 01 Progress Transition description to Informational
Dec 01 Progress v4-over-mipv6 to Informational
Mar 02 Progress 6to4 to DS
Mar 02 Progress MECH to DS
Mar 02 Progress SIIT-DSTM to either Informational or PS
Aug 02 Progress NAT-PT to DS
Aug 02 Progress SIIT to DS
Jan 96 [IPngWG] Original IPv6
Testing Address Allocation specified (RFC1897), under old provider-based addressing format
Mar 96 Agreement established to create a 6bone to test IPv6
Apr 96 Transition Mechanisms for IPv6 Hosts and Routers RFC1933 published as PS
May 96 Register 6bone.net with InterNIC and establis dns support
Jul 96 6bone startup with UNI-C/DK, G6/FR and WIDE/JP using provider-based testing
addresses (RFC1897)
Aug 96 6bone registry (ftp-based) established at RIPE-NCC
Dec 96 6bone converted to a tiered backbone architecture
Jun 97 6bone registry converted from ftp-based to RIPE-based
Sep 97 Routing Aspects Of IPv6 Transition RFC2185 published as Informational RFC
Oct 97 6bone converts to new Aggregatable Unicast Address Format
(RFC2374) using 3FFE TLA addresses (RFC2471)
Dec 98 [IPngWG] RFC2471 formalizes 3FFE TLA IPv6 Testing Address
Allocation
Mar 99 6bone Routing Practice RFC2546 published as Informational RFC
Feb 00 Stateless IP/ICMP Translation Algorithm (SIIT) RFC2765
published as PS
Feb 00 Network Address Translation - Protocol Translation (NAT-PT) RFC2766 published as PS
Feb 00 Dual Stack Hosts using the "Bump-In-the-Stack" Technique (BIS) RFC2767 published
as Informational RFC
Feb 00 6Bone Backbone Routing Guidelines (HARDEN) RFC2772 published as
Informational RFC
Aug 00 Transition Mechanisms for IPv6 Hosts and Routers RFC2893
published as PS, replacing RFC1933
Sep 00 6bone pTLA and pNLA Formats (pTLA) RFC2921 published as Informational RFC
Sep 00 Connection of IPv6 Domains via IPv4 Clouds (6to4) approved as
PS
Jan 01 IPv6 Tunnel Broker RFC3053 published as Informational RFC
Feb 01 Connection of IPv6 Domains via IPv4 Clouds (6to4)
RFC3056 published as PS
Mar 01 SOCKS-Gateway approved as Informational RFC
[Questions and comments] [6bone Home Page] [ngtrans Home Page]