draft-ietf-sigtran-m2ua-11.txt   draft-ietf-sigtran-m2ua-12.txt 
skipping to change at page 1, line 15 skipping to change at page 1, line 15
NetRake NetRake
Greg Sidebottom Greg Sidebottom
gregside consulting gregside consulting
Tom George Tom George
Alcatel Alcatel
Brian Bidulock Brian Bidulock
OpenSS7 OpenSS7
Jacob Heitz Jacob Heitz
Lucent Lucent
Expires in May 2002 Nov 2001 Expires in May 2002 Dec 2001
SS7 MTP2-User Adaptation Layer Signaling System 7 (SS7) Message Transfer Part (MTP) 2 -
<draft-ietf-sigtran-m2ua-11.txt> User Adaptation Layer
<draft-ietf-sigtran-m2ua-12.txt>
Status of This Memo Status of This Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC 2026. Internet-Drafts are working provisions of Section 10 of RFC 2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups MAY also distribute and its working groups. Note that other groups MAY also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
skipping to change at page 16, line 48 skipping to change at page 16, line 48
8 (0x08) Interface Identifier (Integer Range) 8 (0x08) Interface Identifier (Integer Range)
9 (0x09) Heartbeat Data 9 (0x09) Heartbeat Data
10 (0x0a) Unused 10 (0x0a) Unused
11 (0x0b) Traffic Mode Type 11 (0x0b) Traffic Mode Type
12 (0x0c) Error Code 12 (0x0c) Error Code
13 (0x0d) Status Type/Information 13 (0x0d) Status Type/Information
14 (0x0e) Unused 14 (0x0e) Unused
15 (0x0f) Unused 15 (0x0f) Unused
16 (0x10) Unused 16 (0x10) Unused
17 (0x11) ASP Identifier 17 (0x11) ASP Identifier
18 (0x12) Unused
19 (0x13) Correlation Id
18-255 Reserved 18-255 Reserved
The M2UA specific parameter Tags defined are as follows: The M2UA specific parameter Tags defined are as follows:
Parameter Value Parameter Name Parameter Value Parameter Name
--------------- -------------- --------------- --------------
768 (0x0300) Protocol Data 1 768 (0x0300) Protocol Data 1
769 (0x0301) Protocol Data 2 (TTC) 769 (0x0301) Protocol Data 2 (TTC)
770 (0x0302) State Request 770 (0x0302) State Request
771 (0x0303) State Event 771 (0x0303) State Event
skipping to change at page 16, line 71 skipping to change at page 17, line 4
775 (0x0307) Sequence Number 775 (0x0307) Sequence Number
776 (0x0308) Retrieval Result 776 (0x0308) Retrieval Result
777 (0x0309) Link Key 777 (0x0309) Link Key
778 (0x030a) Local-LK-Identifier 778 (0x030a) Local-LK-Identifier
779 (0x030b) Signalling Data Terminal (SDT) Identifier 779 (0x030b) Signalling Data Terminal (SDT) Identifier
780 (0x030c) Signailng Data Link (SDL) Identifier 780 (0x030c) Signailng Data Link (SDL) Identifier
781 (0x030d) Registration Result 781 (0x030d) Registration Result
782 (0x030e) Registration Status 782 (0x030e) Registration Status
783 (0x030f) De-Registration Result 783 (0x030f) De-Registration Result
784 (0x0310) De-Registration Status 784 (0x0310) De-Registration Status
785 (0x0311) Correlation Id
786 (0x0312) Correlation Id Ack
Parameter Length: 16 bits (unsigned integer) Parameter Length: 16 bits (unsigned integer)
The Parameter Length field contains the size of the parameter in The Parameter Length field contains the size of the parameter in
bytes, including the Parameter Tag, Parameter Length, and Parameter bytes, including the Parameter Tag, Parameter Length, and Parameter
Value fields. Thus, a parameter with a zero-length Parameter Value Value fields. Thus, a parameter with a zero-length Parameter Value
field would have a Length field of 4. The Parameter Length does not field would have a Length field of 4. The Parameter Length does not
include any padding bytes. include any padding bytes.
Parameter Value: variable-length. Parameter Value: variable-length.
skipping to change at page 19, line 16 skipping to change at page 19, line 16
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 (0x301) | Length | | Tag (0x301) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ Protocol Data / \ Protocol Data /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x311) | Length = 8 | | Tag (0x13) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation Id | | Correlation Id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Protocol Data field contains the MTP2-User application message in The Protocol Data field contains the MTP2-User application message in
network byte order starting with the Length Indicator (LI) octet. network byte order starting with the Length Indicator (LI) octet.
The Japanese TTC variant uses the spare bits of the LI octet for The Japanese TTC variant uses the spare bits of the LI octet for
priority. The length of the Protocol Data MUST NOT exceed the length priority. The length of the Protocol Data MUST NOT exceed the length
of a MTP2-User application message [2] [3]. of a MTP2-User application message [2] [3].
skipping to change at page 19, line 42 skipping to change at page 19, line 42
The Data Acknowledge message contains the following parameter: The Data Acknowledge message contains the following parameter:
Correlation Id Mandatory Correlation Id Mandatory
The following format MUST be used for the Data Ack Message: The following format MUST be used for the Data Ack 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 (0x312) | Length = 8 | | Tag (0x13) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation Id | | Correlation Id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Correlation Id parameter of the Data message and the Data Ack The Correlation Id parameter of the Data message and the Data Ack
message provide a mechanism, for those SG implementations capable for message provide a mechanism, for those SG implementations capable for
taking advantage of them, to obtain an acknowledgement that the MSU taking advantage of them, to obtain an acknowledgement that the MSU
has been transferred to the M2UA peer before acknowleding the MSU to has been transferred to the M2UA peer before acknowleding the MSU to
the SS7 peer, removing the risk of losing messages due to association the SS7 peer, removing the risk of losing messages due to association
failure or SCTP congestion. failure or SCTP congestion.
skipping to change at page 26, line 49 skipping to change at page 26, line 49
identified for its use but the INFO String MAY be used for debugging identified for its use but the INFO String MAY be used for debugging
purposes. purposes.
3.3.2.2 ASP Up Ack 3.3.2.2 ASP Up Ack
The ASP Up Ack message is used to acknowledge an ASP Up message The ASP Up Ack message is used to acknowledge an ASP Up message
received from a remote M2UA peer. received from a remote M2UA peer.
The ASPUP Ack message contains the following parameters: The ASPUP Ack message contains the following parameters:
ASP Identifier (optional)
INFO String (optional) INFO String (optional)
The format for ASPUP Ack Message parameters is as follows: The format for ASPUP Ack 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 (0xe) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASP Identifier* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length | | Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ INFO String* / \ INFO String* /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
If the ASPUP message contains an ASP Identifer, the ASPUP Ack will
reflect the ASP Identifier back to the ASP.
The format and description of the optional Info String parameter is the The format and description of the optional Info String parameter is the
same as for the ASP UP message (See Section 3.3.2.1). same as for the ASP UP message (See Section 3.3.2.1).
3.3.2.3 ASP Down (ASPDN) 3.3.2.3 ASP Down (ASPDN)
The ASP Down (ASPDN) message is used to indicate to a remote M2UA peer The ASP Down (ASPDN) message is used to indicate to a remote M2UA peer
that the adaptation layer is not ready to receive traffic or that the adaptation layer is not ready to receive traffic or
maintenance messages. maintenance messages.
The ASPDN message contains the following parameters The ASPDN message contains the following parameters
skipping to change at page 32, line 29 skipping to change at page 32, line 29
The format and description of the optional Info String parameter is the The format and description of the optional Info String parameter is the
same as for the ASP UP message (See Section 3.3.2.1). same as for the ASP UP message (See Section 3.3.2.1).
3.3.2.8 ASP Active Ack 3.3.2.8 ASP Active Ack
The ASP Active (ASPAC) Ack message is used to acknowledge an ASP Active The ASP Active (ASPAC) Ack message is used to acknowledge an ASP Active
message received from a remote M2UA peer. message received from a remote M2UA peer.
The ASPAC Ack message contains the following parameters: The ASPAC Ack message contains the following parameters:
Traffic Mode Type (mandatory) Traffic Mode Type (optional)
Interface Identifier (optional) Interface Identifier (optional)
- Combination of integer and integer ranges, OR - Combination of integer and integer ranges, OR
- string (text formatted) - string (text formatted)
INFO String (optional) INFO String (optional)
The format for the ASPAC Ack message with Integer-formatted Interface The format for the ASPAC Ack message with Integer-formatted Interface
Identifiers is as follows: Identifiers 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 34, line 36 skipping to change at page 34, line 36
| Tag (0x4) | Length | | Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ INFO String* / \ INFO String* /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format and description of the optional Info String parameter is the The format and description of the optional Info String parameter is the
same as for the ASP Up message (See Section 3.3.2.1). same as for the ASP Up message (See Section 3.3.2.1).
The format of the Type and Interface Identifier parameters is the same The format of the Traffic Mode Type and Interface Identifier parameters
as for the ASP Active message (See Section 3.3.2.5). is the same as for the ASP Active message (See Section 3.3.2.5).
3.3.2.9 ASP Inactive (ASPIA) 3.3.2.9 ASP Inactive (ASPIA)
The ASP Inactive (ASPIA) message is sent by an ASP to indicate to an The ASP Inactive (ASPIA) message is sent by an ASP to indicate to an
SGP that it is no longer an active ASP to be used from within a list SGP that it is no longer an active ASP to be used from within a list
of ASPs. The SGP will respond with an ASPIA Ack message and either of ASPs. The SGP will respond with an ASPIA Ack message and either
discard incoming messages or buffer for a timed period and then discard incoming messages or buffer for a timed period and then
discard. discard.
The ASPIA message contains the following parameters: The ASPIA message contains the following parameters:
skipping to change at page 69, line 36 skipping to change at page 69, line 36
-Rtrv Msg Cfm->|--Rtrv Cfm (ACTION_RTRV_MSGS)->|---Rtrv Msg Cfm--> -Rtrv Msg Cfm->|--Rtrv Cfm (ACTION_RTRV_MSGS)->|---Rtrv Msg Cfm-->
(seq_num = -1) (seq_num = -1)
An example of a message flow for a request to drop messages (clear An example of a message flow for a request to drop messages (clear
retransmission buffers) is shown below. retransmission buffers) is shown below.
MTP2 M2UA M2UA MTP3 MTP2 M2UA M2UA MTP3
SGP SGP ASP ASP SGP SGP ASP ASP
<-Clr TB/RTB Req-|<-Rtrv Req (ACTION_DROP_MSGS)-|<--Clr TB/RTB Req--- -Clr RTB Req----|<-StateReq (STATUS_CLEAR_RTB)--|<--Clr RTB Req-----
-Clr TB/RTB Ind->|-Rtrv Cfm (ACTION_DROP_MSGS)->|---Clr TB/RTB Ind--> -Clr RTB Req--->|-StateCfm (STATUS_CLEAR_RTB)-->|---Clr RTB Req---->
5.3.7 Flush and Continue 5.3.7 Flush and Continue
The following message flow shows a request to flush buffers. The following message flow shows a request to flush buffers.
MTP2 M2UA M2UA MTP3 MTP2 M2UA M2UA MTP3
SGP SGP ASP ASP SGP SGP ASP ASP
<--Flush Req----|<-State Req (STATUS_FLUSH_BUFS)--|<---Flush Req-- <--Flush Req----|<-State Req (STATUS_FLUSH_BUFS)--|<---Flush Req--
skipping to change at page 74, line 7 skipping to change at page 74, line 7
9.0 Acknowledgements 9.0 Acknowledgements
The authors would like to thank John Loughney, Neil Olson, Michael The authors would like to thank John Loughney, Neil Olson, Michael
Tuexen, Nikhil Jain, Steve Lorusso, Dan Brendes, Joe Keller, Heinz Tuexen, Nikhil Jain, Steve Lorusso, Dan Brendes, Joe Keller, Heinz
Prantner, Barry Nagelberg, Naoto Makinae, Joyce Archibald, Mark Prantner, Barry Nagelberg, Naoto Makinae, Joyce Archibald, Mark
Kobine, Nitin Tomar, Harsh Bhondwe and Karen King for their valuable Kobine, Nitin Tomar, Harsh Bhondwe and Karen King for their valuable
comments and suggestions. comments and suggestions.
10.0 References 10.0 References
10.1 Normative
[1] ITU-T Recommendation Q.700, 'Introduction To ITU-T Signalling [1] ITU-T Recommendation Q.700, 'Introduction To ITU-T Signalling
System No. 7 (SS7)' System No. 7 (SS7)'
[2] ITU-T Recommendation Q.701-Q.705, 'Signalling System No. 7 (SS7) - [2] ITU-T Recommendation Q.701-Q.705, 'Signalling System No. 7 (SS7) -
Message Transfer Part (MTP)' Message Transfer Part (MTP)'
[3] ANSI T1.111 'Signalling System Number 7 - Message Transfer Part' [3] ANSI T1.111 'Signalling System Number 7 - Message Transfer Part'
[4] Bellcore GR-246-CORE 'Bell Communications Research Specification [4] Bellcore GR-246-CORE 'Bell Communications Research Specification
of Signalling System Number 7', Volume 1, December 1995 of Signalling System Number 7', Volume 1, December 1995
10.2 Informative
[5] Stream Control Transmission Protocol, RFC 2960, October 2000 [5] Stream Control Transmission Protocol, RFC 2960, October 2000
[6] Architectural Framework for Signalling Transport, RFC 2719, [6] Architectural Framework for Signalling Transport, RFC 2719,
October 1999 October 1999
[7] ITU-T Recommendation Q.2140, 'B-ISDN ATM Adaptation Layer', [7] ITU-T Recommendation Q.2140, 'B-ISDN ATM Adaptation Layer',
February 1995 February 1995
[8] ITU-T Recommendation Q.2210, 'Message transfer part level 3 [8] ITU-T Recommendation Q.2210, 'Message transfer part level 3
 End of changes. 

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