draft-ietf-sigtran-iua-imp-guide-01.txt   draft-ietf-sigtran-iua-imp-guide-02.txt 
Network Working Group K. Morneault Network Working Group K. Morneault
INTERNET-DRAFT Cisco Systems INTERNET-DRAFT Cisco Systems
Expires in six months July 2002 Expires in six months Oct 2002
IUA (RFC 3057) Outstanding Issues IUA (RFC 3057) Outstanding Issues
<draft-ietf-sigtran-iua-imp-guide-01.txt> <draft-ietf-sigtran-iua-imp-guide-02.txt>
Status of This Memo Status of This Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026 [RFC2026]. Internet-Drafts all provisions of Section 10 of RFC 2026 [RFC2026]. Internet-Drafts
are working documents of the Internet Engineering Task Force (IETF), are working documents of the Internet Engineering Task Force (IETF),
its areas, and its working groups. Note that other groups may also its areas, and its working groups. Note that other groups may also
distribute working documents as Internet-Drafts. distribute working documents as Internet-Drafts.
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Abstract Abstract
This document captures problems and issues discovered on the SIGTRAN This document captures problems and issues discovered on the SIGTRAN
mailing list and at future bakeoffs for IUA [RFC3057]. This document mailing list and at future interops for IUA [RFC3057]. This document
will be updated after each bakeoff augmenting the existing draft to will be updated after each interop augmenting the existing draft to
include any new issues discovered during inter-operability testing. include any new issues discovered during inter-operability testing.
Two basic sets of problems are identified by this draft: first, issues Two basic sets of problems are identified by this draft: first, issues
that need to be addressed when the next revision of IUA is created, that need to be addressed when the next revision of IUA is created,
i.e. issues that should be remembered in a BIS document; second, i.e. issues that should be remembered in a BIS document; second,
issues that were found that are strictly implementation problems. issues that were found that are strictly implementation problems.
Table of Contents Table of Contents
1.0 Introduction................................................ 2 1.0 Introduction................................................ 2
2.0 Conventions................................................. 2 2.0 Conventions................................................. 2
skipping to change at line 1517 skipping to change at line 1517
3.20.3 Solution description 3.20.3 Solution description
An example message flow is provided for the case of Interface An example message flow is provided for the case of Interface
Identifier misconfiguration. Identifier misconfiguration.
3.21 ASP Inactive Traffic Mode Parameter 3.21 ASP Inactive Traffic Mode Parameter
3.21.1 Description of the problem 3.21.1 Description of the problem
The Traffic Mode Type parameter was removed from ASP Inactive The Traffic Mode Type parameter was removed from ASP Inactive
message for all other UAs. and ASP Inactive Acknowledgement messages for all other UAs.
3.21.2 Text changes to the document 3.21.2 Text changes to the document
--------- ---------
Old text: (Section 3.3.2.7) Old text: (Section 3.3.2.7)
--------- ---------
The ASPIA message contains the following parameters The ASPIA message contains the following parameters
Traffic Mode Type (Mandatory) Traffic Mode Type (Mandatory)
skipping to change at line 1692 skipping to change at line 1692
| of Tag Type 0x3 | | of Tag Type 0x3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length | | Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| INFO String* | | INFO String* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
---------
Old text: (Section 3.3.2.8)
---------
The ASP Inactive (ASPIA) Ack message is used to acknowledge an ASP
Inactive message received from a remote IUA peer.
The ASPIA Ack message contains the following parameters:
Traffic Mode Type (Mandatory)
Interface Identifiers (Optional)
- Combination of integer and integer ranges, OR
- string (text formatted)
INFO String (Optional)
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xb) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x1=integer) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifiers* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x8=integer range) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StartN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StopN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Additional Interface Identifiers |
| of Tag Type 0x1 or 0x8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| INFO String* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format for the ASP Inactive Ack message using text formatted
(string) Interface Identifiers is as follows:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xb) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x3=string) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Additional Interface Identifiers |
| of Tag Type 0x3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| INFO String* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format of the Traffic Mode Type and Interface Identifier
parameters is the same as for the ASP Inactive message (See Section
3.3.2.7).
---------
New text: (Section 3.3.2.8)
---------
The ASP Inactive (ASPIA) Ack message is used to acknowledge an ASP
Inactive message received from a remote IUA peer.
The ASPIA Ack message contains the following parameters:
Interface Identifiers (Optional)
- Combination of integer and integer ranges, OR
- string (text formatted)
INFO String (Optional)
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x1=integer) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifiers* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x8=integer range) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StartN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StopN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Additional Interface Identifiers |
| of Tag Type 0x1 or 0x8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| INFO String* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format for the ASP Inactive Ack message using text formatted
(string) Interface Identifiers is as follows:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x3=string) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Additional Interface Identifiers |
| of Tag Type 0x3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| INFO String* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format of the Interface Identifier parameters is the same as for
the ASP Inactive message (See Section 3.3.2.7).
3.21.3 Solution description 3.21.3 Solution description
Remove Traffic Mode Type from ASP Inactive message in order to Remove Traffic Mode Type from ASP Inactive message in order to
remain consistent with other UAs. remain consistent with other UAs.
3.22 Encoding of the DLCI parameter 3.22 Encoding of the DLCI parameter
3.22.1 Description of the problem 3.22.1 Description of the problem
The text states the DLCI field is encoded in accordance to Q.921 The text states the DLCI field is encoded in accordance to Q.921
skipping to change at line 1946 skipping to change at line 2114
-------- --------
New text (Section 5.1.2) New text (Section 5.1.2)
-------- --------
SG ASP1 ASP2 SG ASP1 ASP2
| | | | | |
|<--------ASP Up----------| | |<--------ASP Up----------| |
|-------ASP Up Ack------->| | |-------ASP Up Ack------->| |
| | | | | |
|----NTFY(AS-INACTIVE)--->| | |----NTFY(AS-INACTIVE)--->| |
|---------------------NTFY(AS-INACTIVE)------------->|
| | | | | |
|<-----------------------------ASP Up----------------| |<-----------------------------ASP Up----------------|
|----------------------------ASP Up Ack------------->| |----------------------------ASP Up Ack------------->|
| | | | | |
| | | | | |
|<-------ASP Active-------| | |<-------ASP Active-------| |
|-----ASP Active Ack----->| | |-----ASP Active Ack----->| |
| | | | | |
|-----NTFY(AS-ACTIVE)---->| | |-----NTFY(AS-ACTIVE)---->| |
|----------------------NTFY(AS-ACTIVE)-------------->| |----------------------NTFY(AS-ACTIVE)-------------->|
skipping to change at line 1988 skipping to change at line 2155
-------- --------
New text (Section 5.1.3) New text (Section 5.1.3)
-------- --------
SG ASP1 ASP2 SG ASP1 ASP2
| | | | | |
|<---------ASP Up---------| | |<---------ASP Up---------| |
|--------ASP Up Ack------>| | |--------ASP Up Ack------>| |
| | | | | |
|----NTFY(AS-INACTIVE)--->| | |----NTFY(AS-INACTIVE)--->| |
|---------------------NTFY(AS-INACTIVE)------------->|
| | | | | |
|<------------------------------ASP Up---------------| |<------------------------------ASP Up---------------|
|-----------------------------ASP Up Ack------------>| |-----------------------------ASP Up Ack------------>|
| | | | | |
| | | | | |
|<--ASP Active (Ldshr)----| | |<--ASP Active (Ldshr)----| |
|----ASP Active Ack------>| | |----ASP Active Ack------>| |
| | | | | |
|-----NTFY(AS-ACTIVE)---->| | |-----NTFY(AS-ACTIVE)---->| |
|----------------------NTFY(AS-ACTIVE)-------------->| |----------------------NTFY(AS-ACTIVE)-------------->|
skipping to change at line 2037 skipping to change at line 2203
-------- --------
New text (Section 5.1.4) New text (Section 5.1.4)
-------- --------
SG ASP1 ASP2 ASP3 SG ASP1 ASP2 ASP3
| | | | | | | |
|<------ASP Up-------| | | |<------ASP Up-------| | |
|-----ASP Up Ack---->| | | |-----ASP Up Ack---->| | |
| | | | | | | |
|-NTFY(AS-INACTIVE)->| | | |-NTFY(AS-INACTIVE)->| | |
|--------------NTFY(AS-INACTIVE)-------->| |
|-----------------------NTFY(AS-INACTIVE)------------------->|
| | | | | | | |
|<--------------------------ASP Up-------| | |<--------------------------ASP Up-------| |
|------------------------ASPUp Ack)----->| | |-----------------------ASP Up Ack------>| |
| | | | | | | |
|<---------------------------------------------ASP Up--------| |<---------------------------------------------ASP Up--------|
|--------------------------------------------ASP Up Ack----->| |--------------------------------------------ASP Up Ack----->|
| | | | | | | |
| | | | | | | |
|<-ASP Act (Ldshr)---| | | |<-ASP Act (Ldshr)---| | |
|----ASP Act Ack---->| | | |----ASP Act Ack---->| | |
| | | | | | | |
|<---------------------ASP Act (Ldshr)---| | |<---------------------ASP Act (Ldshr)---| |
|----------------------ASP Act Ack------>| | |----------------------ASP Act Ack------>| |
skipping to change at line 2085 skipping to change at line 2249
SG ASP1 ASP2 SG ASP1 ASP2
| | | | | |
|<-----ASP Inactive-------| | |<-----ASP Inactive-------| |
|----ASP Inactive Ack---->| | |----ASP Inactive Ack---->| |
| | | | | |
|----NTFY(AS-Pending)---->| | |----NTFY(AS-Pending)---->| |
|-------------------NTFY(AS-Pending)---------------->| |-------------------NTFY(AS-Pending)---------------->|
| | | | | |
|<------------------------------ ASP Active----------| |<------------------------------ ASP Active----------|
|-----------------------------ASP Active Ack)------->| |-----------------------------ASP Active Ack)------->|
| | | | |
|----NTFY(AS-ACTIVE)----->| | |----NTFY(AS-ACTIVE)----->| |
|-------------------NTFY(AS-ACTIVE)----------------->| |-------------------NTFY(AS-ACTIVE)----------------->|
3.23.3 Solution description 3.23.3 Solution description
The new text shows when the SG should send Notify messages. The new text shows when the SG should send Notify messages.
4.0 Acknowledgements 4.0 Acknowledgements
The author would like to thank the following people that have The author would like to thank the following people that have
provided comments and input for this document: Alex Audu, provided comments and input for this document: Alex Audu,
Greg Sidebottom, Srinivasa A. Shikaripura, Subhodeep Sarkar, Greg Sidebottom, Srinivasa A. Shikaripura, Subhodeep Sarkar,
Sujatha Krao, Ming Lin, Shih-Chang Liang and Michael Tuexen. Sujatha Krao, Ming Lin, Shih-Chang Liang, Michael Tuexen and
Kameshwar Mallampalli.
5.0 Authors Addresses 5.0 Authors Addresses
Ken A. Morneault Ken A. Morneault
13615 Dulles Technology Drive 13615 Dulles Technology Drive
Herndon, VA 20171 Herndon, VA 20171
USA USA
EMail: kmorneau@cisco.com EMail: kmorneau@cisco.com
 End of changes. 

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