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

A new Request for Comments is now available in online RFC libraries.

        RFC 4092

        Title:      Usage of the Session Description Protocol (SDP)
                    Alternative Network Address Types (ANAT) Semantics
                    in the Session Initiation Protocol (SIP)
        Author(s):  G. Camarillo, J. Rosenberg
        Status:     Standards Track
        Date:       June 2005
        Mailbox:    Gonzalo.Camarillo@ericsson.com, jdrosen@cisco.com
        Pages:      6
        Characters: 12624
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sip-anat-usage-00.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4092.txt

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.

This document is a product of the Session Initiation Protocol Working
Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.