Cell Relay Archive

Cell Relay Retreat>List Archive>month:1999-May> msg00058



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

Re: CBR always 47 byte payload?

  • From: James Carlson <carlson@ironbridgenetworks.com>
  • Date: 17 May 1999 07:36:36 -0400
  • Organization: UltraNet Communications , an RCN Company http://www.ultranet.com/
  • X-Complaints-To: abuse@ultra.net
  • X-Ultra-Time: 17 May 1999 11:36:36 GMT


Rohit Gupta <rogupta@hss.hns.com> writes:
> In that case why does the ATM Forum or ITU-T put this line in first para of the
> AAL1 specs
> 
> "transfer of service data units with a constant source bit rate and the delivery of them
> with the same bit rate"

Because that's what the retiming information in the one octet header
of AAL-1 gives you.  You need that to forward the clocking information
from one end of the pipe to the other.  (The assumption here being
that if you're doing AAL-1, then you're doing it in order to carry
PDH-like circuits over ATM.)

CES assumes a CBR-like service underneath in order to limit the delay
variance enough that a single octet timestamp is sufficient to handle
jitter values.  That doesn't mean you can't use CBR cell scheduling
for other things.

(Theoretically, at least, you could also transfer CES data over a
non-CBR service, as long as the ordering properties and buffering were
sufficient to cover any latency variance.)

-- 
James Carlson, Software Architect                   <carlson@ibnets.com>
IronBridge Networks / 55 Hayden Avenue   71.246W   Vox:  +1 781 372 8132
Lexington MA  02421-7996 / USA           42.423N   Fax:  +1 781 372 8090
"PPP Design and Debugging" --- http://people.ne.mediaone.net/carlson/ppp