[Technical Errata Reported] RFC4666 (2065)
RFC Errata System <[email protected]>
| Newsgroups | gmane.ietf.sigtran |
|---|---|
| Message-ID | <[email protected]> |
The following errata report has been submitted for RFC4666, "Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA)". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=4666&eid=2065 -------------------------------------- Type: Technical Reported by: AMIR KHAN <[email protected]> Section: 3.8.2 Original Text ------------- The Notify message contains the following parameters: Status Mandatory ASP Identifier Conditional Routing Context Optional INFO String Optional Corrected Text -------------- The Notify message contains the following parameters: Status Mandatory ASP Identifier Conditional Routing Context Conditional <Changed> INFO String Optional Notes ----- Considering the scenario below I think the Routing Context in Notify must be conditional. If ASP1 is Actively processing traffic for both AS1(Override) and AS2(Loadshare) and another ASP2 of AS1 becomes ACTIVE. Then I think it becomes mandatory for SG to send Notify message ("Alternate ASP Active") with AS1 Routing Context. ASP1 will use this Notify (containing AS1 Routing Context) to become INACTIVE for AS1, without this AS1 Routing Context ASP1 will become INACTIVE for both AS1 and AS2, which is not desired here. Also please go through mailing list with subject line "M3UA Notification and Routing Context" for more on this. Instructions: ------------- This errata is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC4666 (draft-ietf-sigtran-rfc3332bis-06) -------------------------------------- Title : Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA) Publication Date : September 2006 Author(s) : K. Morneault, Ed., J. Pastor-Balbas, Ed. Category : PROPOSED STANDARD Source : Signaling Transport Area : Real-time Applications and Infrastructure Stream : IETF Verifying Party : IESG