Ngtrans Workgroup RFCs

Browse Ngtrans Workgroup RFCs by Number

RFC1933 - Transition Mechanisms for IPv6 Hosts and Routers: This document specifies IPv4 compatibility mechanisms that can be implemented by IPv6 hosts and routers. [STANDARDS-TRACK]
RFC2185 - Routing Aspects of IPv6 Transition: This document gives an overview of the routing aspects of the IPv6 transition. It is based on the protocols defined in the document "Transition Mechanisms for IPv6 Hosts and Routers." Readers should be familiar with the transition mechanisms before reading this document. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC2546 - 6Bone Routing Practice: This memo identifies guidelines on how 6Bone sites might operate, so that the 6Bone can remain a quality experimentation environment and to avoid pathological situations that have been encountered in the past. It defines the 'best current practice' acceptable in the 6Bone for the configuration of both Interior Gateway Protocols and Exterior Gateway Protocols. This memo provides information for the Internet community.
RFC2765 - Stateless IP/ICMP Translation Algorithm (SIIT): This document specifies a transition mechanism algorithm in addition to the mechanisms already specified. [STANDARDS-TRACK]
RFC2766 - Network Address Translation - Protocol Translation (NAT-PT): This document specifies an IPv4-to-IPv6 transition mechanism, in addition to those already specified. [STANDARDS-TRACK]
RFC2767 - Dual Stack Hosts using the "Bump-In-the-Stack" Technique (BIS): This memo proposes a mechanism of dual stack hosts using the technique called "Bump-in-the-Stack" in the IP security area. This memo provides information for the Internet community.
RFC2772 - 6Bone Backbone Routing Guidelines: This document provides a set of guidelines for all 6bone routing equipment operators to use as a reference for efficient and stable deployment of 6bone routing systems. This memo provides information for the Internet community.
RFC2893 - Transition Mechanisms for IPv6 Hosts and Routers: This document specifies IPv4 compatibility mechanisms that can be implemented by IPv6 hosts and routers. [STANDARDS-TRACK]
RFC2921 - 6BONE pTLA and pNLA Formats (pTLA): This memo defines how the 6bone uses the 3FFE::/16 IPv6 address prefix, allocated in RFC 2471, "IPv6 Testing Address Allocation", to create pseudo Top-Level Aggregation Identifiers (pTLA's) and pseudo Next-Level Aggregation Identifiers (pNLA's). This memo provides information for the Internet community.
RFC3053 - IPv6 Tunnel Broker: The motivation for the development of the tunnel broker model is to help early IPv6 adopters to hook up to an existing IPv6 network (e.g., the 6bone) and to get stable, permanent IPv6 addresses and DNS names. The concept of the tunnel broker was first presented at Orlando's IETF in December 1998. Two implementations were demonstrated during the Grenoble IPng & NGtrans interim meeting in February 1999. This memo provides information for the Internet community.
RFC3056 - Connection of IPv6 Domains via IPv4 Clouds: This memo specifies an optional interim mechanism for IPv6 sites to communicate with each other over the IPv4 network without explicit tunnel setup, and for them to communicate with native IPv6 domains via relay routers. [STANDARDS-TRACK]
RFC3068 - An Anycast Prefix for 6to4 Relay Routers: This memo introduces a "6to4 anycast address" in order to simplify the configuration of 6to4 routers. It also defines how this address will be used by 6to4 relay routers, how the corresponding "6to4 anycast prefix" will be advertised in the IGP and in the EGP. The memo documents the reservation by IANA (Internet Assigned Numbers Authority) of the "6to4 relay anycast prefix." [STANDARDS-TRACK]
RFC3089 - A SOCKS-based IPv6/IPv4 Gateway Mechanism: This document describes a SOCKS-based IPv6/IPv4 gateway mechanism that enables smooth heterogeneous communications between the IPv6 nodes and IPv4 nodes. This memo provides information for the Internet community.
RFC3142 - An IPv6-to-IPv4 Transport Relay Translator: The document describes an IPv6-to-IPv4 transport relay translator (TRT). This memo provides information for the Internet community.
RFC3338 - Dual Stack Hosts Using "Bump-in-the-API" (BIA)