RFC 4380: Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)
In plain English — editorial summary, not part of the RFC
We propose here a service that enables nodes located behind one or more IPv4 Network Address Translations (NATs) to obtain IPv6 connectivity by tunneling packets over UDP; we call this the Teredo service. Running the service requires the help of "Teredo servers" and "Teredo relays". The Teredo servers are stateless, and only have to manage a small fraction of the traffic between Teredo clients; the Teredo relays act as IPv6 routers between the Teredo service and the "native" IPv6 Internet. The relays can also provide interoperability with hosts using other transition mechanisms such as "6to4". [STANDARDS-TRACK]
Document record
- Document ID
- RFC4380
- Published
- February 2006
- Authors
- C. Huitema
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 53
- Also known as
- —
Referenced by
3 later RFCs formally update or obsolete part of this document.
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?