[rfc-dist] RFC 3524 on Mapping of Media Streams to Resource Reservation Flows

[[e-mail] ([e-mail])]

--NextPart


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


        RFC 3324

        Title:      Mapping of Media Streams to Resource Reservation
                    Flows
        Author(s):  G. Camarillo, A. Monrad
        Status:     Standards Track
        Date:       April 2003
        Mailbox:    [e-mail],
                    [e-mail]
        Pages:      6
        Characters: 11249
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-mmusic-reservation-flows-01.txt

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


This document defines an extension to the Session Description Protocol
(SDP) grouping framework.  It allows requesting a group of media
streams to be mapped into a single resource reservation flow.  The SDP
syntax needed is defined, as well as a new "semantics" attribute
called Single Reservation Flow (SRF).

This document is a product of the Multiparty Multimedia Session
Control Working Group of the IETF.

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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
[e-mail].  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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="[e-mail]"

Content-Type: text/plain
Content-ID: <[e-mail]>

RETRIEVE: rfc
DOC-ID: rfc3524

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc3524.txt";
        site="ftp.isi.edu";
        access-type="anon-ftp";
        directory="in-notes"

Content-Type: text/plain
Content-ID: <[e-mail]>

--OtherAccess--
--NextPart--