[AVT] RE: I-D ACTION:draft-ash-avt-hc-over-mpls-protocol-00.txt
"Ash, Gerald R \(Jerry\), ALABS" <gash@att.com> Thu, 21 April 2005 22:01 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOjjg-0000Pl-3L; Thu, 21 Apr 2005 18:01:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOjje-0000PY-Eo for avt@megatron.ietf.org; Thu, 21 Apr 2005 18:01:22 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20642 for <avt@ietf.org>; Thu, 21 Apr 2005 18:01:19 -0400 (EDT)
Received: from kcmso2.att.com ([192.128.134.71] helo=kcmso2.proxy.att.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOjv8-0006hE-FW for avt@ietf.org; Thu, 21 Apr 2005 18:13:15 -0400
Received: from attrh5i.attrh.att.com ([135.38.62.12]) by kcmso2.proxy.att.com (AT&T IPNS/MSO-5.5) with ESMTP id j3LLxVKc004675 for <avt@ietf.org>; Thu, 21 Apr 2005 17:01:06 -0500
Received: from kcclust06evs1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (7.2.052) id 426289720014C449 for avt@ietf.org; Thu, 21 Apr 2005 18:01:06 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 21 Apr 2005 17:01:07 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA060CE568@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: I-D ACTION:draft-ash-avt-hc-over-mpls-protocol-00.txt
Thread-Index: AcVGsK+ZB2HmnyVzRdmKlM478mx93gAB+qAA
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: IETF AVT WG <avt@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Content-Transfer-Encoding: quoted-printable
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Subject: [AVT] RE: I-D ACTION:draft-ash-avt-hc-over-mpls-protocol-00.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
Hi All, Please review and comment on the (significantly) updated draft "Protocol Extensions for Header Compression over MPLS" (http://www.ietf.org/internet-drafts/draft-ash-avt-hc-over-mpls-protocol -00.txt). Here is a brief background and overview/explanation of the updates: Work on requirements for header compression over MPLS (http://www.ietf.org/internet-drafts/draft-ietf-avt-hc-mpls-reqs-03.txt) is complete, and work on protocol extensions for header compression over MPLS is underway (previous draft at http://ietf.org/internet-drafts/draft-ash-avt-ecrtp-over-mpls-protocol-0 2.txt). Chartering of the protocol work in the AVT working group has been submitted for approval with the following milestone: Dec 05: Submit any extensions for RTP HC on MPLS networks for Proposed Standard There has been considerable discussion on the previous protocol extensions draft (http://ietf.org/internet-drafts/draft-ash-avt-ecrtp-over-mpls-protocol- 02.txt) in the last couple of months. I presented the update on the header compression over MPLS protocol extensions work at the AVT meeting at IETF-62; slides and minutes are available at https://datatracker.ietf.org/public/proceeding_interim.cgi?meeting_num=6 2 (look under AVT for minutes and slides). The recent discussion and issues regarding the basic approach are summarized in the slides. Header compression experts in the AVT and ROHC working groups wish to re-use, and extend, the existing layer 2 approaches for assignment of context identification (CID) and header compression parameter negotiation. In a multipoint-to-point MPLS environment, one approach would be to have the various header compressors assign CIDs as they do now, with the possible need to resolve CID conflicts/collisions at the header decompressor. Some comments were made that current header compression methods do not have to resolve CID collisions, however the synchronization source (SSRC) assigned in RTP could need collision/conflict resolution. A second approach, suggested by Andy Malis and Loa Andersson, is to use pseudowires and/or targeted LDP to create 'point-to-point' sessions between header compressor and header decompressor, thereby avoiding any issue of CID collision. The disadvantage of this approach is that it requires an additional 4-byte label to be carried with each packet. The updated draft based on the second approach is available at http://www.ietf.org/internet-drafts/draft-ash-avt-hc-over-mpls-protocol- 00.txt. Once again, please review and comment on the updated draft. Thanks, Jerry -----Original Message----- From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org] On Behalf Of Internet-Drafts@ietf.org Sent: Thursday, April 21, 2005 3:39 PM To: i-d-announce@ietf.org Subject: I-D ACTION:draft-ash-avt-hc-over-mpls-protocol-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Protocol Extensions for Header Compression over MPLS Author(s) : J. Ash, et al. Filename : draft-ash-avt-hc-over-mpls-protocol-00.txt Pages : 12 Date : 2005-4-21 VoIP typically uses the encapsulation voice/RTP/UDP/IP. When MPLS labels are added, this becomes voice/RTP/UDP/IP/MPLS-labels. For an MPLS VPN, the packet header is at least 48 bytes, while the voice payload is often no more than 30 bytes, for example. Header compression can significantly reduce the overhead through various compression mechanisms. MPLS is used to route header-compressed (HC) packets over an MPLS LSP without compression/decompression cycles at each router. Such an HC over MPLS capability increases the bandwidth efficiency as well as processing scalability of the maximum number of simultaneous compressed flows that use HC at each router. MPLS pseudowires are used to transport the HC context and other control messages between the ingress and egress MPLS label switched router (LSR), and the pseudowires define a point to point instance of each HC session at the header decompressor. Standard HC methods (e.g., ECRTP, ROHC, etc.) are re-used to determine the context. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ash-avt-hc-over-mpls-protocol- 00.txt _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt
- [AVT] RE: I-D ACTION:draft-ash-avt-hc-over-mpls-p… Ash, Gerald R (Jerry), ALABS
- [AVT] RE: [rohc] RE: I-D ACTION:draft-ash-avt-hc-… Lars-Erik Jonsson (LU/EAB)
- [AVT] RE: I-D ACTION:draft-ash-avt-hc-over-mpls-p… Ash, Gerald R (Jerry), ALABS
- Re: [AVT] RE: I-D ACTION:draft-ash-avt-hc-over-mp… Colin Perkins
- RE: [AVT] RE: I-D ACTION:draft-ash-avt-hc-over-mp… Ash, Gerald R (Jerry), ALABS
- Re: [AVT] RE: I-D ACTION:draft-ash-avt-hc-over-mp… Colin Perkins
- [AVT] RE: I-D ACTION:draft-ash-avt-hc-over-mpls-p… Lars-Erik Jonsson (LU/EAB)