Re: SONET/SDH Encoding for LMP Test messages

[Dimitri Papadimitriou <[e-mail]>]

hi sidney, this i-d doesn't make any assumption concerning
the "origin" of the Jx trace message field this is why i 
didn't say "provisioned" in my previous reply (i mentioned 
only "available") now concerning its exact value the current
i-d refers to specific technology being used and as such i'd 
say that the concern you've raised is covered (meaning any 
value which is suitable for the specific technology is here
considered as valid) but for clarity it might be useful to 
include also a statement concerning the uniqueness of the 
value as processed by the control plane - thanks for the 
pointer, dimitri.
> 
> Dimitri,
> 
> Some carriers do not provision the trace message, specially 
> the J0 trace. In the case Jx is not provisioned, is the NE
> expected to generate the Jx trace message? If so, the draft 
> should explicitly indicate it and message formats should be 
> suggested for uniqueness (e.g., that specified in Rec. G.831 
> Appendix I).
> 
> Thanks,
> 
> Sidney
> 
> -----Original Message-----
> From: Dimitri Papadimitriou [mailto:[e-mail]]
> Sent: Friday, September 26, 2003 3:01 PM
> To: [e-mail]
> Cc: [e-mail]
> Subject: Re: SONET/SDH Encoding for LMP Test messages
> 
> 
> hi, the Trace Message field value of the TRACE object used 
> in the Test message (and that is sent over the control 
> channel) corresponds to the Jx pattern being sent in-band,
> The Trace Message value is assumed to be available at the 
> transmitter side before the Test message is sent - thanks, 
> dimitri.
> 
> > Dimitri,
> > 
> > Reading the "draft-ietf-ccamp-lmp-test-sonet-sdh-03.txt" I had the
> > impression that Jx Trace messages MUST be provisioned prior to
> > link verification process can take place as described in this document.
> > Is this assumption correct?
> > 
> > Thanks,
> > 
> > Sidney Shiba
> > Fujitsu Network Communications
> > 2801 Telecom Parkway
> > Richardson, TX 75082
> > 
> > 
> > 
> > 
> > 
>