Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

RE: [EFM] EFM Requirements


For the record, the actual stream transport for VoIP is done via RTP/RTCP -
layer protocols. Needless to say, these protocols would rely on the QoS
mechanisms supported at L2/L3. For an example of mapping the MGCP session
descriptions into L2 QoS parameter
sets please see PacketCable 1.0 Dynamic QoS specification at The spec is publicly available.


-----Original Message-----
From: Matt Squire [mailto:mattsquire@xxxxxxx]
Sent: Friday, August 17, 2001 7:07 PM
To: Lough, Andy
Cc: Stds-802-3-Efm (E-mail)
Subject: Re: [EFM] EFM Requirements

Everyone is exploring SIP as a signaling protocol.  So what.  History is
littered with failed explorations.  

Might it happen?  Certainly.  Should we be able to support it if it
does?  Sure.  But SIP is the signaling protocol, it has nothing to do
with the data flow except to set it up.  Our L2 needs to have priorities
and be able to transport low loss/low latency data.  Its Ethernet, it
can.  There is nothing for us to do as far as SIP and Ethernet are

- Matt  

"Lough, Andy" wrote:
> Bob,
> my understanding is that most major carriers in EU are exploring SIP over
IP as their packet voice protocol going forward. So I believe this decision
is made, our focus should be to provide the best layer1/2 package to support
> R's
> Andy