[Fecframe] RFC 6695 on Methods to Convey Forward Error Correction (FEC) Framework Configuration Information
rfc-editor@rfc-editor.org Thu, 02 August 2012 19:01 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 6A9AC11E826B; Thu, 2 Aug 2012 12:01:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.291
X-Spam-Level:
X-Spam-Status: No, score=-102.291 tagged_above=-999 required=5 tests=[AWL=0.309, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 IrjPXcq1AXx6; Thu, 2 Aug 2012 12:01:47 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id E4AA811E825C; Thu, 2 Aug 2012 12:01:46 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 0D03272E026; Thu, 2 Aug 2012 12:01:00 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120802190101.0D03272E026@rfc-editor.org>
Date: Thu, 02 Aug 2012 12:01:00 -0700
Cc: fecframe@ietf.org, rfc-editor@rfc-editor.org
Subject: [Fecframe] RFC 6695 on Methods to Convey Forward Error Correction (FEC) Framework Configuration Information
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: Thu, 02 Aug 2012 19:01:47 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6695
Title: Methods to Convey Forward Error
Correction (FEC) Framework Configuration Information
Author: R. Asati
Status: Informational
Stream: IETF
Date: August 2012
Mailbox: rajiva@cisco.com
Pages: 15
Characters: 34678
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-fecframe-config-signaling-09.txt
URL: http://www.rfc-editor.org/rfc/rfc6695.txt
The Forward Error Correction (FEC) Framework document (RFC 6363)
defines the FEC Framework Configuration Information necessary for
the FEC Framework operation. This document describes how to use
signaling protocols such as the Session Announcement Protocol (SAP),
the Session Initiation Protocol (SIP), the Real Time Streaming
Protocol (RTSP), etc. for determining and communicating the
configuration information between sender(s) and receiver(s).
This document doesn't define any new signaling protocol. This document
is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the FEC Framework Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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