Search RFCs

RFC Editor

File formats:

Status:

EXPERIMENTAL

Authors:

R. Despres, Ed.
B. Carpenter
D. Wing
S. Jiang

Stream:

INDEPENDENT

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC6751

Discuss this RFC: Send questions or comments to the mailing listrfc-ise@rfc-editor.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 6751

Abstract

In customer sites having IPv4-only Customer Premises Equipment (CPE),Teredo (RFC 4380, RFC 5991, RFC 6081) provides last-resort IPv6connectivity. However, because it is designed to work without theinvolvement of Internet Service Providers, it has significantlimitations (connectivity between IPv6 native addresses and Teredoaddresses is uncertain; connectivity between Teredo addresses failsfor some combinations of NAT types). 6a44 is a complementarysolution that, being based on ISP cooperation, avoids theselimitations. At the beginning of 6a44 IPv6 addresses, it replacesthe Teredo well-known prefix, present at the beginning of Teredo IPv6addresses, with network-specific /48 prefixes assigned by local ISPs(an evolution similar to that from 6to4 to 6rd (IPv6 Rapid Deploymenton IPv4 Infrastructures)). The specification is expected to becomplete enough for running code to be independently written and thesolution to be incrementally deployed and used. This document definesan Experimental Protocol for the Internet community.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.