RFC 5547 on A Session Description Protocol (SDP) Offer/Answer Mechanism to Enable File Transfer

rfc-editor@rfc-editor.org Tue, 05 May 2009 23:25 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 6026828C282; Tue, 5 May 2009 16:25:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.927
X-Spam-Status: No, score=-16.927 tagged_above=-999 required=5 tests=[AWL=0.072, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id TmEcYE3ckwDJ; Tue, 5 May 2009 16:25:35 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu []) by core3.amsl.com (Postfix) with ESMTP id 22D3A28C2B4; Tue, 5 May 2009 16:25:23 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 662D129C041; Tue, 5 May 2009 16:23:35 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5547 on A Session Description Protocol (SDP) Offer/Answer Mechanism to Enable File Transfer
From: rfc-editor@rfc-editor.org
Message-Id: <20090505232335.662D129C041@bosco.isi.edu>
Date: Tue, 05 May 2009 16:23:35 -0700
Cc: mmusic@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 May 2009 23:25:36 -0000

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

        RFC 5547

        Title:      A Session Description Protocol (SDP) 
                    Offer/Answer Mechanism to Enable File Transfer 
        Author:     M. Garcia-Martin, M. Isomaki,
                    G. Camarillo, S. Loreto,
                    P. Kyzivat
        Status:     Standards Track
        Date:       May 2009
        Mailbox:    miguel.a.garcia@ericsson.com, 
        Pages:      50
        Characters: 112625
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mmusic-file-transfer-mech-11.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5547.txt

This document provides a mechanism to negotiate the transfer of one
or more files between two endpoints by using the Session Description
Protocol (SDP) offer/answer model specified in RFC 3264.  SDP is
extended to describe the attributes of the files to be transferred.
The offerer can describe either the files it wants to send or the
files it would like to receive.  The answerer can either accept or
reject the offer separately for each individual file.  The transfer
of one or more files is initiated after a successful negotiation.
The Message Session Relay Protocol (MSRP) is defined as the default
mechanism to actually carry the files between the endpoints.  The
conventions on how to use MSRP for file transfer are also provided in
this document.  [STANDARDS TRACK]

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

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

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

The RFC Editor Team
USC/Information Sciences Institute