Next Generation Transition (ngtrans)


In addition to this official charter maintained by the IETF Secretariat, there is additional information about this working group on the Web at:

       Additional NGTRANS Page

Last Modified: 2002-06-05

Chair(s):

Tony Hain <tony@tndh.net>
Alain Durand <Alain.Durand@sun.com>
Margaret Wasserman <mrw@windriver.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:

Mar 01  Decide if BGP-tunnel is Informational or Experimental
Mar 01  Decide fate of ipv4survey as it has been deleted from I-D registry
Mar 01  Progress 6papa to Informational
Done  Progress socks-gateway back to IESG for Informational
Done  Progress tcpudp-relay back to IESG for Informational
Mar 01  Decide what to do with personal draft templin-v6v4compat
Mar 01  Decide what to do with personal draft tsuchiya-mtp
Mar 01  Decide what to do with personal draft hain-6to4-scaling
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 Transition description to Informational
Dec 01  Progress v4-over-mipv6 to Informational
Mar 02  Progress SIIT-DSTM to either Informational or PS
Mar 02  Progress 6to4 to DS
Mar 02  Progress MECH to DS
Aug 02  Progress NAT-PT to DS
Aug 02  Progress SIIT to DS

Internet-Drafts:

An overview of the Introduction of IPv6 in the Internet ( bytes)
Dual Stack Transition Mechanism (DSTM) ( bytes)
Survey of IPv4 Addresses in Currently Deployed IETF Standards ( bytes)
Connecting IPv6 Domains across IPv4 Clouds with BGP ( bytes)
Support for Multicast over 6to4 Networks ( bytes)
Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) ( bytes)
SMTP operational experience in mixed IPv4/IPv6 environements ( bytes)
An IPv6/IPv4 Multicast Translator based on IGMP/MLD Proxying (mtp) ( bytes)
Moving in a Dual Stack Internet ( bytes)
Dual Stack Hosts using 'Bump-in-the-API' (BIA) (2549 bytes)
NGtrans IPv6 DNS operational requirements and roadmap ( bytes)
Teredo: Tunneling IPv6 over UDP through NATs ( bytes)
Interaction of transition mechanisms ( bytes)
MIME TYPE definition for tunnels ( bytes)
Dual Stack Transition Mechanism (DSTM) Overview ( bytes)
ISATAP Transition Scenario for Enterprise/Managed Networks ( bytes)
Unmanaged Networks Transition Scope ( bytes)
Transition Mechanisms for IPv6 Hosts and Routers ( bytes)

Request For Comments:

Transition Mechanisms for IPv6 Hosts and Routers (RFC 1933) (47005 bytes) obsoleted by RFC 2893
Routing Aspects of IPv6 Transition (RFC 2185) (31281 bytes)
6Bone Routing Practice (RFC 2546) (17844 bytes) obsoleted by RFC 2772
Stateless IP/ICMP Translation Algorithm (SIIT) (RFC 2765) (59465 bytes)
Network Address Translation - Protocol Translation (NAT-PT] (RFC 2766) (49836 bytes)
Dual Stack Hosts using the Bump-In-the-Stack Technique (BIS) (RFC 2767) (26402 bytes)
6Bone Backbone Routing Guidelines (RFC 2772) (28565 bytes)
Transition Mechanisms for IPv6 Hosts and Routers (RFC 2893) (62731 bytes)
6BONE pTLA and pNLA Formats (pTLA) (RFC 2921) (14218 bytes)
IPv6 Tunnel Broker (RFC 3053) (27336 bytes)
Connection of IPv6 Domains via IPv4 Clouds (RFC 3056) (54902 bytes)
A SOCKS-based IPv6/IPv4 Gateway Mechanism (RFC 3089) (25193 bytes)
An anycast prefix for 6to4 relay routers (RFC 3068) (20120 bytes)
An IPv6-to-IPv4 transport relay translator (RFC 3142) (20864 bytes)

IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.

Return to working group directory.

Return to IETF home page.