Re: Regarding J0 byte in LMP test message

[Maarten Vissers <mvissers@lucent.com>]

FYI, the use of an ascii string with CR/LF termination for trace identifiers
(e.g. J1) is not longer the recommended approach in SONET. Refer to T1.269-2000.
As per annex B/T1.269 the ascii string with CR/LF termination is to be supported
for interworking with older SONET equipment that only supports the CR/LF format.

Regards,

Maarten 

Nik Langrind wrote:
> 
> Hi,
> 
> One aspect of Bhavesh's question that sparked my interest: CR/LF. I don't
> know whether the IP packet should be followed with a CR/LF or not. It seems
> to me that one ought to follow up the packet with a CR/LF, so that if the
> other end's SONET framer syncs to it, the IP packet will end up sitting in
> the received section trace buffer with the IP Vers/Header Length field in
> the first byte of the buffer.
> 
> On the other hand, one's receive code can't necessarily rely on this, right?
> So when I am testing, anytime I get a stable section trace messages, I ought
> to rotate through every byte, looking for IPV4, and calculating the IP
> header checksum to ensure that I've found the right starting point.
> 
> What are others doing?
> 
> Thanks,
> Nik
> 
> > -----Original Message-----
> > From: Jonathan Lang [mailto:jplang@calient.net]
> > Sent: Thursday, May 16, 2002 1:39 PM
> > To: 'Bhavesh Patel'; 'ccamp@ops.ietf.org'
> > Subject: RE: Regarding J0 byte in LMP test message
> >
> >
> > Bhavesh,
> >   The answers to your questions can be found in Section 14.9
> > of the LMP
> > draft. Please look at the Verify Transport Mechanism.
> >
> > Thanks,
> > Jonathan
> >
> > > -----Original Message-----
> > > From: Bhavesh Patel [mailto:bpatel@fwion.com]
> > > Sent: Thursday, May 16, 2002 5:53 AM
> > > To: 'ccamp@ops.ietf.org'
> > > Cc: Bhavesh Patel
> > > Subject: Regarding J0 byte in LMP test message
> > >
> > >
> > >
> > > Hi,
> > >
> > > I have a question regarding LMP link verification.
> > >
> > > 1)Why did the authors of LMP protocol choose J0 byte for
> > sending test
> > > message when encodingType=sonet? Is it because the OXC/PXC
> > falls in the
> > > section portion of sonet network?
> > > 2) Why the need to make J0 byte IP encoded message? why it
> > cannot be an
> > > ascii string with CR/LF termination similar to J1 byte?
> > > 2) In a metro network application where one deploys PXCs
> > connected point
> > to
> > > point, what does it fall under section/line/path (assume
> > PXC is doing some
> > > O-E-O for lmp test message needs for sending over data
> > bearing links)?
> > > Why not use J1 byte for lmp test message?
> > >
> > > Your replies are appreciated.
> > >
> > > Bhavesh Patel
> > > Embedded Software
> > > bpatel@fwion.com <mailto:bpatel@fwion.com>
> > > 732-946-7400, ext 2087
> > >
> > >
> >
begin:vcard 
n:Vissers;Maarten
tel;cell:+31 62 061 3945
tel;fax:+31 35 687 5976
tel;home:+31 35 526 5463
tel;work:+31 35 687 4270
x-mozilla-html:FALSE
org:Optical Network Group;Lucent Technologies Nederland
version:2.1
email;internet:mvissers@lucent.com
title:Consulting Member of Technical Staff
adr;quoted-printable:;;Botterstraat 45=0D=0A=0D=0A;1271 XL Huizen;;;The Netherlands
fn:Maarten Vissers
end:vcard