RE: (M2PA) Initial version of M2PA IG is Now Available
"Davidson, Mark" <[email protected]>
| Newsgroups | gmane.ietf.sigtran |
|---|---|
| Message-ID | <[email protected]> |
> > >-----Original Message----- >From: Brian F. G. Bidulock [mailto:[email protected]] >Sent: Thursday, May 25, 2006 6:39 PM >To: Davidson, Mark >Cc: [email protected] >Subject: Re: [Sigtran] (M2PA) Initial version of M2PA IG is Now Available > >Davidson,, > >Davidson, Mark wrote: (Thu, 25 May 2006 08:25:27) >> Brian's objections are the same ones he raised before Jeff's draft was >> even written. >> >> I was at the M2PA plugtest and I will say that most of the issues in >> Jeff's draft did not appear (the one I know of for sure was that not >> everyone had the same initial FSN). But the testing I saw only >> covered basic alignment, traffic handling, processor outage of >> in-service links and congestion. Issues such as processor outage and >> recovery during proving were not tested to my knowledge. > >I agree that it would be a good starting point to strike all items from Jeffery's IG expect the FSN. > Not what I wrote. Please don't put words in my mouth. > >> The additional states introduced by the processor outage recovery >> procedure (waiting for an LSR on stream 1) introduces several issues >> that should be clarified (or failing the link should be an option as >> they really aren't worth the effort required to solve them). > >That was the change made at 48 hours. There is no waiting for LSR state in the RFC. > Waiting for the 2nd LSR after LSPR was changed, but NOT waiting for the first one. This text is still there: "M2PA SHALL cease transmitting User Data messages after sending the Link Status Processor Recovered message, until it has received the Link Status Ready message ..." >> >> Some of the issues in the draft WERE discussed on this list (e.g. >> alignment bugs in Q.703 SDLs) and satisfactory answers were not >> forthcoming. > >Which issues where those? > >I don't think that bugs in SDLs developed by the ITU are within the scope of M2PA. Do you? > M2PA says you can base an implementation on Q.703. If Q.703 has errors that affect operability of M2PA implementations they should be addressed.