Skip to main content

Conventions for the use of the Session Description Protocol (SDP) for ATM Bearer Connections
draft-ietf-mmusic-sdp-atm-05

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3108.
Authors Mohamed Mostafa , Rajesh Kumar
Last updated 2020-01-21 (Latest revision 2001-02-02)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Formats
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Became RFC 3108 (Proposed Standard)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)
draft-ietf-mmusic-sdp-atm-05
A new Request for Comments is now available in online RFC libraries.

        RFC 3108

        Title:      Conventions for the use of the Session Description
                    Protocol (SDP) for ATM Bearer Connections
        Author(s):  R. Kumar, M. Mostafa
        Status:     Standards Track
        Date:       May 2001
        Mailbox:    rkumar@cisco.com, mmostafa@cisco.com
        Pages:      111
        Characters: 248037
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-mmusic-sdp-atm-05.txt

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

This document describes conventions for using the Session Description
Protocol (SDP) described in RFC 2327 for controlling ATM Bearer
Connections, and any associated ATM Adaptation Layer (AAL).  The AALs
addressed are Type 1, Type 2 and Type 5.  This list of conventions is
meant to be exhaustive.  Individual applications can use subsets of
these conventions.  Further, these conventions are meant to comply
strictly with the SDP syntax as defined in RFC 2327.

This document is a product of the Multiparty Multimedia Session
Control 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.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.