metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 4092: Usage of the Session Description Protocol (SDP) Alternative Network Address Types (ANAT) Semantics in the Session Initiation Protocol (SIP)

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5245.

Current document in this lineage: RFC 8445 — Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal; RFC 8839 — Session Description Protocol (SDP) Offer/Answer Procedures for Interactive Connectivity Establishment (ICE)

In plain English — editorial summary, not part of the RFC

This document describes how to use the Alternative Network Address Types (ANAT) semantics of the Session Description Protocol (SDP) grouping framework in SIP. In particular, we define the sdp-anat SIP option-tag. This SIP option-tag ensures that SDP session descriptions that use ANAT are only handled by SIP entities with ANAT support. To justify the need for such a SIP option-tag, we describe what could possibly happen if an ANAT-unaware SIP entity tried to handle media lines grouped with ANAT. [STANDARDS-TRACK]

Document record

Document ID
RFC4092
Published
June 2005
Authors
G. Camarillo; J. Rosenberg
Status
PROPOSED STANDARD
Stream
IETF
Area
rai
Pages
6
Also known as
—
Obsoleted by:
RFC 5245

Topics

Standards lineage

This document is one revision in a chain of 6 RFCs, each formally replacing the one before it.

  1. RFC 4091 (2005)
  2. RFC 4092 (2005)
  3. RFC 5245 (2010)
  4. RFC 6336 (2011)
  5. RFC 8445 (2018)
  6. RFC 8839 (2021) ✓

Read the full history of Session Description Protocol (SDP) Offer/Answer Procedures for Interactive Connectivity Establishment (ICE) →

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/4092-usage-of-the-session-description-protocol-sdp-alternative-network-address-types