RE: DRN and TID Label Issues - Issue #8

"Haresign Lincoln" <[email protected]>
Newsgroups gmane.ietf.sigtran
Message-ID <849535E338E99741B7F7413F73253EDB04E8BCAF@us-nj-mail1.comverse.com>
Brian,

If an ASP dies, other ASP will be notified with a Notify message.
That's exactly the scenario here.  An ASP sent a message with a
particular local TID.  If it dies (so the response can not be routed), a
Notify is sent when the ASP dies.

Regards,
Lincoln


-----Original Message-----
From: Brian F. G. Bidulock [mailto:[email protected]] 
Sent: Wednesday, October 11, 2006 4:05 PM
To: Haresign Lincoln
Cc: Barry Nagelberg; [email protected]
Subject: [Sigtran] DRN and TID Label Issues - Issue #8

Lincoln,

RFC 3868 says:

4.3.4.5.  Notify Procedures

   A Notify message reflecting a change in the AS state MUST be sent to
   all ASPs in the AS, except those in the ASP-DOWN state, with
   appropriate Status Information and any ASP Identifier of the failed
   ASP.  At the ASP, Layer Management is informed with an M-NOTIFY
   indication primitive.  The Notify message must be sent whether the AS
   state change was a result of an ASP failure or reception of an ASP
   State management (ASPSM) / ASP Traffic Management (ASPTM) message.
   In the second case, the Notify message MUST be sent after any ASP
   State or Traffic Management related acknowledgement messages  (e.g.,
   ASP Up Ack, ASP Down Ack, ASP Active Ack, or ASP Inactive Ack).


Application of DRN/TID label is inconsistent with the adopted
notification procedures.  The SG always notifies the ASPs with a Notify
message when traffic is pending or in danger of being discarded.

DRN/TID has no notification procedure when a ASP Inactive is received
for a necessary label range, nor when an unsolicited ASP Inactive Ack is
sent.

(LOADSEL has a notification procedure BTW.)

--brian

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