[AVT] RE: I-D ACTION:draft-ash-avt-hc-over-mpls-protocol-01.txt

"Ash, Gerald R \(Jerry\), ALABS" <gash@att.com> Fri, 08 July 2005 16:33 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DqvnJ-00034f-47; Fri, 08 Jul 2005 12:33:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DqvnI-00034a-Gp for avt@megatron.ietf.org; Fri, 08 Jul 2005 12:33:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26256 for <avt@ietf.org>; Fri, 8 Jul 2005 12:33:38 -0400 (EDT)
Received: from mail120.messagelabs.com ([216.82.255.211]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1DqwEc-0004T4-PR for avt@ietf.org; Fri, 08 Jul 2005 13:02:01 -0400
X-VirusChecked: Checked
X-Env-Sender: gash@att.com
X-Msg-Ref: server-9.tower-120.messagelabs.com!1120840402!3339395!1
X-StarScan-Version: 5.4.15; banners=-,-,-
X-Originating-IP: [192.128.167.69]
Received: (qmail 15588 invoked from network); 8 Jul 2005 16:33:23 -0000
Received: from almso1.att.com (HELO almso1.proxy.att.com) (192.128.167.69) by server-9.tower-120.messagelabs.com with SMTP; 8 Jul 2005 16:33:23 -0000
Received: from attrh3i.attrh.att.com ([135.38.62.9]) by almso1.proxy.att.com (AT&T IPNS/MLO-6.0) with ESMTP id j68GX7Px011244 for <avt@ietf.org>; Fri, 8 Jul 2005 12:33:22 -0400
Received: from kcclust06evs1.ugd.att.com (135.38.164.89) by attrh3i.attrh.att.com (7.2.052) id 42BED27600262564 for avt@ietf.org; Fri, 8 Jul 2005 12:33:22 -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: Fri, 08 Jul 2005 11:33:22 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA060CE668@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: I-D ACTION:draft-ash-avt-hc-over-mpls-protocol-01.txt
Thread-Index: AcWD0YbHU77AD7LDTN2AdZ1EHqnoVgAAEz7A
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: IETF AVT WG <avt@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
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-01.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
-01.txt).

Note that a work item and milestone were recently added to the AVT
charter on this work:

"- in collaboration with the MPLS and ROHC WGs, to develop a solution
for header compression of RTP across MPLS networks that avoid
decompression and compression at each MPLS node.
...
Dec 05 Submit any extensions for RTP HC on MPLS networks for Proposed
Standard" 

The updated I-D responds to comments on the AVT list from Lars-Erik
Jonsson and Colin Perkins:

http://www1.ietf.org/mail-archive/web/avt/current/msg05408.html
http://www1.ietf.org/mail-archive/web/avt/current/msg05419.html
http://www1.ietf.org/mail-archive/web/avt/current/msg05428.html
http://www1.ietf.org/mail-archive/web/avt/current/msg05433.html
http://www1.ietf.org/mail-archive/web/avt/current/msg05530.html

The main changes are as follows:

1. Lars-Erik's suggested outline is used, in particular:
   - Section 2 'Terminology' is added
   - Section 3 'Header Compression over MPLS Protocol Overview' is added
   - Section 4 'Protocol Specifications' is reorganized
2. Pseudowire (PW) setup and header compression session configuration
are covered in Sections 3.1 and 4.1.  In particular, the PW Interface
Parameters Sub-TLV is used to signal header compression session setup
and header compression parameter negotiation, such as described for
header-compression-over-PPP mechanisms [RFC3241, RFC3544].
3. Encapsulation of header compressed packets is covered in Sections 3.2
and 4.2.  See in particular Figure 3 illustrating 'Header Compression
over MPLS Media Stream Transport'.
4. A PW type has been assigned to each header compression scheme, as
discussed in Section 4.1 and [IANA]
(http://ietf.org/internet-drafts/draft-ietf-pwe3-iana-allocation-11.txt)
.

Once again, please review and comment on the updated draft.  It will be
good to have some discussion on the list in anticipation of proposing
this as an AVT WG document at the IETF-63/AVT meeting.

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: Friday, July 08, 2005 10:50 AM
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-ash-avt-hc-over-mpls-protocol-01.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-01.txt
	Pages		: 17
	Date		: 2005-7-8
	
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 typically 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-
01.txt

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt