draft-ietf-ccamp-gmpls-ason-reqts-03.txt   draft-ietf-ccamp-gmpls-ason-reqts-04.txt 
CCAMP Working Group D. Papadimitriou (Alcatel) CCAMP Working Group D. Papadimitriou (Alcatel)
Internet Draft Z. Lin (New York City Transit) Internet Draft J. Drake (Calient)
Category: Informational J. Drake (Calient) Category: Informational J. Ash (ATT)
J. Ash (ATT) A. Farrel (Old Dog Consulting)
Expiration Date: March 2004 A. Farrel (Old Dog Consulting) Expiration Date: April 2004 L. Ong (Ciena)
L. Ong (Ciena)
September 2003 October 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-03.txt draft-ietf-ccamp-gmpls-ason-reqts-04.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 49
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 March 2004 1 D.Papadimitriou et al. - Expires April 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 93 skipping to change at line 92
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]).
Also, the ASON model distinguishes reference points (representing Also, the ASON model distinguishes reference points (representing
points of protocol information exchange) defined (1) between an points of protocol information exchange) defined (1) between an
administrative domain and a user a.k.a. user-network interface administrative domain and a user a.k.a. user-network interface
(UNI), (2) between (and when needed within) administrative domains (UNI), (2) between (and when needed within) administrative domains
a.k.a. external network-network interface (E-NNI) and, (3) between a.k.a. external network-network interface (E-NNI) and, (3) between
areas of the same administrative domain and when needed between areas of the same administrative domain and when needed between
control components (or simply controllers) within areas a.k.a. control components (or simply controllers) within areas a.k.a.
internal network-network interface (I-NNI). A full description of internal network-network interface (I-NNI).
the ASON terms and relationship between ASON model and GMPLS
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 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
D.Papadimitriou et al. - Expires March 2004 2
(e) extended label association
(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 next sections detail the signaling protocol requirements for
protocols may be applied to the ASON architecture can be found in GMPLS to support the following ASON functions:
[IPO-ASON] and [IPO-REQS]. The former includes a summary of the ASON
functions as well as a detailed discussion of the applicability of
the GMPLS protocol suite.
The next sections detail the requirements concerning the functions
including:
- Support for soft permanent connection capability - Support for soft permanent connection capability
- Support for call and connection separation - Support for call and connection separation
- Support for call segments - Support for call segments
- Support for extended restart capabilities during control plane - Support for extended restart capabilities during control plane
failures failures
- Support for extended label usage - Support for extended label association
- Support for crankback capability - Support for crankback capability
- Support for additional error cases - Support for additional error cases
Also, the support of these functions is strictly independent and The support of these functions must be strictly independent of and
must be agnostic of any user-to-network interface and therefore not agnostic to any user-to-network interface (UNI) and therefore not be
constrained or restricted by its implementation specifics (see [ITU- constrained or restricted by the implementation specifics of the UNI
T G.8080] and [ITU-T G.7713]). (see [ITU-T G.8080] and [ITU-T G.7713]).
In support of the G.8080 end-to-end call model across different In support of the G.8080 end-to-end call model across different
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. This implies that there needs to be a clear mapping of
clear mapping of signaling requests between GMPLS control domains signaling requests between GMPLS control domains and non-GMPLS
and non-GMPLS control domains. This document provides signalling control domains. This document provides signalling requirements for
requirements for G.8080 distributed call and connection management G.8080 distributed call and connection management based on GMPLS,
based on GMPLS, within a GMPLS based control domain and between within a GMPLS based control domain and between GMPLS based control
GMPLS based control domains. It does not restrict use of other domains. It does not restrict use of other protocols within a
protocols within a control domain. Interworking aspects, including control domain. Interworking aspects, including mapping of non-GMPLS
mapping of non-GMPLS protocol signaling requests and support of non- protocol signaling requests and support of non-GMPLS address
GMPLS address formats, are outside the scope of this document. formats, are strictly under the responsibility of the non-GMPLS
control domain, and thus outside the scope of this document.
Any User-Network Interface (UNI) that is compliant with [RFC-3473], Any User-Network Interface (UNI) that is compliant with [RFC 3473],
e.g. [GMPLS-OVERLAY] and [GMPLS-VPN] is considered, by definition, e.g. [GMPLS-OVERLAY] and [GMPLS-VPN] is considered, by definition,
to be a GMPLS UNI and must be supported. 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
4.5 'Support for Extended Label Association' covers the requirements
when a non-GMPLS capable sub-network is introduced or when nodes do
not support any signaling protocols.
D.Papadimitriou et al. - Expires March 2004 3 D.Papadimitriou et al. - Expires March 2004 3
4.5 'Support for Extended Label Usage' covers the requirements when
a non-GMPLS capable sub-network is introduced or when nodes do not
support any signaling protocols.
4.1 Support for Soft Permanent Connection (SPC) Capability 4.1 Support for Soft Permanent Connection (SPC) Capability
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
for any other function described in this document). for any other function described in this document).
The end-to-end connection is thus created by associating the The end-to-end connection is thus created by associating the
incoming interface of the ingress node with the switched connection incoming interface of the ingress node with the switched connection
within the network, and the outgoing interface of the switched within the network, and the outgoing interface of the switched
connection terminating network node (also referred to as egress connection terminating network node (also referred to as egress
node). An SPC connection is illustrated in the following Figure, node). An SPC connection is illustrated in the following Figure.
which shows user's node A connected to a provider's node B via link This shows user's node A connected to a provider's node B via link
#1, user's node Z connected to a provider's node Y via link #3, and #1, user's node Z connected to a provider's node Y via link #3, and
an abstract link #2 connecting provider's node B and node Y. an abstract link #2 connecting provider's node B and node Y. Nodes
B and Y are referred to as the ingress and egress (respectively) of
the network switched connection.
--- --- --- --- --- --- --- ---
| A |--1--| B |-----2-//------| Y |--3--| Z | | A |--1--| B |-----2-//------| Y |--3--| Z |
--- --- --- --- --- --- --- ---
In this instance, the connection on link #1 and link #3 are both In this instance, the connection on link #1 and link #3 are both
provisioned (permanent connections that may be simple links). In provisioned (permanent connections that may be simple links). In
contrast, the connection over link #2 is set up using the contrast, the connection over link #2 is set up using the
distributed control plane. Thus the SPC is composed of the splicing distributed control plane. Thus the SPC is composed of the splicing
of link #1, #2 and #3. of link #1, #2 and #3.
skipping to change at line 212 skipping to change at line 206
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.
D.Papadimitriou et al. - Expires March 2004 4
4.2 Support for Call and Connection Separation 4.2 Support for Call and Connection Separation
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.
A property of a call is to contain zero, one or multiple A property of a call is to contain zero, one or multiple
connections. Within the same call, connections may be of different connections. Within the same call, connections may be of different
types and each connection may exist independently of other types and each connection may exist independently of other
connections, i.e., each connection is setup and released with connections, i.e., each connection is setup and released with
separate Path/Resv messages. For example, a call may contain a set separate signaling messages. For example, a call may contain a set
of basic connections and virtually concatenated connections (see of basic connections and virtually concatenated connections (see
[GMPLS-SONET] for corresponding connection signaling extensions). [GMPLS-SONET] for corresponding connection signaling extensions).
The concept of the call allows for a better flexibility in how end- The concept of the call allows for a better flexibility in how end-
points set up connections and how networks offer services to users. points set up connections and how networks offer services to users.
In essence, a call allows: In essence, a call allows:
- Support for virtual concatenation where each connection can travel - Support for virtual concatenation where each connection can travel
on different diverse paths on different diverse paths
- An upgrade strategy for control plane operations, where a call - An upgrade strategy for control plane operations, where a call
control component (service provisioning) may be separate from the control component (service provisioning) may be separate from the
skipping to change at line 312 skipping to change at line 306
must have the ability to recover the connectivity information of must have the ability to recover the connectivity information of
its neighbors. its neighbors.
- Upon recovery from a control plane failure, calls and connections - Upon recovery from a control plane failure, calls and connections
in the process of being established (i.e. pending call/connection in the process of being established (i.e. pending call/connection
setup requests) should be released or continued (with setup). setup requests) should be released or continued (with setup).
- Upon recovery from a control plane failure, calls and connections - Upon recovery from a control plane failure, calls and connections
in the process of being released must be released. in the process of being released must be released.
- 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 Association
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
D.Papadimitriou et al. - Expires March 2004 6
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.
----- ----- ----- -----
| | --- --- | | | | --- --- | |
| A |---| B |---| C |---| Z | | A |---| B |---| C |---| Z |
| | --- --- | | | | --- --- | |
----- ----- ----- -----
skipping to change at line 372 skipping to change at line 367
- 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.
D.Papadimitriou et al. - Expires March 2004 7
4.6 Support for Crankback 4.6 Support for Crankback
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
requests are simultaneously triggered. requests are simultaneously triggered.
The following mechanisms are assumed during crankback signaling (see The following mechanisms are assumed during crankback signaling:
also [GMPLS-CRANK]):
- the blocking resource (link or node) must be identified and - the blocking resource (link or node) must be identified and
returned in the error response message towards the repair node returned in the error response message towards the repair node
(that may or may not be the ingress node); it is also assumed that (that may or may not be the ingress node); it is also assumed that
this process will occur within a limited period of time this process will occur within a limited period of time
- the computation (from the repair node) of an alternate path around - the computation (from the repair node) of an alternate path around
the blocking link or node satisfying the initial connection the blocking link or node satisfying the initial connection
constraints constraints
- the re-initiation of the connection setup request from the repair - the re-initiation of the connection setup request from the repair
node (i.e. the node that has intercepted and processed the error node (i.e. the node that has intercepted and processed the error
response message) response message)
The following properties are expected for crankback signaling (see The following properties are expected for crankback signaling:
[GMPLS-CRANK]):
- Error information persistence: the entity that computes the - Error information persistence: the entity that computes the
alternate (re-routing) path should store the identifiers of the alternate (re-routing) path should store the identifiers of the
blocking resources as indicated in the error message until the blocking resources as indicated in the error message until the
connection is successfully established or until the node abandons connection is successfully established or until the node abandons
rerouting attempts. Since crankback may happen more than once while rerouting attempts. Since crankback may happen more than once
establishing a specific connection, the history of all experienced while establishing a specific connection, the history of all
blockages for this connection should be maintained (at least until experienced blockages for this connection should be maintained (at
the routing protocol updates the state of this information) to least until the routing protocol updates the state of this
perform an accurate path computation avoiding all blockages. information) to perform an accurate path computation avoiding all
blockages.
- 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
of retries should be strictly limited. The maximum number of number of retries should be strictly limited. The maximum number
crankback rerouting attempts allowed can be limited per connection, of crankback rerouting attempts allowed can be limited per
per node, per area or even per administrative domain. connection, 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
should send an error message upstream indicating "Maximum
number of re-routings exceeded". This error message will be D.Papadimitriou et al. - Expires March 2004 8
sent back to the ingress node with no further rerouting failure should send an error message upstream indicating
attempts. Then, the ingress node may choose to retry the "Maximum number of re-routings exceeded". This error message
connection setup according to local policy but also re-use its will be sent back to the ingress node with no further
original path or compute a path that avoids the blocking rerouting attempts. Then, the ingress node may choose to
resources. retry the connection setup according to local policy but also
re-use its original path or compute a path that avoids the
blocking 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
the next repair point. the next repair point.
4.7 Support for Additional Error Cases 4.7 Support for Additional Error Cases
To support the ASON network, the following additional category of To support the ASON network, the following additional category of
error cases are defined: error cases are defined:
skipping to change at line 479 skipping to change at line 473
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
D.Papadimitriou et al. - Expires March 2004 9
signaling extensions must be such that they can be rejected by pre- signaling extensions must be such that they can be rejected by pre-
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], it is not possible to establish a connection
associated call has been set up. Also, policy and authentication until the associated call has been set up. Also, policy and
procedures are applied prior to the establishment of the call (and authentication procedures are applied prior to the establishment of
can then also be restricted to connection establishment in the the call (and can then also be restricted to connection
context of this call). establishment in the 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 Nic Larkin, Osama Aboul-Magd and The authors would like to thank Nic Larkin, Osama Aboul-Magd and
Dimitrios Pendarakis for their comments and contributions to the Dimitrios Pendarakis for their contribution to the previous version
previous version of this document, Deborah Brungard for her input of this document, Zhi-Wei Lin for his contribution to this document,
and guidance in our understanding of the ASON model, and Gert Deborah Brungard for her input and guidance in our understanding of
Grammel for his decryption effort during the redaction of some parts the ASON model, and Gert Grammel for his decryption effort during
of this document. 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.
[RFC-3209] D.Awduche et al., "RSVP-TE: Extensions to RSVP for [RFC 3209] D.Awduche et al., "RSVP-TE: Extensions to RSVP for
LSP Tunnels," RFC 3209, December 2001. LSP Tunnels," RFC 3209, December 2001.
[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 [ITU-T 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 D.Papadimitriou et al. - Expires March 2004 10
MPLS Signaling," Work in Progress, draft-iwata-mpls-
crankback-06.txt, June 2003.
[GMPLS-SONET] E.Mannie and D.Papadimitriou (Editors), "GMPLS 8.2 Informative References
Extensions for SONET and SDH Control, Work in
Progress," draft-ietf-ccamp-gmpls-sonet-sdh-08.txt,
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 [GMPLS-OVERLAY]G.Swallow et al., "GMPLS RSVP Support for Overlay
Model," Work in Progress, draft-ietf-ccamp-gmpls- Model," Work in Progress, draft-ietf-ccamp-gmpls-
overlay-01.txt, February 2003. overlay-01.txt, February 2003.
[GMPLS-SONET] E.Mannie and D.Papadimitriou (Editors), "GMPLS
Extensions for SONET and SDH Control, Work in
Progress," draft-ietf-ccamp-gmpls-sonet-sdh-08.txt,
February 2003.
[GMPLS-VPN] H.Ould-Brahim and Y.Rekhter (Editor), "GVPN Services: [GMPLS-VPN] H.Ould-Brahim and Y.Rekhter (Editor), "GVPN Services:
Generalized VPN Services using BGP and GMPLS Generalized VPN Services using BGP and GMPLS
Toolkit," Work in Progress, draft-ouldbrahim-ppvpn- Toolkit," Work in Progress, draft-ouldbrahim-ppvpn-
gvpn-bgpgmpls-03.txt, March 2003. gvpn-bgpgmpls-03.txt, March 2003.
8.2 Informative References [ITU-T G.7713] ITU-T Rec. G.7713/Y.1304, "Distributed Call and
[IPO-ASON] Aboul-Magd (Editor) et al., "Automatic Switched
Optical Network (ASON) Architecture and Its Related
Protocols," Work in progress, draft-ietf-ipo-ason-
02.txt, March 2002.
[IPO-REQS] Y.Xue (Editor) et al., "Optical Network Service
Requirements," Work in progress, draft-ietf-ipo-
carrier-requirements-05.txt.
[ITUT G.7713] ITU-T Rec. G.7713/Y.1304, "Distributed Call and
Connection Management," November 2001. Connection Management," November 2001.
9. Author's Addresses 9. Author's Addresses
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 Phone: +32 3 2408491
EMail: dimitri.papadimitriou@alcatel.be
Zhi-Wei Lin (New York City Transit)
2 Broadway, Room C3.25
New York, NY 10004, USA
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
Email: adrian@olddog.co.uk Old Dog Consulting
Phone: +44 (0) 1978 860944
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 March 2004 12 D.Papadimitriou et al. - Expires March 2004 11
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 633 skipping to change at line 611
functions. Through signaling, the control plane sets up and releases functions. Through signaling, the control plane sets up and releases
connections, and may restore a connection in case of a failure. connections, and may restore a connection in case of a failure.
(Control) Domain: represents a collection of entities that are (Control) Domain: represents a collection of entities that are
grouped for a particular purpose. G.8080 applies this G.805 grouped for a particular purpose. G.8080 applies this G.805
recommendation concept (that defines two particular forms, the recommendation concept (that defines two particular forms, the
administrative domain and the management domain) to the control administrative domain and the management domain) to the control
plane in the form of a control domain. The entities that are grouped plane in the form of a control domain. The entities that are grouped
in a control domain are components of the control plane. in a control domain are components of the control plane.
External NNI: interfaces are located between protocol controllers External NNI (E-NNI): interfaces are located between protocol
between control domains. controllers between control domains.
Internal NNI: interfaces are located between protocol controllers Internal NNI (I-NNI): interfaces are located between protocol
within control domains. controllers within control domains.
Link: See Recommendation G.805. Link: See Recommendation G.805.
Management plane: performs management functions for the Transport Management plane: performs management functions for the Transport
Plane, the control plane and the system as a whole. It also provides Plane, the control plane and the system as a whole. It also provides
coordination between all the planes. The following management coordination between all the planes. The following management
functional areas are performed in the management plane: performance, functional areas are performed in the management plane: performance,
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 March 2004 13 User Network Interface (UNI): interfaces are located between
protocol controllers between a user and a control domain.
D.Papadimitriou et al. - Expires March 2004 12
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 685 skipping to change at line 666
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 March 2004 14 D.Papadimitriou et al. - Expires March 2004 13
 End of changes. 

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