draft-ietf-ccamp-gmpls-ason-reqts-02.txt   draft-ietf-ccamp-gmpls-ason-reqts-03.txt 
CCAMP Working Group D. Papadimitriou (Alcatel) CCAMP Working Group D. Papadimitriou (Alcatel)
Internet Draft Z. Lin (New York City Transit) Internet Draft Z. Lin (New York City Transit)
Category: Informational J. Drake (Calient) Category: Informational J. Drake (Calient)
J. Ash (ATT) J. Ash (ATT)
Expiration Date: February 2004 A. Farrel (Old Dog Consulting) Expiration Date: March 2004 A. Farrel (Old Dog Consulting)
L. Ong (Ciena) L. Ong (Ciena)
August 2003 September 2003
Requirements for Generalized MPLS (GMPLS) Signaling Usage Requirements for Generalized MPLS (GMPLS) Signaling Usage
and Extensions for Automatically Switched Optical Network (ASON) and Extensions for Automatically Switched Optical Network (ASON)
draft-ietf-ccamp-gmpls-ason-reqts-02.txt draft-ietf-ccamp-gmpls-ason-reqts-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 RFC-2026. all provisions of Section 10 of RFC-2026.
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. Internet-Drafts are draft documents valid for a maximum of Drafts. Internet-Drafts are draft documents valid for a maximum of
skipping to change at line 50 skipping to change at line 50
applications. These include support for requesting TDM connections applications. These include support for requesting TDM connections
including SONET/SDH and Optical Transport Networks (OTNs). including SONET/SDH and Optical Transport Networks (OTNs).
This document concentrates on the signaling aspects of the GMPLS This document concentrates on the signaling aspects of the GMPLS
suite of protocols. It identifies the features to be covered by the suite of protocols. It identifies the features to be covered by the
GMPLS signaling protocol to support the capabilities of an GMPLS signaling protocol to support the capabilities of an
Automatically Switched Optical Network (ASON). This document Automatically Switched Optical Network (ASON). This document
provides a problem statement and additional requirements on the provides a problem statement and additional requirements on the
GMPLS signaling protocol to support the ASON functionality. GMPLS signaling protocol to support the ASON functionality.
D.Papadimitriou et al. - Expires February 2004 1 D.Papadimitriou et al. - Expires March 2004 1
2. Conventions used in this document 2. Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in RFC-2119. this document are to be interpreted as described in RFC-2119.
3. Introduction 3. Introduction
The GMPLS suite of protocol specifications provides support for The GMPLS suite of protocol specifications provides support for
skipping to change at line 86 skipping to change at line 86
description of backward compatibility considerations is provided in description of backward compatibility considerations is provided in
Section 5. A terminology section is provided in the Appendix. Section 5. A terminology section is provided in the Appendix.
Problem Statement: Problem Statement:
The Automatically Switched Optical Network (ASON) architecture The Automatically Switched Optical Network (ASON) architecture
describes the application of an automated control plane for describes the application of an automated control plane for
supporting both call and connection management services (for a supporting both call and connection management services (for a
detailed description see [ITU-T G.8080]). detailed description see [ITU-T G.8080]).
The ASON control plane specification is meant to be applicable to Also, the ASON model distinguishes reference points (representing
different transport technologies (e.g., SDH/SONET, OTN) in various points of protocol information exchange) defined (1) between an
networking environments (e.g., inter-carrier, intra-carrier). Also, administrative domain and a user a.k.a. user-network interface
the ASON model distinguishes reference points (representing points (UNI), (2) between (and when needed within) administrative domains
of protocol information exchange) defined (1) between an a.k.a. external network-network interface (E-NNI) and, (3) between
administrative domain and a user, (2) between administrative domains areas of the same administrative domain and when needed between
and, (3) between areas of the same administrative domain and when control components (or simply controllers) within areas a.k.a.
needed between control components (or simply controllers) within internal network-network interface (I-NNI). A full description of
areas. A full description of the ASON terms and relationship between the ASON terms and relationship between ASON model and GMPLS
ASON model and GMPLS protocol suite may be found in [IPO-ASON]. protocol suite may be found in [IPO-ASON].
This document describes the use of GMPLS signaling (in particular, This document describes the use of GMPLS signaling (in particular,
[RFC 3471] and [RFC 3473]) to provide call and connection management [RFC 3471] and [RFC 3473]) to provide call and connection management
(see [ITU-T G.7713]). The following functionality is expected to be (see [ITU-T G.7713]). The following functionality is expected to be
supported and to be backward compatible with the GMPLS protocol supported and to be backward compatible with the GMPLS protocol
suite as currently defined by the IETF: suite as currently defined by the IETF:
(a) soft permanent connection capability (a) soft permanent connection capability
(b) call and connection separation (b) call and connection separation
D.Papadimitriou et al. - Expires February 2004 2 D.Papadimitriou et al. - Expires March 2004 2
(c) call segments (c) call segments
(d) extended restart capabilities during control plane failures (d) extended restart capabilities during control plane failures
(e) extended label usage (e) extended label usage
(f) crankback capability (f) crankback capability
(g) additional error cases. (g) additional error cases.
4. Requirements for Extending Applicability of GMPLS to ASON 4. Requirements for Extending Applicability of GMPLS to ASON
The applicability statements regarding how the GMPLS suite of The applicability statements regarding how the GMPLS suite of
protocols may be applied to the ASON architecture can be found in protocols may be applied to the ASON architecture can be found in
skipping to change at line 148 skipping to change at line 148
signaling domains, end-to-end signaling should be facilitated signaling domains, end-to-end signaling should be facilitated
regardless of the administrative boundaries and protocols within the regardless of the administrative boundaries and protocols within the
network. The resulting requirement being that there needs to be a network. The resulting requirement being that there needs to be a
clear mapping of signaling requests between GMPLS control domains clear mapping of signaling requests between GMPLS control domains
and non-GMPLS control domains. This document provides signalling and non-GMPLS control domains. This document provides signalling
requirements for G.8080 distributed call and connection management requirements for G.8080 distributed call and connection management
based on GMPLS, within a GMPLS based control domain and between based on GMPLS, within a GMPLS based control domain and between
GMPLS based control domains. It does not restrict use of other GMPLS based control domains. It does not restrict use of other
protocols within a control domain. Interworking aspects, including protocols within a control domain. Interworking aspects, including
mapping of non-GMPLS protocol signaling requests and support of non- mapping of non-GMPLS protocol signaling requests and support of non-
GMPLS address formats, is outside the scope of this document. GMPLS address formats, are outside the scope of this document.
Any User-Network Interface (UNI) that is compliant with [RFC-3473],
e.g. [GMPLS-OVERLAY] and [GMPLS-VPN] is considered, by definition,
to be a GMPLS UNI and must be supported.
Compatibility aspects of non-GMPLS systems (nodes) within a GMPLS Compatibility aspects of non-GMPLS systems (nodes) within a GMPLS
control domain i.e. the support of GMPLS systems and other systems control domain i.e. the support of GMPLS systems and other systems
which utilize other signaling protocols or some which may not which utilize other signaling protocols or some which may not
support any signaling protocols is described. For instance, Section support any signaling protocols is described. For instance, Section
D.Papadimitriou et al. - Expires March 2004 3
4.5 'Support for Extended Label Usage' covers the requirements when 4.5 'Support for Extended Label Usage' covers the requirements when
a non-GMPLS capable sub-network is introduced or when nodes do not a non-GMPLS capable sub-network is introduced or when nodes do not
support any signaling protocols. support any signaling protocols.
4.1 Support for Soft Permanent Connection (SPC) Capability 4.1 Support for Soft Permanent Connection (SPC) Capability
D.Papadimitriou et al. - Expires February 2004 3
An SPC is a combination of a permanent connection at the source An SPC is a combination of a permanent connection at the source
user-to-network side, a permanent connection at the destination user-to-network side, a permanent connection at the destination
user-to-network side, and a switched connection within the network. user-to-network side, and a switched connection within the network.
An Element Management System (EMS) or a Network Management System An Element Management System (EMS) or a Network Management System
(NMS) typically initiates the establishment of the switched (NMS) typically initiates the establishment of the switched
connection by communicating with the node that initiates the connection by communicating with the node that initiates the
switched connection (also known as the ingress node). The latter switched connection (also known as the ingress node). The latter
then sets the connection using the distributed GMPLS signaling then sets the connection using the distributed GMPLS signaling
protocol. For the SPC, the communication method between the EMS/NMS protocol. For the SPC, the communication method between the EMS/NMS
and the ingress node is beyond the scope of this document (so it is and the ingress node is beyond the scope of this document (so it is
skipping to change at line 206 skipping to change at line 212
networks, the GMPLS signaling protocol should also support networks, the GMPLS signaling protocol should also support
indication of the service level requested for the SPC. In the case indication of the service level requested for the SPC. In the case
where an SPC spans multiple domains, indication of both source and where an SPC spans multiple domains, indication of both source and
destination endpoints controlling the SPC request may be needed. destination endpoints controlling the SPC request may be needed.
These may be done via the source and destination signaling These may be done via the source and destination signaling
controller addresses. controller addresses.
Note that the association at the ingress node between the permanent Note that the association at the ingress node between the permanent
connection and the switched connection is an implementation matter connection and the switched connection is an implementation matter
under the control of the EMS/NMS and is not within the scope of the under the control of the EMS/NMS and is not within the scope of the
D.Papadimitriou et al. - Expires March 2004 4
signaling protocol. It is, therefore, outside the scope of this signaling protocol. It is, therefore, outside the scope of this
document. document.
4.2 Support for Call and Connection Separation 4.2 Support for Call and Connection Separation
D.Papadimitriou et al. - Expires February 2004 4
A call may be simply described as "An association between endpoints A call may be simply described as "An association between endpoints
that supports an instance of a service" [ITU-T G.8080]. Thus, it can that supports an instance of a service" [ITU-T G.8080]. Thus, it can
be considered as a service provided between two end-points, where be considered as a service provided between two end-points, where
several calls may exist between them. Multiple connections may be several calls may exist between them. Multiple connections may be
associated to each call. The call concept provides an abstract associated to each call. The call concept provides an abstract
relationship between two users, where this relationship describes relationship between two users, where this relationship describes
(or verifies) to what extent the users are willing to offer (or (or verifies) to what extent the users are willing to offer (or
accept) service to each other. Therefore, a call does not provide accept) service to each other. Therefore, a call does not provide
the actual connectivity for transmitting user traffic, but only the actual connectivity for transmitting user traffic, but only
builds a relationship by which subsequent connections may be made. builds a relationship by which subsequent connections may be made.
skipping to change at line 260 skipping to change at line 267
For instance, a feasible structure for the call identifier (to For instance, a feasible structure for the call identifier (to
guarantee global uniqueness) may concatenate a globally unique fixed guarantee global uniqueness) may concatenate a globally unique fixed
ID (e.g., may be composed of country code, carrier code) with an ID (e.g., may be composed of country code, carrier code) with an
operator specific ID (where the operator specific ID may be composed operator specific ID (where the operator specific ID may be composed
of a unique access point code - such as source node address - and a of a unique access point code - such as source node address - and a
local identifier). Other formats shall also be possible depending on local identifier). Other formats shall also be possible depending on
the call identification conventions between parties involved in the the call identification conventions between parties involved in the
call setup process. call setup process.
D.Papadimitriou et al. - Expires March 2004 5
4.3 Support for Call Segments 4.3 Support for Call Segments
As described in [ITU-T G.8080], call segmentation may be applied As described in [ITU-T G.8080], call segmentation may be applied
when a call crosses several administrative domains. As such, an end- when a call crosses several administrative domains. As such, an end-
D.Papadimitriou et al. - Expires February 2004 5
to-end call may consist of multiple call segments, when the call to-end call may consist of multiple call segments, when the call
traverses multiple administrative domains. Each call segment can traverses multiple administrative domains. Each call segment can
have one or more associated connections and the number of have one or more associated connections and the number of
connections associated with each call segment may not be the same connections associated with each call segment may not be the same
for a given end-to-end call. for a given end-to-end call.
The initiating caller interacts with a called party by means of one The initiating caller interacts with a called party by means of one
or more intermediate call controllers located at the network edge or more intermediate call controllers located at the network edge
between administrative domains (i.e., inter-domain reference point) between administrative domains (i.e., inter-domain reference point)
and in particular at the user-to-network reference point. Their and in particular at the user-to-network reference point. Their
skipping to change at line 312 skipping to change at line 319
- Upon recovery from a control plane failure, a call must have - Upon recovery from a control plane failure, a call must have
the ability to re-synchronize with its associated connections. the ability to re-synchronize with its associated connections.
4.5 Support for Extended Label Usage 4.5 Support for Extended Label Usage
Labels are defined in GMPLS (see [RFC 3471]) to provide information Labels are defined in GMPLS (see [RFC 3471]) to provide information
on the resources used on link local basis for a particular on the resources used on link local basis for a particular
connection. The labels may range from specifying a particular connection. The labels may range from specifying a particular
timeslot, a particular wavelength to a particular port/fiber. timeslot, a particular wavelength to a particular port/fiber.
D.Papadimitriou et al. - Expires March 2004 6
In the ASON context, the value of a label MAY not be consistently In the ASON context, the value of a label MAY not be consistently
the same across a link. For example, the figure below illustrates the same across a link. For example, the figure below illustrates
the case where two GMPLS capable nodes (A and Z) are interconnected the case where two GMPLS capable nodes (A and Z) are interconnected
across two non-GMPLS capable nodes (B and C), where these nodes are across two non-GMPLS capable nodes (B and C), where these nodes are
all SONET/SDH nodes providing, e.g., a VC-4 service. all SONET/SDH nodes providing, e.g., a VC-4 service.
D.Papadimitriou et al. - Expires February 2004 6
----- ----- ----- -----
| | --- --- | | | | --- --- | |
| A |---| B |---| C |---| Z | | A |---| B |---| C |---| Z |
| | --- --- | | | | --- --- | |
----- ----- ----- -----
Labels have an associated implicit imposed structure based on Labels have an associated implicit imposed structure based on
[GMPLS-SONET] and [GMPLS-OTN]. Thus, once the local label is [GMPLS-SONET] and [GMPLS-OTN]. Thus, once the local label is
exchanged with its neighboring control plane node, the structure of exchanged with its neighboring control plane node, the structure of
the local label MAY not be significant to the neighbor node since the local label MAY not be significant to the neighbor node since
skipping to change at line 365 skipping to change at line 372
- Manual provisioning of the label association - Manual provisioning of the label association
- Discovery of the label association - Discovery of the label association
Either method may be used. In case of dynamic association, this Either method may be used. In case of dynamic association, this
implies that the discovery mechanism operates at the timeslot/label implies that the discovery mechanism operates at the timeslot/label
level before the connection request is processed at the ingress level before the connection request is processed at the ingress
node. Note that in the case where two nodes are directly connected, node. Note that in the case where two nodes are directly connected,
no association is required. In particular, for directly connected no association is required. In particular, for directly connected
TDM interfaces no mapping function (at all) is required due to the TDM interfaces no mapping function (at all) is required due to the
implicit label structure (see [GMPLS-SONET] and [GMPLS-OTN]). In implicit label structure (see [GMPLS-SONET] and [GMPLS-OTN]). In
D.Papadimitriou et al. - Expires March 2004 7
such instances, the label association function provides a one-to-one such instances, the label association function provides a one-to-one
mapping of the received to local label values. mapping of the received to local label values.
4.6 Support for Crankback 4.6 Support for Crankback
D.Papadimitriou et al. - Expires February 2004 7
Crankback has been identified as an important requirement for ASON Crankback has been identified as an important requirement for ASON
networks. It allows a connection setup request to be retried on an networks. It allows a connection setup request to be retried on an
alternate path that detours around a blocked link or node upon a alternate path that detours around a blocked link or node upon a
setup failure, for instance, because a link or a node along the setup failure, for instance, because a link or a node along the
selected path has insufficient resources. selected path has insufficient resources.
Crankback mechanisms may also be applied during connection recovery Crankback mechanisms may also be applied during connection recovery
by indicating the location of the failed link or node. This would by indicating the location of the failed link or node. This would
significantly improve the successful recovery ratio for failed significantly improve the successful recovery ratio for failed
connections, especially in situations where a large number of setup connections, especially in situations where a large number of setup
skipping to change at line 418 skipping to change at line 426
- Rerouting attempts limitation: to prevent an endless repetition of - Rerouting attempts limitation: to prevent an endless repetition of
connection setup attempts (using crankback information), the number connection setup attempts (using crankback information), the number
of retries should be strictly limited. The maximum number of of retries should be strictly limited. The maximum number of
crankback rerouting attempts allowed can be limited per connection, crankback rerouting attempts allowed can be limited per connection,
per node, per area or even per administrative domain. per node, per area or even per administrative domain.
- When the number of retries at a particular node or area is - When the number of retries at a particular node or area is
exceeded, the node currently handling the failure reports the exceeded, the node currently handling the failure reports the
error message upstream to the next repair node where further error message upstream to the next repair node where further
rerouting attempts may be performed. It is important that the rerouting attempts may be performed. It is important that the
D.Papadimitriou et al. - Expires March 2004 8
crankback information provided indicates that re-routing crankback information provided indicates that re-routing
through this node will not succeed. through this node will not succeed.
- When the maximum number of retries for a specific connection - When the maximum number of retries for a specific connection
has been exceeded, the repair node handling the current failure has been exceeded, the repair node handling the current failure
should send an error message upstream indicating "Maximum should send an error message upstream indicating "Maximum
D.Papadimitriou et al. - Expires February 2004 8
number of re-routings exceeded". This error message will be number of re-routings exceeded". This error message will be
sent back to the ingress node with no further rerouting sent back to the ingress node with no further rerouting
attempts. Then, the ingress node may choose to retry the attempts. Then, the ingress node may choose to retry the
connection setup according to local policy but also re-use its connection setup according to local policy but also re-use its
original path or compute a path that avoids the blocking original path or compute a path that avoids the blocking
resources. resources.
Note: after several retries, a given repair point may be unable to Note: after several retries, a given repair point may be unable to
compute a path to the destination node that avoids all of the compute a path to the destination node that avoids all of the
blockages. In this case, it must pass the error message upstream to blockages. In this case, it must pass the error message upstream to
skipping to change at line 471 skipping to change at line 479
3473]) between any arbitrary pair of nodes and traversing any 3473]) between any arbitrary pair of nodes and traversing any
arbitrary set of nodes. Further, the use of any GMPLS signaling arbitrary set of nodes. Further, the use of any GMPLS signaling
extensions to set up calls or connections that support the functions extensions to set up calls or connections that support the functions
described in this document must not perturb existing conventional described in this document must not perturb existing conventional
connections. connections.
Additionally, when transit nodes, that do not need to participate in Additionally, when transit nodes, that do not need to participate in
the new functions described in this document, lie on the path of a the new functions described in this document, lie on the path of a
call or connection, the GMPLS signaling extensions must be such that call or connection, the GMPLS signaling extensions must be such that
those transit nodes are able to participate in the establishment of those transit nodes are able to participate in the establishment of
D.Papadimitriou et al. - Expires March 2004 9
the call or connection by passing the setup information onwards, the call or connection by passing the setup information onwards,
unmodified. unmodified.
Lastly, when a transit or egress node is called upon to support a Lastly, when a transit or egress node is called upon to support a
function described in this document, but does not, the GMPLS function described in this document, but does not, the GMPLS
signaling extensions must be such that they can be rejected by pre- signaling extensions must be such that they can be rejected by pre-
D.Papadimitriou et al. - Expires February 2004 9
existing GMPLS signaling mechanisms in a way that is not detrimental existing GMPLS signaling mechanisms in a way that is not detrimental
to the network as a whole. to the network as a whole.
6. Security Considerations 6. Security Considerations
Per [ITU-T G.8080], a connection cannot be established until the Per [ITU-T G.8080], a connection cannot be established until the
associated call has been set up. Also, policy and authentication associated call has been set up. Also, policy and authentication
procedures are applied prior to the establishment of the call (and procedures are applied prior to the establishment of the call (and
can then also be restricted to connection establishment in the can then also be restricted to connection establishment in the
context of this call). context of this call).
This document introduces no new security requirements to GMPLS This document introduces no new security requirements to GMPLS
signaling (see [RFC3471]). signaling (see [RFC3471]).
7. Acknowledgements 7. Acknowledgements
The authors would like to thank Deborah Brungard, Nic Larkin, Osama The authors would like to thank Nic Larkin, Osama Aboul-Magd and
Aboul-Magd and Dimitrios Pendarakis for their comments and Dimitrios Pendarakis for their comments and contributions to the
contributions to the previous version of this document. previous version of this document, Deborah Brungard for her input
and guidance in our understanding of the ASON model, and Gert
Grammel for his decryption effort during the redaction of some parts
of this document.
8. References 8. References
8.1 Normative References 8.1 Normative References
[RFC-2026] S.Bradner, "The Internet Standards Process -- [RFC-2026] S.Bradner, "The Internet Standards Process --
Revision 3", BCP 9, RFC 2026, October 1996. Revision 3", BCP 9, RFC 2026, October 1996.
[RFC-2119] S.Bradner, "Key words for use in RFCs to Indicate [RFC-2119] S.Bradner, "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
skipping to change at line 522 skipping to change at line 533
[RFC-3471] L.Berger (Editor) et al., "Generalized Multi- [RFC-3471] L.Berger (Editor) et al., "Generalized Multi-
Protocol Label Switching (GMPLS) - Signaling Protocol Label Switching (GMPLS) - Signaling
Functional Description," RFC 3471, January 2003. Functional Description," RFC 3471, January 2003.
[RFC-3473] L.Berger (Editor) et al., "Generalized Multi-Protocol [RFC-3473] L.Berger (Editor) et al., "Generalized Multi-Protocol
Label Switching (GMPLS) Signaling - Resource Label Switching (GMPLS) Signaling - Resource
ReserVation Protocol-Traffic Engineering (RSVP-TE) ReserVation Protocol-Traffic Engineering (RSVP-TE)
Extensions," RFC 3473, January 2003. Extensions," RFC 3473, January 2003.
[ITUT G.8080] ITU-T Rec. G.8080/Y.1304, "Architecture for the [ITUT G.8080] ITU-T Rec. G.8080/Y.1304, "Architecture for the
D.Papadimitriou et al. - Expires March 2004 10
Automatically Switched Optical Network (ASON)," Automatically Switched Optical Network (ASON),"
November 2001 (and Revision, January 2003). November 2001 (and Revision, January 2003).
[GMPLS-CRANK] A.Farrel (Editor), "Crankback Routing Extensions for [GMPLS-CRANK] A.Farrel (Editor), "Crankback Routing Extensions for
MPLS Signaling," Work in Progress, draft-iwata-mpls- MPLS Signaling," Work in Progress, draft-iwata-mpls-
crankback-06.txt, June 2003. crankback-06.txt, June 2003.
[GMPLS-SONET] E.Mannie and D.Papadimitriou (Editors), "GMPLS [GMPLS-SONET] E.Mannie and D.Papadimitriou (Editors), "GMPLS
Extensions for SONET and SDH Control, Work in Extensions for SONET and SDH Control, Work in
D.Papadimitriou et al. - Expires February 2004 10
Progress," draft-ietf-ccamp-gmpls-sonet-sdh-08.txt, Progress," draft-ietf-ccamp-gmpls-sonet-sdh-08.txt,
February 2003. February 2003.
[GMPLS-OTN] D.Papadimitriou (Editor), "GMPLS Signaling Extensions [GMPLS-OTN] D.Papadimitriou (Editor), "GMPLS Signaling Extensions
for G.709 Optical Transport Networks Control," Work for G.709 Optical Transport Networks Control," Work
in progress, draft-ietf-ccamp-gmpls-g709-04.txt, May in progress, draft-ietf-ccamp-gmpls-g709-04.txt, May
2003. 2003.
[GMPLS-OVERLAY]G.Swallow et al., "GMPLS RSVP Support for Overlay
Model," Work in Progress, draft-ietf-ccamp-gmpls-
overlay-01.txt, February 2003.
[GMPLS-VPN] H.Ould-Brahim and Y.Rekhter (Editor), "GVPN Services:
Generalized VPN Services using BGP and GMPLS
Toolkit," Work in Progress, draft-ouldbrahim-ppvpn-
gvpn-bgpgmpls-03.txt, March 2003.
8.2 Informative References 8.2 Informative References
[IPO-ASON] Aboul-Magd (Editor) et al., "Automatic Switched [IPO-ASON] Aboul-Magd (Editor) et al., "Automatic Switched
Optical Network (ASON) Architecture and Its Related Optical Network (ASON) Architecture and Its Related
Protocols," Work in progress, draft-ietf-ipo-ason- Protocols," Work in progress, draft-ietf-ipo-ason-
02.txt, March 2002. 02.txt, March 2002.
[IPO-REQS] Y.Xue (Editor) et al., "Optical Network Service [IPO-REQS] Y.Xue (Editor) et al., "Optical Network Service
Requirements," Work in progress, draft-ietf-ipo- Requirements," Work in progress, draft-ietf-ipo-
carrier-requirements-05.txt. carrier-requirements-05.txt.
skipping to change at line 567 skipping to change at line 587
Dimitri Papadimitriou (Alcatel) Dimitri Papadimitriou (Alcatel)
Francis Wellesplein 1, Francis Wellesplein 1,
B-2018 Antwerpen, Belgium B-2018 Antwerpen, Belgium
Email: dimitri.papadimitriou@alcatel.be Email: dimitri.papadimitriou@alcatel.be
Zhi-Wei Lin (New York City Transit) Zhi-Wei Lin (New York City Transit)
2 Broadway, Room C3.25 2 Broadway, Room C3.25
New York, NY 10004, USA New York, NY 10004, USA
Email: zhiwlin@nyct.com Email: zhiwlin@nyct.com
D.Papadimitriou et al. - Expires March 2004 11
John Drake (Calient) John Drake (Calient)
5853 Rue Ferrari, 5853 Rue Ferrari,
San Jose, CA 95138, USA San Jose, CA 95138, USA
Email: jdrake@calient.net Email: jdrake@calient.net
Adrian Farrel (Old Dog Consulting) Adrian Farrel (Old Dog Consulting)
Email: adrian@olddog.co.uk Email: adrian@olddog.co.uk
Gerald R. Ash (ATT) Gerald R. Ash (ATT)
AT&T Labs, Room MT D5-2A01 AT&T Labs, Room MT D5-2A01
200 Laurel Avenue 200 Laurel Avenue
Middletown, NJ 07748, USA Middletown, NJ 07748, USA
Email: gash@att.com Email: gash@att.com
Lyndon Ong (Ciena) Lyndon Ong (Ciena)
5965 Silver Creek Valley Road 5965 Silver Creek Valley Road
San Jose, CA 95138, USA San Jose, CA 95138, USA
Email: lyong@ciena.com Email: lyong@ciena.com
D.Papadimitriou et al. - Expires February 2004 11 D.Papadimitriou et al. - Expires March 2004 12
Appendix - Terminology Appendix - Terminology
This document makes use of the following terms: This document makes use of the following terms:
Administrative domain: See Recommendation G.805. Administrative domain: See Recommendation G.805.
Call: association between endpoints that supports an instance of a Call: association between endpoints that supports an instance of a
service. service.
skipping to change at line 634 skipping to change at line 655
fault, configuration, accounting and security management fault, configuration, accounting and security management
Management domain: See Recommendation G.805. Management domain: See Recommendation G.805.
Transport plane: provides bi-directional or unidirectional transfer Transport plane: provides bi-directional or unidirectional transfer
of user information, from one location to another. It can also of user information, from one location to another. It can also
provide transfer of some control and network management information. provide transfer of some control and network management information.
The Transport Plane is layered; it is equivalent to the Transport The Transport Plane is layered; it is equivalent to the Transport
Network defined in G.805. Network defined in G.805.
D.Papadimitriou et al. - Expires February 2004 12 D.Papadimitriou et al. - Expires March 2004 13
Full Copyright Statement Full Copyright Statement
"Copyright (C) The Internet Society (2003). All Rights Reserved. "Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph kind, provided that the above copyright notice and this paragraph
skipping to change at line 664 skipping to change at line 685
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
D.Papadimitriou et al. - Expires February 2004 13 D.Papadimitriou et al. - Expires March 2004 14
 End of changes. 

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