RE: draft-ietf-ccamp-lmp-test-sonet-sdh-01.txt

[John Drake <[e-mail]>]

Stephen,

I think there may be some misunderstanding about how the Jx Trace
Correlation actually works.

Normally the Test message is sent in the data plane using the various
SDH/SONET overhead bytes.  However, for backwards compatibility with all
existing SDH/SONET equipment, the Trace Correlation transport mechanism was
introduced.  When it is used, the existing pattern in the overhead bytes of
a particular data link is passed in a Test Message sent over the control
plane.  See below: 

Thanks,

John


0x08 J0-trace: J0 Section Trace Correlation 
         
                Capable of transmitting SONET/SDH Section/RS trace over 
                J0 Section/RS overhead byte as defined in ANSI 
                T1.105/ITU-T G.707. 
                 
                The Test message is not transmitted using the J0 bytes 
                (i.e., over the data link), but is sent over the 
                control channel and correlated for consistency to the 
                received J0 pattern. 
                 
                In order to get the mapping between the Interface_Id 
                over which the J0 test message is sent and the J0 
                pattern sent in-band, the transmitting node must 
                provide the correlation between this pattern and the J0 
                test message.  This correlation is done using the TRACE 
                object as defined in Section 4
.. 
                 
                The format of the test message is as follows: 
                 
                <Test Message> ::= <Common Header> <LOCAL_INTERFACE_ID> 
                <VERIFY_ID> <TRACE> 
                 
                Note that no change is required for the 
                TestStatusSuccess or TestStatusFailure messages. 
                 

> -----Original Message-----
> From: Stephen Trowbridge [mailto:[e-mail]]
> Sent: Monday, March 17, 2003 8:19 PM
> To: ccamp
> Subject: draft-ietf-ccamp-lmp-test-sonet-sdh-01.txt
> 
> 
> All,
> Bert asked me to have a look at this from an ITU-T perspective.
> As I look back through the email archives, I see a number of issues
> that were raised that were never addressed before (or after) a WG last
> call was issued for the -00 draft this document during Dec. 2002.
> There were a number of comments raised with respect to the draft
> in particular from Sept-Nov 2002 that were not addressed. In addition,
> there is the entire thread (2002 archive) "J0/J1 encoding issues" that
> applies to this draft that was never addressed. Perhaps the December
> last call slipped by "under radar" without these issues having been
> addressed.
> 
> I think that the simplest way to resolve the issues is to align
> the draft with ITU-T G.7714.1 (as has Dimitri just did for
> draft-lang-ccamp-lmp-bootstrap-03.txt). Then we have all the documents
> aligned around the same J0/J1 format.
> 
> Once this alignment is done, I think the next question is whether
> draft-ietf-ccamp-lmp-test-sonet-sdh-01.txt contains any extra 
> information
> over what is in ITU-T G.7714.1. If not, perhaps it can just 
> go info track
> if the normative text is in ITU-T G.7714.1.
> Regards,
> Steve
>