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

[Dimitri Papadimitriou <dpapadimitriou@psg.com>]

hi steve,
 
> All,
> Bert asked me to have a look at this from an ITU-T perspective.

what does that really mean ?

> 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.

would you please share with us this list of issues that were not
addressed

> There were a number of comments raised with respect to the draft
> in particular from Sept-Nov 2002 that were not addressed. 

we are not aware of any lmp sonet-sdh i-d comments that haven't been 
addressed since so far (even after this i-d passed the last call)
 
> 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.

or the people that raised these issues are satisfied with the answers

> 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.

the IETF lmp sonet-sdh link verification is compliant with G.707

hope this clarifies,

regards,
- dimitri.

> Regards,
> Steve
> 
>