RFC 6081: Teredo Extensions
In plain English — editorial summary, not part of the RFC
This document specifies a set of extensions to the Teredo protocol. These extensions provide additional capabilities to Teredo, including support for more types of Network Address Translations (NATs) and support for more efficient communication. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6081
- Published
- January 2011
- Authors
- D. Thaler
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 59
- Also known as
- —
- Updates:
- RFC 4380
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6052IPv6 Addressing of IPv4/IPv6 TranslatorsCurrent
October 2010
- RFC 6535Dual-Stack Hosts Using "Bump-in-the-Host" (BIH)Current
February 2012
- RFC 6127IPv4 Run-Out and IPv4-IPv6 Co-Existence ScenariosCurrent
May 2011
- RFC 5928Traversal Using Relays around NAT (TURN) Resolution MechanismUpdated
August 2010
- RFC 5627Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP)Current
October 2009
- RFC 5619Softwire Security Analysis and RequirementsCurrent
August 2009
- RFC 6619Scalable Operation of Address Translators with Per-Interface BindingsCurrent
June 2012
- RFC 5389Session Traversal Utilities for NAT (STUN)Obsoleted
October 2008
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?