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

Re: A Minor NIT


I'm still learning all this SONET stuff so I only claim to be a SONET "white
belt". My understanding of the WIS proposal is as follows:

1) The adjustment space (H3) is 192 bytes total, but that adjustment granularity
is one byte;
2) H3 is not part of the SPE, it is part of the Line Overhead;
3) Whether the SPE is bytes or 66-bit words, no SPE byte or bit
stuffing/deletion actually occurs. Only pointers are adjusted;
4) The payload pointer which is adjusted is contained in H1 and H2, again, part
of the Line Overhead.

Those wearing SONET belts with less color than white should feel free to correct
my understanding above. 

Best Regards,

Wesley Lee wrote:
> Rich & Tom,
> I had thought I understood pretty much everything, but now on the
> issue of pointer adjustment, there may be a problem.  As I understand
> this, if there is a positive adjustment, there is need to to
> byte stuff (or is it 192 * bytes?).  But since the SPE is composed of
> 66-bit code words, how can we stuff the SPE by the 192 bytes. Pls
> correct me if my understanding is wrong.
> -Wesley Lee
> ----------------------------
> Tom,
> Very well said. You echo my understanding also. This implies that SONET/SDH SPE
> pointer adjustment, while operating on byte boundaries, is 100% compatible with
> an SPE payload that is on 66-bit boundaries. Does anyone out there disagree with
> this statement?
> Best Regards,
> Rich
> --
> Thomas Dineen wrote:
> >
> > Gentlepeople:
> >
> > The SPE content is considered bytes when being passed through
> > the SONET network. When the SONET network needs to "adjust"
> > 1 SPE with respect to another SPE in order to account for
> > clock jitter and tolerances, it does so on byte boundaries.
> > This could potentially further separate a 66-bit word. The
> > SONET network also uses byte boundaries to find the OH bytes
> > within a frame.
> >
> >         While I generally agree with the above statement I would
> > like to point out one possible NIT regarding SONET pointer adjustments.
> > I prefer to view, and please feel free to jump in if you disagree, the SONET
> > STS-N Frame structure, and especially its encapsulated SPE structure
> > as a continuous stream. Now pointer adjustments do cause short term
> > instantaneous variances in the data rate, but in the end the average rate
> > will be that of the associated Stratum Clock reference.
> >
> >         A positive pointer adjustment will add one stuff byte, and thus
> > delete
> > one payload byte from this SPE. A negative pointer adjustment will
> > delete one stuff byte, and thus add one payload byte to this SPE,
> > actually the H3. Please note that in either case all of the payload bytes
> > get there, eventually.
> >
> >         But in the end the SPE stream is concatenated together logically
> > to form a continuous stream of bytes. The parsing of 66b encoded frames
> > will occur on this stream of bytes and thus should be un affected by
> > activities at the SONET physical layer including pointer adjustments
> > and frame structure.
> >
> > Thomas Dineen
> --
> ==================================================================
> Lucent Microelectronics Enterprise LAN Division - West
> 1381 McCarthy Blvd, Miltpitas, CA 95035
> Work: 408-952-8822  FAX : 408-952-8887   wlee@xxxxxxxxxx
> ==================================================================
Richard Taborek Sr.                 Phone: 408-845-6102       
Chief Technology Officer             Cell: 408-832-3957
nSerial Corporation                   Fax: 408-845-6114
2500-5 Augustine Dr.        mailto:rtaborek@xxxxxxxxxxx
Santa Clara, CA 95054