Session Description Protocol (SDP) Simple Capability Declaration

Versions: 00 01 02 03 04 05 rfc3407                      Standards Track
A new Request for Comments is now available in online RFC libraries.

        RFC 3407

        Title:      Session Description Protocol (SDP)
                    Simple Capability Declaration
        Author(s):  F. Andreasen
        Status:     Standards Track
        Date:       October 2002
        Pages:      10
        Characters: 21133
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-andreasen-mmusic-sdp-simcap-05.txt


This document defines a set of Session Description Protocol (SDP)
attributes that enables SDP to provide a minimal and backwards
compatible capability declaration mechanism.  Such capability
declarations can be used as input to a subsequent session
negotiation, which is done by means outside the scope of this
document.  This provides a simple and limited solution to the general
capability negotiation problem being addressed by the next
generation of SDP, also known as SDPng.

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

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.echo
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.