Re: (M2PA) Initial version of M2PA IG is Now Available

"Brian F. G. Bidulock" <[email protected]>
Newsgroups gmane.ietf.sigtran
Organization http://www.openss7.org/
Message-ID <[email protected]>
Andrew,

Andrew Booth wrote:                          (Mon, 29 May 2006 16:03:59)
>
> I think the RFC does (implicitly) say to ignore LS Ready during proving.
> If I recall correctly, MTP2 (q.703/T1.111.3) ignores FISU during
> proving. Hence in the absence of specific text, M2PA should ignore LS
> Ready during proving.

Well, no, but it explicitly says:

   The Link Status Ready message replaces the FISU of MTP2 that is sent
   at the end of the proving period.  The Link Status Ready message is
   used to verify that both ends have completed proving.  When M2PA
   starts timer T1, it SHALL send a Link Status Ready message to its
   peer in the case where MTP2 would send a FISU after proving is
   complete.  If the Link Status Ready message is sent, then M2PA MAY
   send additional Link Status Ready messages while timer T1 is running.
   These Link Status Ready messages are sent on the Link Status stream.

   In the case that MTP2 sends an MSU or SIPO message at the end of
   proving, M2PA SHALL send (respectively) a User Data or Link Status
   Processor Outage message.

How about changing the one line

   peer in the case where MTP2 would send a FISU after proving is

to

   peer in the case where MTP2 would send FISU(s) after proving is

Is that satisfactory?  I don't think that it merits changing a page
of text, possibly breaking other things.  Particularly when a M2PA
link that ignores LSR will not even align with itself.

(I'll reply separately on the second part.)

--brian

-- 
Brian F. G. Bidulock
[email protected]
http://www.openss7.org/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.