RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

RFC 4666, "Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA)", September 2006

Source of RFC: sigtran (rai)

Errata ID: 2065
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT

Reported By: AMIR KHAN
Date Reported: 2010-03-04
Held for Document Update by: Robert Sparks

Section 3.8.2 says:

The Notify message contains the following parameters:

      Status                     Mandatory
      ASP Identifier             Conditional
      Routing Context            Optional
      INFO String                Optional

It should say:

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.

Report New Errata



Advanced Search