[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [AVT] RE: I-D ACTION:draft-ash-avt-ecrtp-over-mpls-protocol-00.txt
--- a a <yourf@yahoo.com> wrote:
> Hi,
>
> It looks pretty good. I have a question rather than
> a
> comment:
>
> In this draft we are trying to add some new objects
> to
> the base RSVP-TE. RSVP or RSVP-TE so far have been
> kept immune from the applications that could make
> use
> of it. So, why are we planning to add something like
> "VoIP-CallIds" instead of some generic name or
> identifier that could be used by different
> applications in different contexts? The L3PID anyway
> would define the kind of the payload being carried
> and
> applications would be free to interpret that
> "generic
> identifier" in the fashion they want. (Pls. excuse
> me
> if I'm not privy to some information or earlier
> discussions).
>
> Today we have SIP (in VoIP networks) and that's why
> usage of VoIP-CallIds may be justified in some sense
> but tomorrow there could be some other protocol
> (that
> may use some other identifier instead of callId) and
> hence we may have to accomodate that as well.
>
> The other minor comments that I have are:
> * Though the draft states that packet type field
> would
> be prepended to the "packet formats" defined in
> ECRTP
> (RFC3545), a pictoral representation would be
> useful.
>
> * Most of the SIP RFCs and SIP drafts have
> associated
> example "Call Flows" with DETAILED message contents
> -
> either in separate drafts/RFCs or in Appendix
> sections
> to the main RFC/drafts. Can we do something similar
> for this draft as well? (It has some message
> seuqence
> shown but it's not that detailed). It would be
> useful
> to see the data plane encodings as well (with label
> stacks, packet types and compressed payloads etc.).
>
> Thanks.
>
>
>
>
> --- "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
> wrote:
> > All,
> >
> > Please review and comment on 'Protocol Extensions
> > for ECRTP over MPLS'
> >
>
http://www.ietf.org/internet-drafts/draft-ash-avt-ecrtp-over-mpls-protocol-00.txt.
> > The protocol extensions enable the use of MPLS to
> > route enhanced compressed RTP (ECRTP) compressed
> > packets over an MPLS LSP without
> > compression/decompression cycles at each router.
> >
> > The proposed extensions are based on the
> > requirements documented in 'Requirements for ECRTP
> > over MPLS'
> >
>
http://www.ietf.org/internet-drafts/draft-ash-avt-ecrtp-over-mpls-reqs-01.txt.
> >
> > Thanks,
> > Jerry
> >
> > -----Original Message-----
> > From: Internet-Drafts@ietf.org
> > [mailto:Internet-Drafts@ietf.org]
> > Sent: Thursday, February 05, 2004 3:43 PM
> > Subject: I-D
> >
> ACTION:draft-ash-avt-ecrtp-over-mpls-protocol-00.txt
> >
> > A New Internet-Draft is available from the on-line
> > Internet-Drafts directories.
> >
> >
> > Title : Protocol Extensions for ECRTP over MPLS
> > Author(s) : J. Ash
> > Filename :
> > draft-ash-avt-ecrtp-over-mpls-protocol-00.txt
> > Pages : 0
> > Date : 2004-2-5
> >
> > 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. VoIP header
> > compression can
> > significantly reduce the VoIP overhead through
> > various compression
> > mechanisms, such as enhanced compressed RTP
> (ECRTP).
> > We consider using
> > MPLS to route ECRTP compressed packets over an
> MPLS
> > LSP without
> > compression/decompression cycles at each router.
> > Such an ECRTP over MPLS
> > capability can increase the bandwidth efficiency
> as
> > well as processing
> > scalability of the maximum number of simultaneous
> > VoIP flows that use
> > header compression at each router. In this draft
> we
> > propose to use
> > RSVP-TE extensions to signal the header
> compression
> > context and other
> > control messages between the ingress and egress
> LSR.
> > We re-use the
> > methods in ECRTP to determine the context.
> >
> > A URL for this Internet-Draft is:
> >
>
http://www.ietf.org/internet-drafts/draft-ash-avt-ecrtp-over-mpls-protocol-00.txt.
> >
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www1.ietf.org/mailman/listinfo/avt
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Finance: Get your refund fast by filing
> online.
> http://taxes.yahoo.com/filing.html
__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html
_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt