[Fecframe] FW: New Version Notification for draft-ietf-fecframe-sdp-elements-10

"Ali C. Begen (abegen)" <abegen@cisco.com> Sat, 09 October 2010 15:35 UTC

Return-Path: <abegen@cisco.com>
X-Original-To: fecframe@core3.amsl.com
Delivered-To: fecframe@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D106D3A6868 for <fecframe@core3.amsl.com>; Sat, 9 Oct 2010 08:35:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.555
X-Spam-Level:
X-Spam-Status: No, score=-10.555 tagged_above=-999 required=5 tests=[AWL=0.044, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SofzvnUM2gAA for <fecframe@core3.amsl.com>; Sat, 9 Oct 2010 08:35:43 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id F41943A67EF for <fecframe@ietf.org>; Sat, 9 Oct 2010 08:35:13 -0700 (PDT)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: An0FAEcosEyrR7Ht/2dsb2JhbACDH5EqjSBbcZ47ihmSE4EigzF0BIRRiHc
X-IronPort-AV: E=Sophos;i="4.57,308,1283731200"; d="scan'208";a="601571570"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-6.cisco.com with ESMTP; 09 Oct 2010 15:36:16 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o99FaG8x004772 for <fecframe@ietf.org>; Sat, 9 Oct 2010 15:36:16 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Sat, 9 Oct 2010 08:36:16 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
Date: Sat, 09 Oct 2010 08:36:11 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D540D5BF354@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <20101009153240.08D203A68BE@core3.amsl.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: New Version Notification for draft-ietf-fecframe-sdp-elements-10
Thread-Index: Actnx3cd312uDQ1MQomlDQgKJoPsWAAAAtsg
References: <20101009153240.08D203A68BE@core3.amsl.com>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: fecframe@ietf.org
X-OriginalArrivalTime: 09 Oct 2010 15:36:16.0668 (UTC) FILETIME=[B66905C0:01CB67C7]
Subject: [Fecframe] FW: New Version Notification for draft-ietf-fecframe-sdp-elements-10
X-BeenThere: fecframe@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of FEC Framework <fecframe.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 09 Oct 2010 15:35:46 -0000

This version should address all the outstanding comments from the IESG.

For diff, please see:
https://datatracker.ietf.org/doc/draft-ietf-fecframe-sdp-elements/#history 

-acbegen

-----Original Message-----
From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org] 
Sent: Saturday, October 09, 2010 11:33 PM
To: Ali C. Begen (abegen)
Subject: New Version Notification for draft-ietf-fecframe-sdp-elements-10 


A new version of I-D, draft-ietf-fecframe-sdp-elements-10.txt has been successfully submitted by Ali Begen and posted to the IETF repository.

Filename:	 draft-ietf-fecframe-sdp-elements
Revision:	 10
Title:		 Session Description Protocol Elements for FEC Framework
Creation_date:	 2010-10-09
WG ID:		 fecframe
Number_of_pages: 19

Abstract:
This document specifies the use of 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.
                                                                                  


The IETF Secretariat.