draft-ietf-mpls-git-uus-02.txt   draft-ietf-mpls-git-uus-03.txt 
Network Working Group Muneyoshi Suzuki Network Working Group Muneyoshi Suzuki
INTERNET DRAFT NTT INTERNET DRAFT NTT
Expires September 29, 1999 March 29, 1999 Expires January 26, 2000 July 26, 1999
The Assignment of the Information Field and Protocol Identifier The Assignment of the Information Field and Protocol Identifier
in the Q.2941 Generic Identifier and Q.2957 User-to-user Signaling in the Q.2941 Generic Identifier and Q.2957 User-to-user Signaling
for the Internet Protocol for the Internet Protocol
<draft-ietf-mpls-git-uus-02.txt> <draft-ietf-mpls-git-uus-03.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 RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. 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
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
To view the list Internet-Draft Shadow Directories, see The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
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
The purpose of this document is to specify the assignment of the The purpose of this document is to specify the assignment of the
information field and protocol identifier in the Q.2941 Generic information field and protocol identifier in the Q.2941 Generic
Identifier and Q.2957 User-to-user Signaling for the Internet Identifier and Q.2957 User-to-user Signaling for the Internet
protocol. protocol.
The assignment, that is specified in section 4 of this document, is The assignment, that is specified in section 4 of this document, is
skipping to change at page 8, line 21 skipping to change at page 8, line 21
Identifier type, length and value fields, and a Generic Identifier Identifier type, length and value fields, and a Generic Identifier
information element may contain multiple identifiers. information element may contain multiple identifiers.
Assignment of the Identifier type field for the Intenet protocol is Assignment of the Identifier type field for the Intenet protocol is
as follows. A leading 0x means hexadecimal. as follows. A leading 0x means hexadecimal.
0x01: Session. 0x01: Session.
0x02: Resource. 0x02: Resource.
0x03-0xFD: Reserved for IANA assignment. 0x10-0xFD: Reserved for IANA assignment.
0xFE: Experiment/Organization specific. 0xFE: Experiment/Organization specific.
The maximum length of the Generic Identifier information element is The maximum length of the Generic Identifier information element is
63 octets. 63 octets.
See the Q.2941.1 and Draft Q.2941.2 for detailed protocol See the Q.2941.1 and Draft Q.2941.2 for detailed protocol
specifications of the Generic Identifier. specifications of the Generic Identifier.
3.2 Overview of the User-to-user Signaling 3.2 Overview of the User-to-user Signaling
skipping to change at page 22, line 22 skipping to change at page 22, line 22
environment. Wild card style aggregated session identifier may be environment. Wild card style aggregated session identifier may be
feasible. However, before specifying Generic Identifier support feasible. However, before specifying Generic Identifier support
for it, session aggregation model in ATM VCs should be clarified. for it, session aggregation model in ATM VCs should be clarified.
o Generic Identifier support for the IPv6 flow label and traffic o Generic Identifier support for the IPv6 flow label and traffic
classes. classes.
The IPv6 flow label and traffic classes support may be needed in The IPv6 flow label and traffic classes support may be needed in
future. However, currently their semantics are not clear. future. However, currently their semantics are not clear.
6. Security Considerations 6. IANA Considerations
When the Identifier related standard/application field in the
Q.2941.2 Generic Identifier information element is the IPv4, ST2+,
IPv6, or MPLS, numbers between 0x10-0xFD in the Identifier type field
are reserved for IANA assignment. (See section 3.1). Following the
policies outlined in [14], these numbers are allocated through an
IETF Consensus action.
When the Protocol discriminator field in the Q.2957 User-user
information element is the Internet protocol/application, numbers
between 0x03-0xFD in the Internet protocol/application identifier
field are reserved for IANA assignment. (See section 4.2.1).
Following the policies outlined in [14], these numbers are allocated
through an IETF Consensus action.
7. Security Considerations
This document specifies the information field and protocol identifier This document specifies the information field and protocol identifier
assignment in the Q.2941 Generic Identifier and Q.2957 User-to-user assignment in the Q.2941 Generic Identifier and Q.2957 User-to-user
Signaling for the Internet protocol, so these do not weaken the Signaling for the Internet protocol, so these do not weaken the
security of the B-ISDN signaling. security of the B-ISDN signaling.
In a called party of the B-ISDN signaling, if the incoming SETUP In a called party of the B-ISDN signaling, if the incoming SETUP
message contains the calling party number and if it is verified and message contains the calling party number and if it is verified and
passed by the ATM network or it is provided by the network, then it passed by the ATM network or it is provided by the network, then it
is feasible to use the calling party number for part of the calling is feasible to use the calling party number for part of the calling
skipping to change at page 23, line 9 skipping to change at page 23, line 26
Call/Connection Control," ITU-T Recommendation Q.2971, October Call/Connection Control," ITU-T Recommendation Q.2971, October
1995. 1995.
[3] ITU-T, "Broadband Integrated Services Digital Network (B-ISDN) [3] ITU-T, "Broadband Integrated Services Digital Network (B-ISDN)
Digital Subscriber Signaling System No. 2 (DSS 2): Generic Digital Subscriber Signaling System No. 2 (DSS 2): Generic
Identifier Transport," Draft ITU-T New Recommendation Q.2941.1, Identifier Transport," Draft ITU-T New Recommendation Q.2941.1,
September 1997. September 1997.
[4] ITU-T, "Broadband Integrated Services Digital Network (B-ISDN) [4] ITU-T, "Broadband Integrated Services Digital Network (B-ISDN)
Digital Subscriber Signaling System No. 2 (DSS 2): Generic Digital Subscriber Signaling System No. 2 (DSS 2): Generic
Identifier Transport," Draft ITU-T New Recommendation Q.2941.2, Identifier Transport Extensions," Draft ITU-T New Recommendation
March 1999. Q.2941.2, July 1999.
[5] ITU-T, "Stage 3 Description for Additional Information [5] ITU-T, "Stage 3 Description for Additional Information
Transfer Supplementary Service Using B-ISDN Digital Subscriber Transfer Supplementary Service Using B-ISDN Digital Subscriber
Signaling System No. 2 (DSS 2)-Basic Call Clause 1-User-to-User Signaling System No. 2 (DSS 2)-Basic Call Clause 1-User-to-User
Signalling (UUS)," ITU-T Recommendation Q.2957, February 1995. Signalling (UUS)," ITU-T Recommendation Q.2957, February 1995.
[6] ITU-T, "Stage 3 Description for Additional Information [6] ITU-T, "Stage 3 Description for Additional Information
Transfer Supplementary Service Using B-ISDN Digital Subscriber Transfer Supplementary Service Using B-ISDN Digital Subscriber
Signaling System No. 2 (DSS 2)-Basic Call Clause 1-User-to-User Signaling System No. 2 (DSS 2)-Basic Call Clause 1-User-to-User
Signalling (UUS)," Draft ITU-T Recommendation Q.2957 Amendment 1, Signalling (UUS)," Draft ITU-T Recommendation Q.2957 Amendment 1,
March 1999. July 1999.
[7] J. Postel Ed., "Internet Protocol," RFC 791, September 1981. [7] J. Postel Ed., "Internet Protocol," RFC 791, September 1981.
[8] S. Deering and R. Hinden, "Internet Protocol, Version 6 (IPv6) [8] S. Deering and R. Hinden, "Internet Protocol, Version 6 (IPv6)
Specification," RFC 2460, December 1998. Specification," RFC 2460, December 1998.
[9] J. Postel, "User Datagram Protocol," RFC 768, August 1980. [9] J. Postel, "User Datagram Protocol," RFC 768, August 1980.
[10] J. Postel Ed., "Transmission Control Protocol," RFC 793, [10] J. Postel Ed., "Transmission Control Protocol," RFC 793,
September 1981. September 1981.
[11] L. Delgrossi and L. Berger, Ed., "Internet Stream Protocol [11] L. Delgrossi and L. Berger, Ed., "Internet Stream Protocol
Version 2 (ST2) Protocol Specification - Version ST2+," RFC 1819, Version 2 (ST2) Protocol Specification - Version ST2+," RFC 1819,
August 1995. August 1995.
[12] R. Braden Ed., "Resource ReSerVation Protocol (RSVP)-Version [12] R. Braden Ed., "Resource ReSerVation Protocol (RSVP)-Version
1 Functional Specification," RFC 2205, September 1997. 1 Functional Specification," RFC 2205, September 1997.
[13] K. Nagami, N. Demizu, H. Esaki, Y. Katsube, and P. Doolan, [13] K. Nagami, N. Demizu, H. Esaki, Y. Katsube, and P. Doolan,
"VCID Notification over ATM link," Internet Draft, December 1998, "VCID Notification over ATM link for LDP," Work in Progress.
<draft-ietf-mpls-vcid-atm-02.txt>.
[14] P. Newman, T. Lyon, and G. Minshall, "Flow Labelled IP: A [14] T. Narten and H. Alvestrand, "Guidelines for Writing an IANA
Considerations Section in RFCs," RFC 2434, October 1998.
[15] P. Newman, T. Lyon, and G. Minshall, "Flow Labelled IP: A
Connectionless Approach to ATM," Proc. IEEE Infocom, March 1996. Connectionless Approach to ATM," Proc. IEEE Infocom, March 1996.
[15] S. Damaskos and A. Gavras, "Connection Oriented Protocols [16] S. Damaskos and A. Gavras, "Connection Oriented Protocols
over ATM: A case study," Proc. SPIE, Vol. 2188, pp.226-278, over ATM: A case study," Proc. SPIE, Vol. 2188, pp.226-278,
February 1994. February 1994.
[16] ITU-T, "Integrated Services Digital Network (ISDN) Overall [17] ITU-T, "Integrated Services Digital Network (ISDN) Overall
Network Aspects and Functions ISDN Protocol Reference Model," Network Aspects and Functions ISDN Protocol Reference Model,"
ITU-T Recommendation I.320, November 1993. ITU-T Recommendation I.320, November 1993.
[17] ITU-T, "Digital Subscriber Signaling System No. 1 (DSS 1) [18] ITU-T, "Digital Subscriber Signaling System No. 1 (DSS 1)
Specification of a Synchronization and Coordination Function for Specification of a Synchronization and Coordination Function for
the Provision of the OSI Connection-mode Network Service in an the Provision of the OSI Connection-mode Network Service in an
ISDN Environment," ITU-T Recommendation Q.923, February 1995. ISDN Environment," ITU-T Recommendation Q.923, February 1995.
Acknowledgments Acknowledgments
I would like to thank Kenichi Kitami of the NTT Information I would like to thank Kenichi Kitami of the NTT Information
Sharing Lab. Group, who is also the chair of ITU-T SG11 WP1, Sharing Lab. Group, who is also the chair of ITU-T SG11 WP1,
Shinichi Kuribayashi of the NTT Information Sharing Platform Shinichi Kuribayashi of the NTT Information Sharing Platform
Labs., Hiroshi Yao and Takumi Ohba of the NTT Network Service Labs., Hiroshi Yao and Takumi Ohba of the NTT Network Service
 End of changes. 

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