RE: M2PA: BSN processing when FSN out of order

"Newman, Catherine J" <[email protected]>
Newsgroups gmane.ietf.sigtran
Message-ID <A09345776B6C7A4985573569C0F300430F9FE40B@rrc-dte-exs01.dte.telcordia.com>
For MTP2, per ANSI, the BSN would still be processed in the case of a
received MSU with an invalid FSN [see T1.111.3, Section 6.2.2, or SDL
Figure 14/Sheet 2&3] even though the message is discarded.  

Can you confirm if this is the intended behavior for M2PA? I didn't see
where this specifically addressed in the M2PA RFC; if it is, please let
me know where.

Thanks,
Cathy Newman

-----Original Message-----
From: Brian F. G. Bidulock [mailto:[email protected]] 
Sent: Thursday, June 22, 2006 4:18 PM
To: Davidson, Mark
Cc: Kanode, Mark; [email protected]
Subject: Re: [Sigtran] M2PA: BSN processing when FSN out of order

Mark,

Davidson, Mark wrote:                         (Thu, 22 Jun 2006
09:03:02)
> 
>    Why does the above requirement exist if M2PA does not retransmit?
> 

See "M2PA Last Call Comment - FSN" from July 14, 2003 (copied below):

| From [email protected]  Mon Jul 14 04:05:05 2003
| From: "Brian F. G. Bidulock" <[email protected]>
| Organization: http://www.openss7.org/
| To: "'[email protected]'" <[email protected]>
| Date: Mon, 14 Jul 2003 04:04:30 -0600
| Subject: [Sigtran] M2PA Last Call Comment - FSN
| 
| M2PA-09 says:
| 
|   If M2PA receives a User Data message with an FSN that is out of
order,
|   M2PA SHALL place the link out of service (see section 4.1.6 Link Out
|   of Service).
| 
| This conflicts with Q.703 that ignores an MSU that contains an FSN
that
| is other than the next expected FSN (i.e, out of order).  This makes
it
| difficult to implement (and is probably the last thing standing in the
| way of implementing) something like the following (that was requested
by
| ITU):
| 
|                            _________________
|                           |                 |
|                           |       IWF       |
|                           |_________________|
|                           |        |        |
|                           |  MTP2  |  M2PA  |
|                           |________|________|
|                                |       |
|                            ____|       |___
| 
| If M2PA discards the message as Q.703 does, and the other end of the
| link was actually broken, the link will be go out of service in due
| course anyway.
| 
| Change to:
| 
|   If M2PA receives a User Data message with an FSN that is out of
order,
|   M2PA SHALL discard the message.
| 
| --brian
| 
| -- 
| Brian F. G. Bidulock
| [email protected]
| http://www.openss7.org/
| 
| _______________________________________________
| Sigtran mailing list
| [email protected]
| https://www1.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
[email protected]
http://www.openss7.org/

_______________________________________________
Sigtran mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/sigtran
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.