The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2003-Feb> msg00023



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

E2E VoIP over MPLS ('VoMPLS') Header Compression

  • From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
  • Date: Wed, 12 Feb 2003 20:21:15 -0500
  • Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, "George Swallow" <swallow@cisco.com>, "Loa Andersson" <loa.andersson@utfors.se>, "GOODE, B (Bur), ALABS" <bgoode@att.com>, "Hand, James C, ALABS" <jameshand@att.com>
  • Thread-Index: AcLS7REDTwK1Hu8ESwOW/VwXhG4KLgABXKbQ
  • Thread-Topic: E2E VoIP over MPLS ('VoMPLS') Header Compression
  • X-MIME-Autoconverted: from quoted-printable to 8bit by cell.onecall.net id h1D1JSP16929

Loa,

> Question:
> Are there any requirements doc on this - there is  a small 
> section in the documents sent out, but it is hardly enough 
> to take a decision.

Yes, Section 4.1 in http://www.ietf.org/internet-drafts/draft-ash-e2e-vompls-hdr-compress-00.txt contains requirements.  In addition, these requirements were specified in slide 3 of the IETF-55/PWE3 presentation http://ietf.org/proceedings/02nov/index.html:

a. need mechanism for end-to-end VoIP over MPLS  CE --> CE header compression
(e.g., from CE1 --> PE1 --> P --> PE2 --> CE2), to provide for efficient voice transport.
b. support various voice encoding (G.729, G.723.1, etc.).
c. compress/decompress header using cRTP (RFC 2508) and/or 'simple' algorithm.
d. operate in RFC2547 VPN context.
e. scalable to very large number of CE --> CE flows.

These additional requirements are added to the next (01) revision of the I-D.  Do you suggest any further elucidation of the requirements?

> Suggestion:
> It is my take that for the time being what should be 
> discussed on the list is whether we want to take this 
> up as a working group task, and whether we should ask 
> ADs and IESG to extend our charter to cover this.

Agreed, that is what I was trying to suggest as well.

Jerry