draft-ietf-sigtran-rfc3332bis-01.txt   draft-ietf-sigtran-rfc3332bis-02.txt 
Network Working Group K. Morneault Network Working Group K. Morneault
INTERNET-DRAFT Cisco Systems INTERNET-DRAFT Cisco Systems
Expires: March 29, 2004 Expires: April 11, 2004
J. Pastor-Balbas J. Pastor-Balbas
Ericsson Ericsson
September 30, 2004 October 12, 2004
Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) -
User Adaptation Layer (M3UA) User Adaptation Layer (M3UA)
<draft-ietf-sigtran-rfc3332bis-01.txt> <draft-ietf-sigtran-rfc3332bis-02.txt>
STATUS OF THIS MEMO STATUS OF THIS MEMO
By submitting this Internet-Draft, each author certifies that any By submitting this Internet-Draft, each author certifies that any
applicable patent or other IPR claims of which they are aware have applicable patent or other IPR claims of which they are aware have
been disclosed, and any of which they become aware will be disclosed, been disclosed, and any of which they become aware will be disclosed,
in accordance with RFC 3668. in accordance with RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Task Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other Force (IETF), its areas, and its working groups. Note that other
skipping to change at page 29, line 52 skipping to change at page 29, line 52
The following section describes the Transfer messages and parameter The following section describes the Transfer messages and parameter
contents. contents.
3.3.1 Payload Data Message (DATA) 3.3.1 Payload Data Message (DATA)
The DATA message contains the SS7 MTP3-User protocol data, which is The DATA message contains the SS7 MTP3-User protocol data, which is
an MTP-TRANSFER primitive, including the complete MTP3 Routing Label. an MTP-TRANSFER primitive, including the complete MTP3 Routing Label.
The DATA message contains the following variable length parameters: The DATA message contains the following variable length parameters:
Network Appearance Conditional Network Appearance Optional
Routing Context Conditional Routing Context Conditional
Protocol Data Mandatory Protocol Data Mandatory
Correlation Id Optional Correlation Id Optional
The following format MUST be used for the Data Message: The following format MUST be used for the Data Message:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0200 | Length = 8 | | Tag = 0x0200 | Length = 8 |
skipping to change at page 33, line 16 skipping to change at page 33, line 16
to a message from the ASP to an unreachable SS7 destination. As an to a message from the ASP to an unreachable SS7 destination. As an
implementation option the SG may suppress the sending of subsequent implementation option the SG may suppress the sending of subsequent
"response" DUNA messages regarding a certain unreachable SS7 "response" DUNA messages regarding a certain unreachable SS7
destination for a certain period to give the remote side time to destination for a certain period to give the remote side time to
react. If there is no alternate route via another SG, the MTP3-User react. If there is no alternate route via another SG, the MTP3-User
at the ASP is expected to stop traffic to the affected destination at the ASP is expected to stop traffic to the affected destination
via the SG as per the defined MTP3-User procedures. via the SG as per the defined MTP3-User procedures.
The DUNA message contains the following parameters: The DUNA message contains the following parameters:
Network Appearance Conditional Network Appearance Optional
Routing Context Conditional Routing Context Conditional
Affected Point Code Mandatory Affected Point Code Mandatory
INFO String Optional INFO String Optional
The format for DUNA Message parameters is as follows: The format for DUNA Message parameters is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0200 | Length = 8 | | Tag = 0x0200 | Length = 8 |
skipping to change at page 35, line 50 skipping to change at page 35, line 50
indicate that the SG has determined that one or more SS7 destinations indicate that the SG has determined that one or more SS7 destinations
are now reachable (and not restricted), or in response to a DAUD are now reachable (and not restricted), or in response to a DAUD
message if appropriate. If the ASP M3UA layer previously had no message if appropriate. If the ASP M3UA layer previously had no
routes to the affected destinations the ASP MTP3-User protocol is routes to the affected destinations the ASP MTP3-User protocol is
informed and may now resume traffic to the affected destination. The informed and may now resume traffic to the affected destination. The
ASP M3UA layer now routes the MTP3-user traffic through the SG ASP M3UA layer now routes the MTP3-user traffic through the SG
initiating the DAVA message. initiating the DAVA message.
The DAVA message contains the following parameters: The DAVA message contains the following parameters:
Network Appearance Conditional Network Appearance Optional
Routing Context Conditional Routing Context Conditional
Affected Point Code Mandatory Affected Point Code Mandatory
INFO String Optional INFO String Optional
The format and description of the Network Appearance, Routing The format and description of the Network Appearance, Routing
Context, Affected Point Code and INFO String parameters is the same Context, Affected Point Code and INFO String parameters is the same
as for the DUNA message (See Section 3.4.1). as for the DUNA message (See Section 3.4.1).
3.4.3 Destination State Audit (DAUD) 3.4.3 Destination State Audit (DAUD)
The DAUD message MAY be sent from the ASP to the SGP to audit the The DAUD message MAY be sent from the ASP to the SGP to audit the
availability/congestion state of SS7 routes from the SG to one or availability/congestion state of SS7 routes from the SG to one or
more affected destinations. more affected destinations.
The DAUD message contains the following parameters: The DAUD message contains the following parameters:
Network Appearance Conditional Network Appearance Optional
Routing Context Conditional Routing Context Conditional
Affected Point Code Mandatory Affected Point Code Mandatory
INFO String Optional INFO String Optional
The format and description of DAUD Message parameters is the same as The format and description of DAUD Message parameters is the same as
for the DUNA message (See Section 3.4.1). for the DUNA message (See Section 3.4.1).
It is recommended that during normal operation (traffic handling) the It is recommended that during normal operation (traffic handling) the
mask field of the Affected Point Code parameter in the DAUD message is mask field of the Affected Point Code parameter in the DAUD message is
kept to a zero value in order to avoid SG overloading. kept to a zero value in order to avoid SG overloading.
skipping to change at page 36, line 46 skipping to change at page 36, line 46
M3UA layer of an ASP to an M3UA peer indicating that the congestion M3UA layer of an ASP to an M3UA peer indicating that the congestion
level of the M3UA layer or the ASP has changed. level of the M3UA layer or the ASP has changed.
IMPLEMENTATION NOTE: An M3UA node may maintain a timer to control IMPLEMENTATION NOTE: An M3UA node may maintain a timer to control
congestion notification validity, if desired. This timer will be congestion notification validity, if desired. This timer will be
useful in those cases where the peer node fails to indicate useful in those cases where the peer node fails to indicate
congestion abatement. congestion abatement.
The SCON message contains the following parameters: The SCON message contains the following parameters:
Network Appearance Conditional Network Appearance Optional
Routing Context Conditional Routing Context Conditional
Affected Point Code Mandatory Affected Point Code Mandatory
Concerned Destination Optional Concerned Destination Optional
Congestion Indications Optional Congestion Indications Optional
INFO String Optional INFO String Optional
The format for SCON Message parameters is as follows: The format for SCON Message parameters is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
skipping to change at page 38, line 43 skipping to change at page 38, line 43
appropriate national MTP recommendations [7,8]. appropriate national MTP recommendations [7,8].
3.4.5 Destination User Part Unavailable (DUPU) 3.4.5 Destination User Part Unavailable (DUPU)
The DUPU message is used by an SGP to inform concerned ASPs that a The DUPU message is used by an SGP to inform concerned ASPs that a
remote peer MTP3-User Part (e.g., ISUP or SCCP) at an SS7 node is remote peer MTP3-User Part (e.g., ISUP or SCCP) at an SS7 node is
unavailable. unavailable.
The DUPU message contains the following parameters: The DUPU message contains the following parameters:
Network Appearance Conditional Network Appearance Optional
Routing Context Conditional Routing Context Conditional
Affected Point Code Mandatory Affected Point Code Mandatory
User/Cause Mandatory User/Cause Mandatory
INFO String Optional INFO String Optional
The format for DUPU message parameters is as follows: The format for DUPU message parameters is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 40, line 6 skipping to change at page 40, line 6
1 Unequipped Remote User 1 Unequipped Remote User
2 Inaccessible Remote User 2 Inaccessible Remote User
MTP3-User Identity field: 16-bits (unsigned integer) MTP3-User Identity field: 16-bits (unsigned integer)
The MTP3-User Identity describes the specific MTP3-User that is The MTP3-User Identity describes the specific MTP3-User that is
unavailable (e.g., ISUP, SCCP, ...). Some of the valid values for unavailable (e.g., ISUP, SCCP, ...). Some of the valid values for
the MTP3-User Identity are shown below. The values align with the MTP3-User Identity are shown below. The values align with
those provided in the SS7 MTP3 User Part Unavailable message and those provided in the SS7 MTP3 User Part Unavailable message and
Service Indicator. Depending on the MTP3 protocol variant/version Service Indicator. Depending on the MTP3 protocol variant/version
used in the network appearance, additional values may be used. used in the Network Appearance, additional values may be used.
The relevant MTP3 protocol variant/version recommendation is The relevant MTP3 protocol variant/version recommendation is
definitive. definitive.
0 to 2 Reserved 0 to 2 Reserved
3 SCCP 3 SCCP
4 TUP 4 TUP
5 ISUP 5 ISUP
6 to 8 Reserved 6 to 8 Reserved
9 Broadband ISUP 9 Broadband ISUP
10 Satellite ISUP 10 Satellite ISUP
skipping to change at page 41, line 5 skipping to change at page 41, line 5
be informed that traffic to the affected destination can be resumed. be informed that traffic to the affected destination can be resumed.
In this case, the M3UA layer should route the traffic through the SG In this case, the M3UA layer should route the traffic through the SG
initiating the DRST message. initiating the DRST message.
This message is optional for the SG to send and it is optional for This message is optional for the SG to send and it is optional for
the ASP to act on any information received in the message. It is for the ASP to act on any information received in the message. It is for
use in the "STP" case described in Section 1.4.1. use in the "STP" case described in Section 1.4.1.
The DRST message contains the following parameters: The DRST message contains the following parameters:
Network Appearance Conditional Network Appearance Optional
Routing Context Conditional Routing Context Conditional
Affected Point Code Mandatory Affected Point Code Mandatory
INFO String Optional INFO String Optional
The format and description of the Network Appearance, Routing The format and description of the Network Appearance, Routing
Context, Affected Point Code and INFO String parameters is the same Context, Affected Point Code and INFO String parameters is the same
as for the DUNA message (See Section 3.4.1). as for the DUNA message (See Section 3.4.1).
3.5 ASP State Maintenance (ASPSM) Messages 3.5 ASP State Maintenance (ASPSM) Messages
skipping to change at page 84, line 44 skipping to change at page 84, line 44
primitive from the nodal interworking function at an SGP, the SGP primitive from the nodal interworking function at an SGP, the SGP
M3UA layer will send a corresponding SS7 Signalling Network M3UA layer will send a corresponding SS7 Signalling Network
Management (SSNM) DUNA, DAVA, SCON, or DUPU message (see Section 3.4) Management (SSNM) DUNA, DAVA, SCON, or DUPU message (see Section 3.4)
to the M3UA peers at concerned ASPs. The M3UA layer must fill in to the M3UA peers at concerned ASPs. The M3UA layer must fill in
various fields of the SSNM messages consistently with the information various fields of the SSNM messages consistently with the information
received in the primitives. received in the primitives.
The SGP M3UA layer determines the set of concerned ASPs to be informed The SGP M3UA layer determines the set of concerned ASPs to be informed
based on the specific SS7 network for which the primitive indication based on the specific SS7 network for which the primitive indication
is relevant. In this way, all ASPs configured to send/receive traffic is relevant. In this way, all ASPs configured to send/receive traffic
within a particular network appearance are informed. If the SGP within a particular Network Appearance are informed. If the SGP
operates within a single SS7 network appearance, then all ASPs are operates within a single SS7 Network Appearance, then all ASPs are
informed. informed.
For the particular case that an ASP becomes active for an AS and For the particular case that an ASP becomes active for an AS and
destinations normally accessible to the AS are inaccessible, destinations normally accessible to the AS are inaccessible,
restricted or congested, the SG MAY send DUNA, DRST or SCON messages restricted or congested, the SG MAY send DUNA, DRST or SCON messages
for the inaccessible, restricted or congested destinations to the ASP for the inaccessible, restricted or congested destinations to the ASP
newly active for the AS to prevent the ASP from sending traffic for newly active for the AS to prevent the ASP from sending traffic for
destinations that it might otherwise not know that are inaccessible, destinations that it might otherwise not know that are inaccessible,
restricted or congested. For the newly activating ASP from which the restricted or congested. For the newly activating ASP from which the
SGP has received an ASP Active message, these DUNA, DRST and SCON SGP has received an ASP Active message, these DUNA, DRST and SCON
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/