[Fecframe] RFC 6364 on Session Description Protocol Elements for the Forward Error Correction (FEC) Framework

rfc-editor@rfc-editor.org Sat, 15 October 2011 01:38 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: fecframe@ietfa.amsl.com
Delivered-To: fecframe@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 727FC21F8CFD; Fri, 14 Oct 2011 18:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.788
X-Spam-Level:
X-Spam-Status: No, score=-101.788 tagged_above=-999 required=5 tests=[AWL=-0.711, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, J_CHICKENPOX_93=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z4NJ58lMrK-O; Fri, 14 Oct 2011 18:38:05 -0700 (PDT)
Received: from rfc-editor.org (rfcpa.amsl.com [12.22.58.47]) by ietfa.amsl.com (Postfix) with ESMTP id 4102121F8D0B; Fri, 14 Oct 2011 18:38:05 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3381298C294; Fri, 14 Oct 2011 18:38:05 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20111015013805.3381298C294@rfc-editor.org>
Date: Fri, 14 Oct 2011 18:38:05 -0700
Cc: fecframe@ietf.org, rfc-editor@rfc-editor.org
Subject: [Fecframe] RFC 6364 on Session Description Protocol Elements for the Forward Error Correction (FEC) Framework
X-BeenThere: fecframe@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of FEC Framework <fecframe.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/fecframe>, <mailto:fecframe-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/fecframe>
List-Post: <mailto:fecframe@ietf.org>
List-Help: <mailto:fecframe-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/fecframe>, <mailto:fecframe-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Oct 2011 01:38:06 -0000

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

        
        RFC 6364

        Title:      Session Description Protocol Elements for 
                    the Forward Error Correction (FEC) Framework 
        Author:     A. Begen
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2011
        Mailbox:    abegen@cisco.com
        Pages:      18
        Characters: 36160
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-fecframe-sdp-elements-11.txt

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

This document specifies the use of the Session Description Protocol
(SDP) to describe the parameters required to signal the Forward Error
Correction (FEC) Framework Configuration Information between the
sender(s) and receiver(s).  This document also provides examples that
show the semantics for grouping multiple source and repair flows
together for the applications that simultaneously use multiple
instances of the FEC Framework.  [STANDARDS-TRACK]

This document is a product of the FEC Framework 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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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
Association Management Solutions, LLC