draft-ietf-sigtran-rfc3332bis-03.txt   draft-ietf-sigtran-rfc3332bis-04.txt 
Network Working Group K. Morneault Network Working Group K. Morneault
INTERNET-DRAFT Cisco Systems INTERNET-DRAFT Cisco Systems
Expires: November 2005 Expires: December 2005
J. Pastor-Balbas J. Pastor-Balbas
Ericsson Ericsson
May 2005 June 2005
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-03.txt> <draft-ietf-sigtran-rfc3332bis-04.txt>
STATUS OF THIS MEMO STATUS OF THIS MEMO
This document is an Internet-Draft and is subject to all provisions This document is an Internet-Draft and is subject to all provisions
of Section 3 of RFC 3667. By submitting this Internet-Draft, each of Section 3 of RFC 3667. By submitting this Internet-Draft, each
author represents that any applicable patent or other IPR claims of author represents that any applicable patent or other IPR claims of
which he or she is aware have been or will be disclosed, and any of which he or she is aware have been or will be disclosed, and any of
which he or she becomes aware will be disclosed, in accordance with which he or she becomes aware will be disclosed, in accordance with
Section 6 of BCP 79. Section 6 of BCP 79.
skipping to change at page 28, line 17 skipping to change at page 28, line 17
The Tag field is a 16-bit identifier of the type of parameter. It The Tag field is a 16-bit identifier of the type of parameter. It
takes a value of 0 to 65534. Common parameters used by adaptation takes a value of 0 to 65534. Common parameters used by adaptation
layers are in the range of 0x00 to 0x3f. M3UA-specific layers are in the range of 0x00 to 0x3f. M3UA-specific
parameters have Tags in the range 0x0200 to 0x02ff. The parameter parameters have Tags in the range 0x0200 to 0x02ff. The parameter
Tags defined are as follows: Tags defined are as follows:
Common Parameters. These TLV parameters are common across the Common Parameters. These TLV parameters are common across the
different adaptation layers: different adaptation layers:
Parameter Name Parameter ID Parameter Name Parameter ID
============== =========== Reserved 0x0000 ============== ============
Reserved 0x0000
Not Used in M3UA 0x0001 Not Used in M3UA 0x0001
Not Used in M3UA 0x0002 Not Used in M3UA 0x0002
Not Used in M3UA 0x0003 Not Used in M3UA 0x0003
INFO String 0x0004 INFO String 0x0004
Not Used in M3UA 0x0005 Not Used in M3UA 0x0005
Routing Context 0x0006 Routing Context 0x0006
Diagnostic Information 0x0007 Diagnostic Information 0x0007
Not Used in M3UA 0x0008 Not Used in M3UA 0x0008
Heartbeat Data 0x0009 Heartbeat Data 0x0009
Not Used in M3UA 0x000a Not Used in M3UA 0x000a
skipping to change at page 95, line 17 skipping to change at page 95, line 17
|<----------------------------------------ASP Act (Ldshr)---| |<----------------------------------------ASP Act (Ldshr)---|
|------------------------------------------ASP Act (Ack)--->| |------------------------------------------ASP Act (Ack)--->|
| | | | | | | |
|-NTFY(AS-ACTIVE)-->| | | |-NTFY(AS-ACTIVE)-->| | |
|-------------------NOTIFY(AS-ACTIVE)-->| | |-------------------NOTIFY(AS-ACTIVE)-->| |
|---------------------------------------NOTIFY(AS-ACTIVE)-->| |---------------------------------------NOTIFY(AS-ACTIVE)-->|
| | | | | | | |
| | | | | | | |
For the Notify message to be sent, the SG maintains knowledge of the For the Notify message to be sent, the SG maintains knowledge of the
minimum ASP resources required (e.g., if the SG knows that "n+k" "2+1" for a Loadshare AS and "n" currently equals "1"). minimum ASP resources required (e.g., if the SG knows that "n+k" =
"2+1" for a Loadshare AS and "n" currently equals "1").
Note: If the SGP detects loss of the ASP1 M3UA peer (e.g., M3UA Note: If the SGP detects loss of the ASP1 M3UA peer (e.g., M3UA
heartbeat loss or detection of SCTP failure), the initial ASP heartbeat loss or detection of SCTP failure), the initial ASP
Inactive message exchange (i.e., SGP-ASP1) would not occur. Inactive message exchange (i.e., SGP-ASP1) would not occur.
5.3 Normal Withdrawal of an ASP from an Application Server 5.3 Normal Withdrawal of an ASP from an Application Server
and Teardown of an Association and Teardown of an Association
An ASP which is now confirmed in the state ASP-INACTIVE (i.e., the An ASP which is now confirmed in the state ASP-INACTIVE (i.e., the
ASP has received an ASP Inactive Ack message) may now proceed to the ASP has received an ASP Inactive Ack message) may now proceed to the
skipping to change at page 101, line 54 skipping to change at page 101, line 54
considered as enough since the response by the other peer can be considered as enough since the response by the other peer can be
considered as a notice that it is in ASP_UP state. considered as a notice that it is in ASP_UP state.
For the same reason, only one ASP Down message is needed since once For the same reason, only one ASP Down message is needed since once
that an IPSP receives ASP_Down ack message it is itself considered as that an IPSP receives ASP_Down ack message it is itself considered as
being in the ASP_Down state and not allowed to receive ASPSM being in the ASP_Down state and not allowed to receive ASPSM
messages. messages.
6. Security Considerations 6. Security Considerations
The security considerations discussed for the 'Security Implementations MUST follow the normative guidance of RFC3788 on
Considerations for SIGTRAN Protocols' RFC 3788 [3] document apply the integration and usage of security mechanisms in SIGTRAN
to this document. protocols.
7. IANA Considerations 7. IANA Considerations
This document contains no actions for IANA. Instead, it is retained This document contains no new actions for IANA. The subsections
for historical purposes. below are retained for historical purposes.
7.1 SCTP Payload Protocol Identifier 7.1 SCTP Payload Protocol Identifier
IANA has assigned an M3UA value for the Payload Protocol Identifier IANA has assigned an M3UA value for the Payload Protocol Identifier
in the SCTP DATA chunk. The following SCTP Payload Protocol in the SCTP DATA chunk. The following SCTP Payload Protocol
Identifier has been registered: Identifier has been registered:
M3UA "3" M3UA "3"
The SCTP Payload Protocol Identifier value "3" SHOULD be included in The SCTP Payload Protocol Identifier value "3" SHOULD be included in
skipping to change at page 108, line 8 skipping to change at page 108, line 8
considered. As an example, for a particular Application Server, the considered. As an example, for a particular Application Server, the
related ASPs could be distributed over at least two Hosts. related ASPs could be distributed over at least two Hosts.
One example of a physical network architecture relevant to SS7 One example of a physical network architecture relevant to SS7
carrier grade operation in the IP network domain is shown in Figure A- carrier grade operation in the IP network domain is shown in Figure A-
1 below: 1 below:
SGs MGCs SGs MGCs
Host#1 ************** ************** Host#3 Host#1 ************** ************** Host#3
* ********__*__________________________*__******** * * *SGP1.1*__*_____ _______________*__* ASP1 * * MGC1 * ********__*__________________________*__******** * =
* *SGP1.1*__*_____ _______________*__* ASP1 * * MGC1
* ******** * \ / * ******** * * ******** * \ / * ******** *
* ********__*______\__/________________*__******** * * ********__*______\__/________________*__******** *
* *SGP2.1*__*_______\/______ _____*__* ASP2 * * * *SGP2.1*__*_______\/______ _____*__* ASP2 * *
* ******** * /\ | | * ******** * * ******** * /\ | | * ******** *
* : * / \ | | * : * * : * / \ | | * : *
* ******** * / \ | | * ******** * * ******** * / \ | | * ******** *
* * SGPn * * | | | | * * ASPn * * * * SGPn * * | | | | * * ASPn * *
* ******** * | | | | * ******** * * ******** * | | | | * ******** *
************** | | | | ************** ************** | | | | **************
| | \ / | | \ /
Host#2 ************** | | \ / ************** Host#4 Host#2 ************** | | \ / ************** Host#4
* ********__*_____| |______\/_______*__******** * * *SGP1.2*__*_________________/\_______*__* ASP1 * * MGC2 * ********__*_____| |______\/_______*__******** * =
* *SGP1.2*__*_________________/\_______*__* ASP1 * * MGC2
* ******** * / \ * ******** * * ******** * / \ * ******** *
* ********__*_______________/ \_____*__******** * * ********__*_______________/ \_____*__******** *
* *SGP2.2*__*__________________________*__* ASP2 * * * *SGP2.2*__*__________________________*__* ASP2 * *
* ******** * * ******** * * ******** * * ******** *
* : * SCTP Associations * : * * : * SCTP Associations * : *
* ******** * * ******** * * ******** * * ******** *
* * SGPn * * * * ASPn * * * * SGPn * * * * ASPn * *
* ******** * * ******** * * ******** * * ******** *
************** ************** ************** **************
 End of changes. 

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