draft-ietf-ccamp-rwa-info-24.txt   rfc7446.txt 
Network Working Group Y. Lee
Internet Draft Huawei
Intended status: Informational G. Bernstein
Expires: June 2015 Grotto Networking
D. Li
Huawei
W. Imajuku
NTT
December 4, 2014 Internet Engineering Task Force (IETF) Y. Lee, Ed.
Request for Comments: 7446 Huawei
Routing and Wavelength Assignment Information Model for Wavelength Category: Informational G. Bernstein, Ed.
Switched Optical Networks ISSN: 2070-1721 Grotto Networking
D. Li
draft-ietf-ccamp-rwa-info-24.txt Huawei
W. Imajuku
NTT
February 2015
Status of this Memo Routing and Wavelength Assignment Information Model
for Wavelength Switched Optical Networks
This Internet-Draft is submitted to IETF in full conformance with Abstract
the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This document provides a model of information needed by the Routing
Task Force (IETF), its areas, and its working groups. Note that and Wavelength Assignment (RWA) process in Wavelength Switched
other groups may also distribute working documents as Internet- Optical Networks (WSONs). The purpose of the information described
Drafts. in this model is to facilitate constrained optical path computation
in WSONs. This model takes into account compatibility constraints
between WSON signal attributes and network elements but does not
include constraints due to optical impairments. Aspects of this
information that may be of use to other technologies utilizing a
GMPLS control plane are discussed.
Internet-Drafts are draft documents valid for a maximum of six Status of This Memo
months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at This document is not an Internet Standards Track specification; it is
http://www.ietf.org/ietf/1id-abstracts.txt published for informational purposes.
The list of Internet-Draft Shadow Directories can be accessed at This document is a product of the Internet Engineering Task Force
http://www.ietf.org/shadow.html (IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
This Internet-Draft will expire on June 4, 2015. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7446.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with respect
respect to this document. Code Components extracted from this to this document. Code Components extracted from this document must
document must include Simplified BSD License text as described in include Simplified BSD License text as described in Section 4.e of
Section 4.e of the Trust Legal Provisions and are provided without the Trust Legal Provisions and are provided without warranty as
warranty as described in the Simplified BSD License. described in the Simplified BSD License.
Abstract
This document provides a model of information needed by the routing
and wavelength assignment (RWA) process in wavelength switched
optical networks (WSONs). The purpose of the information described
in this model is to facilitate constrained lightpath computation in
WSONs. This model takes into account compatibility constraints
between WSON signal attributes and network elements but does not
include constraints due to optical impairments. Aspects of this
information that may be of use to other technologies utilizing a
GMPLS control plane are discussed.
Table of Contents Table of Contents
1. Introduction...................................................3 1. Introduction ....................................................3
2. Terminology....................................................3 2. Terminology .....................................................3
3. Routing and Wavelength Assignment Information Model............4 3. Routing and Wavelength Assignment Information Model .............3
3.1. Dynamic and Relatively Static Information.................4 3.1. Dynamic and Relatively Static Information ..................4
4. Node Information (General).....................................5 4. Node Information (General) ......................................4
4.1. Connectivity Matrix.......................................5 4.1. Connectivity Matrix ........................................5
5. Node Information (WSON specific)...............................6 5. Node Information (WSON Specific) ................................5
5.1. Resource Accessibility/Availability.......................7 5.1. Resource Accessibility/Availability ........................7
5.2. Resource Signal Constraints and Processing Capabilities..11 5.2. Resource Signal Constraints and Processing Capabilities ...11
5.3. Compatibility and Capability Details.....................12 5.3. Compatibility and Capability Details ......................12
5.3.1. Shared Input or Output Indication...................12 5.3.1. Shared Input or Output Indication ..................12
5.3.2. Optical Interface Class List........................13 5.3.2. Optical Interface Class List .......................12
5.3.3. Acceptable Client Signal List.......................13 5.3.3. Acceptable Client Signal List ......................13
5.3.4. Processing Capability List..........................13 5.3.4. Processing Capability List .........................13
6. Link Information (General)....................................14 6. Link Information (General) .....................................13
6.1. Administrative Group.....................................14 6.1. Administrative Group ......................................14
6.2. Interface Switching Capability Descriptor................15 6.2. Interface Switching Capability Descriptor .................14
6.3. Link Protection Type (for this link).....................15 6.3. Link Protection Type (for This Link) ......................14
6.4. Shared Risk Link Group Information.......................15 6.4. Shared Risk Link Group Information ........................14
6.5. Traffic Engineering Metric...............................15 6.5. Traffic Engineering Metric ................................15
6.6. Port Label Restrictions..................................15 6.6. Port Label Restrictions ...................................15
6.6.1. Port-Wavelength Exclusivity Example.................18 6.6.1. Port-Wavelength Exclusivity Example ................17
7. Dynamic Components of the Information Model...................19 7. Dynamic Components of the Information Model ....................18
7.1. Dynamic Link Information (General).......................20 7.1. Dynamic Link Information (General) ........................19
7.2. Dynamic Node Information (WSON Specific).................20 7.2. Dynamic Node Information (WSON Specific) ..................19
8. Security Considerations.......................................20 8. Security Considerations ........................................19
9. IANA Considerations...........................................21 9. References .....................................................20
10. Acknowledgments..............................................21 9.1. Normative References ......................................20
11. References...................................................22 9.2. Informative References ....................................21
11.1. Normative References....................................22 Contributors ......................................................22
11.2. Informative References..................................23 Authors' Addresses ................................................23
12. Contributors.................................................24
Authors' Addresses...............................................25
Intellectual Property Statement..................................25
Disclaimer of Validity...........................................26
1. Introduction 1. Introduction
The purpose of the WSONs information model described in this The purpose of the WSON information model described in this document
document is to facilitate constrained lightpath computation and as is to facilitate constrained optical path computation, and as such it
such is not a general purpose network management information model. is not a general-purpose network management information model. This
This constraint is frequently referred to as the "wavelength constraint is frequently referred to as the "wavelength continuity"
continuity" constraint, and the corresponding constrained lightpath constraint, and the corresponding constrained optical path
computation is known as the routing and wavelength assignment (RWA) computation is known as the Routing and Wavelength Assignment (RWA)
problem. Hence the information model must provide sufficient problem. Hence, the information model must provide sufficient
topology and wavelength restriction and availability information to topology and wavelength restriction and availability information to
support this computation. More details on the RWA process and WSON support this computation. More details on the RWA process and WSON
subsystems and their properties can be found in [RFC6163]. The model subsystems and their properties can be found in [RFC6163]. The model
defined here includes constraints between WSON signal attributes and defined here includes constraints between WSON signal attributes and
network elements, but does not include optical impairments. network elements but does not include optical impairments.
In addition to presenting an information model suitable for path In addition to presenting an information model suitable for path
computation in WSON, this document also highlights model aspects computation in WSON, this document also highlights model aspects that
that may have general applicability to other technologies utilizing may have general applicability to other technologies utilizing a
a GMPLS control plane. The portion of the information model GMPLS control plane. The portion of the information model applicable
applicable to other technologies beyond WSON is referred to as to technologies beyond WSON is referred to as "general" to
"general" to distinguish it from the "WSON-specific" portion that is distinguish it from the "WSON-specific" portion that is applicable
applicable only to WSON technology. only to WSON technology.
2. Terminology 2. Terminology
Refer to [RFC6163] for Reconfigurable Optical Add/Drop Multiplexer Refer to [RFC6163] for definitions of Reconfigurable Optical Add/Drop
(ROADM), RWA, Wavelength Conversion, Wavelength Division Multiplexer (ROADM), RWA, Wavelength Conversion, Wavelength Division
Multiplexing (WDM) and WSON. Multiplexing (WDM), WSON, and other related terminology used in this
document.
3. Routing and Wavelength Assignment Information Model 3. Routing and Wavelength Assignment Information Model
The WSON RWA information model in this document comprises four The WSON RWA information model in this document comprises four
categories of information. The categories are independent of whether categories of information. The categories are independent of whether
the information comes from a switching subsystem or from a line the information comes from a switching subsystem or from a line
subsystem -- a switching subsystem refers to WSON nodes such as subsystem -- a switching subsystem refers to WSON nodes such as a
ROADM or Optical Add/Drop Multiplexer (OADM), and a line subsystem ROADM or an Optical Add/Drop Multiplexer (OADM), and a line subsystem
refers to devices such as WDM or Optical Amplifier. The categories refers to devices such as WDM or Optical Amplifier. The categories
are these: are these:
o Node Information o Node Information
o Link Information o Link Information
o Dynamic Node Information o Dynamic Node Information
o Dynamic Link Information o Dynamic Link Information
Note that this is roughly the categorization used in Section 7 of
[G.7715].
Note that this is roughly the categorization used in [G.7715] In the following, where applicable, the Reduced Backus-Naur Form
section 7.
In the following, where applicable, the reduced Backus-Naur form
(RBNF) syntax of [RBNF] is used to aid in defining the RWA (RBNF) syntax of [RBNF] is used to aid in defining the RWA
information model. information model.
3.1. Dynamic and Relatively Static Information 3.1. Dynamic and Relatively Static Information
All the RWA information of concern in a WSON network is subject to All the RWA information of concern in a WSON network is subject to
change over time. Equipment can be upgraded; links may be placed in change over time. Equipment can be upgraded; links may be placed in
or out of service and the like. However, from the point of view of or out of service and the like. However, from the point of view of
RWA computations there is a difference between information that can RWA computations, there is a difference between information that can
change with each successive connection establishment in the network change with each successive connection establishment in the network
and that information that is relatively static and independent of and information that is relatively static and independent of
connection establishment. A key example of the former is link connection establishment. A key example of the former is link
wavelength usage since this can change with connection wavelength usage since this can change with connection setup/teardown
setup/teardown and this information is a key input to the RWA and this information is a key input to the RWA process. Examples of
process. Examples of relatively static information are the relatively static information are the potential port connectivity of
potential port connectivity of a WDM ROADM, and the channel spacing a WDM ROADM, and the channel spacing on a WDM link.
on a WDM link.
This document separates, where possible, dynamic and static This document separates, where possible, dynamic and static
information so that these can be kept separate in possible encodings information so that these can be kept separate in possible encodings.
and hence allowing for separate updates of these two types of This allows for separate updates of these two types of information,
information thereby reducing processing and traffic load caused by thereby reducing processing and traffic load caused by the timely
the timely distribution of the more dynamic RWA WSON information. distribution of the more dynamic RWA WSON information.
4. Node Information (General) 4. Node Information (General)
The node information described here contains the relatively static The node information described here contains the relatively static
information related to a WSON node. This includes connectivity information related to a WSON node. This includes connectivity
constraints amongst ports and wavelengths since WSON switches can constraints amongst ports and wavelengths since WSON switches can
exhibit asymmetric switching properties. Additional information exhibit asymmetric switching properties. Additional information
could include properties of wavelength converters in the node if any could include properties of wavelength converters in the node, if any
are present. In [Switch] it was shown that the wavelength are present. In [Switch] it was shown that the wavelength
connectivity constraints for a large class of practical WSON devices connectivity constraints for a large class of practical WSON devices
can be modeled via switched and fixed connectivity matrices along can be modeled via switched and fixed connectivity matrices along
with corresponding switched and fixed port constraints. These with corresponding switched and fixed port constraints. These
connectivity matrices are included with the node information while connectivity matrices are included with the node information, while
the switched and fixed port wavelength constraints are included with the switched and fixed port wavelength constraints are included with
the link information. the link information.
Formally, Formally,
<Node_Information> ::= <Node_ID> [<ConnectivityMatrix>...] <Node_Information> ::= <Node_ID> [<ConnectivityMatrix>...]
Where the Node_ID would be an appropriate identifier for the node Where the Node_ID would be an appropriate identifier for the node
within the WSON RWA context. within the WSON RWA context.
Note that multiple connectivity matrices are allowed and hence can Note that multiple connectivity matrices are allowed and hence can
fully support the most general cases enumerated in [Switch]. fully support the most-general cases enumerated in [Switch].
4.1. Connectivity Matrix 4.1. Connectivity Matrix
The connectivity matrix (ConnectivityMatrix) represents either the The connectivity matrix (ConnectivityMatrix) represents either the
potential connectivity matrix for asymmetric switches (e.g. ROADMs potential connectivity matrix for asymmetric switches (e.g., ROADMs
and such) or fixed connectivity for an asymmetric device such as a and such) or fixed connectivity for an asymmetric device such as a
multiplexer. Note that this matrix does not represent any particular multiplexer. Note that this matrix does not represent any particular
internal blocking behavior but indicates which input ports and internal blocking behavior but indicates which input ports and
wavelengths could possibly be connected to a particular output port. wavelengths could possibly be connected to a particular output port.
Representing internal state dependent blocking for a switch or ROADM For a switch or ROADM, representing blocking that is dependent on the
is beyond the scope of this document and due to its highly internal state is beyond the scope of this document. Due to its
implementation dependent nature would most likely not be subject to highly implementation-dependent nature, it would most likely not be
standardization in the future. The connectivity matrix is a subject to standardization in the future. The connectivity matrix is
conceptual M by N matrix representing the potential switched or a conceptual M by N matrix representing the potential switched or
fixed connectivity, where M represents the number of input ports and fixed connectivity, where M represents the number of input ports and
N the number of output ports. This is a "conceptual" matrix since N the number of output ports. This is a "conceptual" matrix since
the matrix tends to exhibit structure that allows for very compact the matrix tends to exhibit structure that allows for very compact
representations that are useful for both transmission and path representations that are useful for both transmission and path
computation. computation.
Note that the connectivity matrix information element can be useful Note that the connectivity matrix information element can be useful
in any technology context where asymmetric switches are utilized. in any technology context where asymmetric switches are utilized.
<ConnectivityMatrix> ::= <MatrixID> <ConnectivityMatrix> ::= <MatrixID>
<ConnType> <ConnType>
skipping to change at page 6, line 22 skipping to change at page 5, line 47
<MatrixID> is a unique identifier for the matrix. <MatrixID> is a unique identifier for the matrix.
<ConnType> can be either 0 or 1 depending upon whether the <ConnType> can be either 0 or 1 depending upon whether the
connectivity is either fixed or switched. connectivity is either fixed or switched.
<Matrix> represents the fixed or switched connectivity in that <Matrix> represents the fixed or switched connectivity in that
Matrix(i, j) = 0 or 1 depending on whether input port i can connect Matrix(i, j) = 0 or 1 depending on whether input port i can connect
to output port j for one or more wavelengths. to output port j for one or more wavelengths.
5. Node Information (WSON specific) 5. Node Information (WSON Specific)
As discussed in [RFC6163] a WSON node may contain electro-optical As discussed in [RFC6163], a WSON node may contain electro-optical
subsystems such as regenerators, wavelength converters or entire subsystems such as regenerators, wavelength converters or entire
switching subsystems. The model present here can be used in switching subsystems. The model present here can be used in
characterizing the accessibility and availability of limited characterizing the accessibility and availability of limited
resources such as regenerators or wavelength converters as well as resources such as regenerators or wavelength converters as well as
WSON signal attribute constraints of electro-optical subsystems. As WSON signal attribute constraints of electro-optical subsystems. As
such this information element is fairly specific to WSON such, this information element is fairly specific to WSON
technologies. technologies.
In this document, the term "resource" is used to refer to a physical
component of a WSON node such as a regenerator or a wavelength
converter. Multiple instances of such components are often present
within a single WSON node. This term is not to be confused with the
concept of forwarding or switching resources such as bandwidth or
lambdas.
A WSON node may include regenerators or wavelength converters A WSON node may include regenerators or wavelength converters
arranged in a shared pool. As discussed in [RFC6163] this can arranged in a shared pool. As discussed in [RFC6163], a WSON node
include OEO based WDM switches as well. There are a number of can also include WDM switches that use optical-electronic-optical
different approaches used in the design of WDM switches containing (OEO) processing. There are a number of different approaches used in
regenerator or converter pools. However, from the point of view of the design of WDM switches containing regenerator or converter pools.
path computation the following need to be known: However, from the point of view of path computation, the following
need to be known:
1. The nodes that support regeneration or wavelength conversion. 1. The nodes that support regeneration or wavelength conversion.
2. The accessibility and availability of a wavelength converter to 2. The accessibility and availability of a wavelength converter to
convert from a given input wavelength on a particular input port convert from a given input wavelength on a particular input port
to a desired output wavelength on a particular output port. to a desired output wavelength on a particular output port.
3. Limitations on the types of signals that can be converted and the 3. Limitations on the types of signals that can be converted and the
conversions that can be performed. conversions that can be performed.
Since resources tend to be packaged together in blocks of similar Since resources tend to be packaged together in blocks of similar
devices, e.g., on line cards or other types of modules, the devices, e.g., on line cards or other types of modules, the
fundamental unit of identifiable resource in this document is the fundamental unit of identifiable resource in this document is the
"resource block". A resource block may contain one or more "resource block".
resources. A resource is the smallest identifiable unit of
processing allocation. One can group together resources into blocks
if they have similar characteristics relevant to the optical system
being modeled, e.g., processing properties, accessibility, etc.
This leads to the following formal high level model: A resource block is a collection of resources from the same WSON node
that are grouped together for administrative reasons and for ease of
encoding in the protocols. All resources in the same resource block
behave in the same way and have similar characteristics relevant to
the optical system, e.g., processing properties, accessibility, etc.
A resource pool is a collection of resource blocks for the purpose of
representing throughput or cross-connect capabilities in a WSON node.
A resource pool associates input ports or links on the node with
output ports or links and is used to indicate how signals may be
passed from an input port or link to an output port or link by way of
a resource block (in other words, by way of a resource). A resource
pool may, therefore, be modeled as a matrix.
A resource block may be present in multiple resource pools.
This leads to the following formal high-level model:
<Node_Information> ::= <Node_ID> <Node_Information> ::= <Node_ID>
[<ConnectivityMatrix>...] [<ConnectivityMatrix>...]
[<ResourcePool>] [<ResourcePool>]
Where Where
<ResourcePool> ::= <ResourceBlockInfo>... <ResourcePool> ::= <ResourceBlockInfo>...
[<ResourceAccessibility>...] [<ResourceAccessibility>...]
[<ResourceWaveConstraints>...] [<ResourceWaveConstraints>...]
[<RBPoolState>] [<RBPoolState>]
First the accessibility of resource blocks is addressed then their First, the accessibility of resource blocks is addressed; then, their
properties are discussed. properties are discussed.
5.1. Resource Accessibility/Availability 5.1. Resource Accessibility/Availability
A similar technique as used to model ROADMs and optical switches can A similar technique as used to model ROADMs, and optical switches can
be used to model regenerator/converter accessibility. This technique be used to model regenerator/converter accessibility. This technique
was generally discussed in [RFC6163] and consisted of a matrix to was generally discussed in [RFC6163] and consisted of a matrix to
indicate possible connectivity along with wavelength constraints for indicate possible connectivity along with wavelength constraints for
links/ports. Since regenerators or wavelength converters may be links/ports. Since regenerators or wavelength converters may be
considered a scarce resource it is desirable that the model include, considered a scarce resource, it is desirable that the model include,
if desired, the usage state (availability) of individual if desired, the usage state (availability) of individual regenerators
regenerators or converters in the pool. Models that incorporate more or converters in the pool. Models that incorporate more state to
state to further reveal blocking conditions on input or output to further reveal blocking conditions on input or output to particular
particular converters are for further study and not included here. converters are for further study and not included here.
The three stage model is shown schematically in Figure 1 and Figure The three-stage model is shown schematically in Figures 1 and 2. The
2. The difference between the two figures is that Figure 1 assumes difference between the two figures is that in Figure 1 it's assumed
that each signal that can get to a resource block may do so, while that each signal that can get to a resource block may do so, while in
in Figure 2 the access to sets of resource blocks is via a shared Figure 2 the access to sets of resource blocks is via a shared fiber
fiber which imposes its own wavelength collision constraint. The that imposes its own wavelength collision constraint. Figure 1 shows
representation of Figure 1 can have more than one input to each that there can be more than one input to each resource block since
resource block since each input represents a single wavelength each input represents a single wavelength signal, while Figure 2
signal, while in Figure 2 shows a single multiplexed WDM input or shows a single WDM input or output, e.g., a fiber, to/from each set
output, e.g., a fiber, to/from each set of block. of blocks.
This model assumes N input ports (fibers), P resource blocks This model assumes N input ports (fibers), P resource blocks
containing one or more identical resources (e.g. wavelength containing one or more identical resources (e.g., wavelength
converters), and M output ports (fibers). Since not all input ports converters), and M output ports (fibers). Since not all input ports
can necessarily reach each resource block, the model starts with a can necessarily reach each resource block, the model starts with a
resource pool input matrix RI(i,p) = {0,1} whether input port i can resource pool input matrix RI(i,p) = {0,1} depending on whether input
potentially reach resource block p. port i can potentially reach resource block p.
Since not all wavelengths can necessarily reach all the resources or Since not all wavelengths can necessarily reach all the resources or
the resources may have limited input wavelength range the model has the resources may have limited input wavelength range, the model has
a set of relatively static input port constraints for each resource. a set of relatively static input port constraints for each resource.
In addition, if the access to a set of resource blocks is via a In addition, if the access to a set of resource blocks is via a
shared fiber (Figure 2) this would impose a dynamic wavelength shared fiber (Figure 2), this would impose a dynamic wavelength
availability constraint on that shared fiber. The resource block availability constraint on that shared fiber. The resource block
input port constraint is modeled via a static wavelength set input port constraint is modeled via a static wavelength set
mechanism and the case of shared access to a set of blocks is mechanism, and the case of shared access to a set of blocks is
modeled via a dynamic wavelength set mechanism. modeled via a dynamic wavelength set mechanism.
Next a state vector RA(j) = {0,...,k} is used to track the number of Next, a state vector RA(j) = {0,...,k} is used to track the number of
resources in resource block j in use. This is the only state kept in resources in resource block j in use. This is the only state kept in
the resource pool model. This state is not necessary for modeling the resource pool model. This state is not necessary for modeling
"fixed" transponder system or full OEO switches with WDM interfaces, "fixed" transponder system or full OEO switches with WDM interfaces,
i.e., systems where there is no sharing. i.e., systems where there is no sharing.
After that, a set of static resource output wavelength constraints After that, a set of static resource output wavelength constraints
and possibly dynamic shared output fiber constraints maybe used. The and possibly dynamic shared output fiber constraints maybe used. The
static constraints indicate what wavelengths a particular resource static constraints indicate what wavelengths a particular resource
block can generate or are restricted to generating e.g., a fixed block can generate or is restricted to generating, e.g., a fixed
regenerator would be limited to a single lambda. The dynamic regenerator would be limited to a single lambda. The dynamic
constraints would be used in the case where a single shared fiber is constraints would be used in the case where a single shared fiber is
used to output the resource block (Figure 2). used to output the resource block (Figure 2).
Finally, to complete the model, a resource pool output matrix Finally, to complete the model, a resource pool output matrix RE(p,k)
RE(p,k) = {0,1} depending on whether the output from resource block = {0,1} depending on whether the output from resource block p can
p can reach output port k, may be used. reach output port k, may be used.
I1 +-------------+ +-------------+ O1 I1 +-------------+ +-------------+ O1
----->| | +--------+ | |-----> ----->| | +--------+ | |----->
I2 | +------+ Rb #1 +-------+ | O2 I2 | +------+ Rb #1 +-------+ | O2
----->| | +--------+ | |-----> ----->| | +--------+ | |----->
| | | | | | | |
| Resource | +--------+ | Resource | | Resource | +--------+ | Resource |
| Pool +------+ +-------+ Pool | | Pool +------+ +-------+ Pool |
| | + Rb #2 + | | | | + Rb #2 + | |
| Input +------+ +-------| Output | | Input +------+ +-------| Output |
skipping to change at page 9, line 31 skipping to change at page 9, line 31
+-------------+ ^ ^ +-------------+ +-------------+ ^ ^ +-------------+
| | | |
| | | |
| | | |
| | | |
Input wavelength Output wavelength Input wavelength Output wavelength
constraints for constraints for constraints for constraints for
each resource each resource each resource each resource
Note: Rb is a Resource Block. Note: Rb is a resource block.
Figure 1 Schematic diagram of resource pool model. Figure 1: Schematic Diagram of the Resource Pool Model
I1 +-------------+ +-------------+ O1 I1 +-------------+ +-------------+ O1
----->| | +--------+ | |-----> ----->| | +--------+ | |----->
I2 | +======+ Rb #1 +-+ | | O2 I2 | +======+ Rb #1 +-+ | | O2
----->| | +--------+ | | |-----> ----->| | +--------+ | | |----->
| | |=====| | | | |=====| |
| Resource | +--------+ | | Resource | | Resource | +--------+ | | Resource |
| Pool | +-+ Rb #2 +-+ | Pool | | Pool | +-+ Rb #2 +-+ | Pool |
| | | +--------+ | | | | | +--------+ | |
| Input |====| | Output | | Input |====| | Output |
skipping to change at page 10, line 33 skipping to change at page 10, line 33
+-------------+ ^ ^ +-------------+ +-------------+ ^ ^ +-------------+
| | | |
| | | |
| | | |
Single (shared) fibers for block input and output Single (shared) fibers for block input and output
Input wavelength Output wavelength Input wavelength Output wavelength
availability for availability for availability for availability for
each block input fiber each block output fiber each block input fiber each block output fiber
Note: Rb is a Resource Block. Note: Rb is a resource block.
Figure 2 Schematic diagram of resource pool model with shared block Figure 2: Schematic Diagram of the Resource Pool Model with
accessibility. Shared Block Accessibility
Formally the model can be specified as: Formally, the model can be specified as:
<ResourceAccessibility> ::= <PoolInputMatrix> <ResourceAccessibility> ::= <PoolInputMatrix>
<PoolOutputMatrix> <PoolOutputMatrix>
<ResourceWaveConstraints> ::= <InputWaveConstraints> <ResourceWaveConstraints> ::= <InputWaveConstraints>
<OutputOutputWaveConstraints> <OutputWaveConstraints>
<RBSharedAccessWaveAvailability> ::= [<InAvailableWavelengths>] <RBSharedAccessWaveAvailability> ::= [<InAvailableWavelengths>]
[<OutAvailableWavelengths>] [<OutAvailableWavelengths>]
<RBPoolState> ::= <ResourceBlockID> <RBPoolState> ::= <ResourceBlockID>
<NumResourcesInUse> <NumResourcesInUse>
[<RBSharedAccessWaveAvailability>] [<RBSharedAccessWaveAvailability>]
[<RBPoolState>] [<RBPoolState>]
Note that except for <RBPoolState> all the other components of Note that, except for <RBPoolState>, all the components of
<ResourcePool> are relatively static. Also the <ResourcePool> are relatively static. Also, the
<InAvailableWavelengths> and <OutAvailableWavelengths> are only used <InAvailableWavelengths> and <OutAvailableWavelengths> are only used
in the cases of shared input or output access to the particular in the cases of shared input or output access to the particular
block. See the resource block information in the next section to see block. See the resource block information in the next section for
how this is specified. how this is specified.
5.2. Resource Signal Constraints and Processing Capabilities 5.2. Resource Signal Constraints and Processing Capabilities
The wavelength conversion abilities of a resource (e.g. regenerator, The wavelength conversion abilities of a resource (e.g., regenerator,
wavelength converter) were modeled in the <OutputWaveConstraints> wavelength converter) were modeled in the <OutputWaveConstraints>
previously discussed. As discussed in [RFC6163] the constraints on previously discussed. As discussed in [RFC6163], the constraints on
an electro-optical resource can be modeled in terms of input an electro-optical resource can be modeled in terms of input
constraints, processing capabilities, and output constraints: constraints, processing capabilities, and output constraints:
<ResourceBlockInfo> ::= <ResourceBlockSet> <ResourceBlockInfo> ::= <ResourceBlockSet>
[<InputConstraints>] [<InputConstraints>]
[<ProcessingCapabilities>] [<ProcessingCapabilities>]
[<OutputConstraints>] [<OutputConstraints>]
Where <ResourceBlockSet> is a list of resource block identifiers Where <ResourceBlockSet> is a list of resource block identifiers
with the same characteristics. If this set is missing the with the same characteristics. If this set is missing, the
constraints are applied to the entire network element. constraints are applied to the entire network element.
The <InputConstraints> are signal compatibility based constraints The <InputConstraints> are constraints are based on signal
and/or shared access constraint indication. The details of these compatibility and/or shared access constraint indication. The
constraints are defined in section 5.3. details of these constraints are defined in Section 5.3.
<InputConstraints> ::= <SharedInput> <InputConstraints> ::= <SharedInput>
[<OpticalInterfaceClassList>] [<OpticalInterfaceClassList>]
[<ClientSignalList>] [<ClientSignalList>]
The <ProcessingCapabilities> are important operations that the The <ProcessingCapabilities> are important operations that the
resource (or network element) can perform on the signal. The details resource (or network element) can perform on the signal. The details
of these capabilities are defined in section 5.3. of these capabilities are defined in Section 5.3.
<ProcessingCapabilities> ::= [<NumResources>] <ProcessingCapabilities> ::= [<NumResources>]
[<RegenerationCapabilities>] [<RegenerationCapabilities>]
[<FaultPerfMon>] [<FaultPerfMon>]
[<VendorSpecific>] [<VendorSpecific>]
The <OutputConstraints> are either restrictions on the properties of The <OutputConstraints> are either restrictions on the properties of
the signal leaving the block, options concerning the signal the signal leaving the block, options concerning the signal
properties when leaving the resource or shared fiber output properties when leaving the resource, or shared fiber output
constraint indication. constraint indication.
<OutputConstraints> := <SharedOutput> <OutputConstraints> := <SharedOutput>
[<OpticalInterfaceClassList>] [<OpticalInterfaceClassList>]
[<ClientSignalList>] [<ClientSignalList>]
5.3. Compatibility and Capability Details 5.3. Compatibility and Capability Details
5.3.1. Shared Input or Output Indication 5.3.1. Shared Input or Output Indication
As discussed in the previous section and shown in Figure 2 the input As discussed in Section 5.2 and shown in Figure 2, the input or
or output access to a resource block may be via a shared fiber. The output access to a resource block may be via a shared fiber. The
<SharedInput> and <SharedOutput> elements are indicators for this <SharedInput> and <SharedOutput> elements are indicators for this
condition with respect to the block being described. condition with respect to the block being described.
5.3.2. Optical Interface Class List 5.3.2. Optical Interface Class List
<OpticalInterfaceClassList> ::= <OpticalInterfaceClass> ... <OpticalInterfaceClassList> ::= <OpticalInterfaceClass> ...
The Optical Interface Class is a unique number that identifies The Optical Interface Class is a unique number that identifies all
all information related to optical characteristics of a physical information related to optical characteristics of a physical
interface. The class may include other optical parameters interface. The class may include other optical parameters related to
related to other interface properties. A class always includes other interface properties. A class always includes signal
signal compatibility information. compatibility information.
The content of each class is out of the scope of this document The content of each class is out of the scope of this document and
and can be defined by other entities (e.g. ITU, optical can be defined by other entities (e.g., the ITU, optical equipment
equipment vendors, etc.). vendors, etc.).
Since even current implementation of physical interfaces may Since even current implementation of physical interfaces may support
support different optical characteristics, a single interface may different optical characteristics, a single interface may support
support multiple interface classes. Which optical interface multiple interface classes. Which optical interface class is used
class is used among all the ones available for an interface is among all the ones available for an interface is out of the scope of
out of the scope of this document but is an output of the RWA this document but is an output of the RWA process.
process.
5.3.3. Acceptable Client Signal List 5.3.3. Acceptable Client Signal List
The list is simply: The list is simply:
<ClientSignalList>::=[<G-PID>]... <ClientSignalList>::=[<G-PID>]...
Where the Generalized Protocol Identifiers (G-PID) object Where the Generalized Protocol Identifiers (G-PID) object represents
represents one of the IETF standardized G-PID values as defined one of the IETF-standardized G-PID values as defined in [RFC3471] and
in [RFC3471] and [RFC4328]. [RFC4328].
5.3.4. Processing Capability List 5.3.4. Processing Capability List
The ProcessingCapabilities were defined in Section 5.2. The ProcessingCapabilities are defined in Section 5.2.
The processing capability list sub-TLV is a list of processing The processing capability list sub-TLV is a list of processing
functions that the WSON network element (NE) can perform on the functions that the WSON network element (NE) can perform on the
signal including: signal including:
1. Number of Resources within the block 1. number of resources within the block
2. Regeneration capability 2. regeneration capability
3. Fault and performance monitoring 3. fault and performance monitoring
4. Vendor Specific capability 4. vendor-specific capability
Note that the code points for Fault and performance monitoring and Note that the code points for fault and performance monitoring and
vendor specific capability are subject to further study. vendor-specific capability are subject to further study.
6. Link Information (General) 6. Link Information (General)
MPLS-TE routing protocol extensions for OSPF and IS-IS [RFC3630], MPLS-TE routing protocol extensions for OSPF [RFC3630] and IS-IS
[RFC5305] along with GMPLS routing protocol extensions for OSPF and [RFC5305], along with GMPLS routing protocol extensions for OSPF
IS-IS [RFC4203, RFC5307] provide the bulk of the relatively static [RFC4203] and IS-IS [RFC5307] provide the bulk of the relatively
link information needed by the RWA process. However, WSON networks static link information needed by the RWA process. However, WSONs
bring in additional link related constraints. These stem from WDM bring in additional link-related constraints. These stem from
line system characterization, laser transmitter tuning restrictions, characterizing WDM line systems, restricting laser transmitter
and switching subsystem port wavelength constraints, e.g., colored tuning, and switching subsystem port wavelength constraints, e.g.,
ROADM drop ports. "colored" ROADM drop ports.
In the following summarize both information from existing GMPLS The following syntax summarizes both information from existing GMPLS
route protocols and new information that maybe needed by the RWA routing protocols and new information that may be needed by the RWA
process. process.
<LinkInfo> ::= <LinkID> <LinkInfo> ::= <LinkID>
[<AdministrativeGroup>] [<AdministrativeGroup>]
[<InterfaceCapDesc>] [<InterfaceCapDesc>]
[<Protection>] [<Protection>]
[<SRLG>...] [<SRLG>...]
[<TrafficEngineeringMetric>] [<TrafficEngineeringMetric>]
[<PortLabelRestriction>...] [<PortLabelRestriction>...]
Note that these additional link characteristics only applies to line Note that these additional link characteristics only apply to line-
side ports of WDM system or add/drop ports pertaining to Resource side ports of a WDM system or add/drop ports pertaining to the
Pool (e.g., Regenerator or Wavelength Converter Pool). The resource pool (e.g., regenerator or wavelength converter pool). The
advertisement of input/output tributary ports is not intended here. advertisement of input/output tributary ports is not intended here.
6.1. Administrative Group 6.1. Administrative Group
Administrative Group: Defined in [RFC3630] and extended for MPLS-TE Administrative Group: Defined in [RFC3630] and extended for MPLS-TE
[RFC7308]. Each set bit corresponds to one administrative group [RFC7308]. Each set bit corresponds to one administrative group
assigned to the interface. A link may belong to multiple groups. assigned to the interface. A link may belong to multiple groups.
This is a configured quantity and can be used to influence routing This is a configured quantity and can be used to influence routing
decisions. decisions.
6.2. Interface Switching Capability Descriptor 6.2. Interface Switching Capability Descriptor
InterfaceSwCapDesc: Defined in [RFC4202], lets us know the different InterfaceSwCapDesc: Defined in [RFC4202]; lets us know the different
switching capabilities on this GMPLS interface. In both [RFC4203] switching capabilities on this GMPLS interface. In both [RFC4203]
and [RFC5307] this information gets combined with the maximum LSP and [RFC5307], this information gets combined with the maximum Link
bandwidth that can be used on this link at eight different priority State Protocol Data Unit (LSP) bandwidth that can be used on this
levels. link at eight different priority levels.
6.3. Link Protection Type (for this link) 6.3. Link Protection Type (for This Link)
Protection: Defined in [RFC4202] and implemented in [RFC4203, Protection: Defined in [RFC4202] and implemented in [RFC4203] and
RFC5307]. Used to indicate what protection, if any, is guarding this [RFC5307]. Used to indicate what protection, if any, is guarding
link. this link.
6.4. Shared Risk Link Group Information 6.4. Shared Risk Link Group Information
SRLG: Defined in [RFC4202] and implemented in [RFC4203, RFC5307]. SRLG: Defined in [RFC4202] and implemented in [RFC4203] and
This allows for the grouping of links into shared risk groups, i.e., [RFC5307]. This allows for the grouping of links into shared risk
those links that are likely, for some reason, to fail at the same groups, i.e., those links that are likely, for some reason, to fail
time. at the same time.
6.5. Traffic Engineering Metric 6.5. Traffic Engineering Metric
TrafficEngineeringMetric: Defined in [RFC3630] and [RFC5305]. This TrafficEngineeringMetric: Defined in [RFC3630] and [RFC5305]. This
allows for the identification of a data channel link metric value allows for the identification of a data-channel link metric value for
for traffic engineering that is separate from the metric used for traffic engineering that is separate from the metric used for path
path cost computation of the control plane. cost computation of the control plane.
Note that multiple "link metric values" could find use in optical Note that multiple "link metric values" could find use in optical
networks, however it would be more useful to the RWA process to networks; however, it would be more useful to the RWA process to
assign these specific meanings such as link mile metric, or assign these specific meanings such as "link mile" metric,
probability of failure metric, etc... "probability of failure" metric, etc.
6.6. Port Label Restrictions 6.6. Port Label Restrictions
Port label restrictions could be applied generally to any label Port label restrictions could be applied generally to any label types
types in GMPLS by adding new kinds of restrictions. Wavelength is a in GMPLS by adding new kinds of restrictions. Wavelength is a type
type of label. of label.
Port label (wavelength) restrictions (PortLabelRestriction) model Port label (wavelength) restrictions (PortLabelRestriction) model the
the label (wavelength) restrictions that the link and various label (wavelength) restrictions that the link and various optical
optical devices such as OXCs, ROADMs, and waveband multiplexers may devices, such as Optical Cross-Connects (OXCs), ROADMs, and waveband
impose on a port. These restrictions tell us what wavelength may or multiplexers, may impose on a port. These restrictions tell us what
may not be used on a link and are relatively static. This plays an wavelength may or may not be used on a link and are relatively
important role in fully characterizing a WSON switching device static. This plays an important role in fully characterizing a WSON
[Switch]. Port wavelength restrictions are specified relative to the switching device [Switch]. Port wavelength restrictions are
port in general or to a specific connectivity matrix (section 4.1. specified relative to the port in general or to a specific
Reference [Switch] gives an example where both switch and fixed connectivity matrix (Section 4.1). [Switch] gives an example where
connectivity matrices are used and both types of constraints occur both switch and fixed connectivity matrices are used and both types
on the same port. of constraints occur on the same port.
<PortLabelRestriction> ::= <MatrixID> <PortLabelRestriction> ::= <MatrixID>
<RestrictionType> <RestrictionType>
<Restriction parameters list> <Restriction parameters list>
<Restriction parameters list> ::= <Restriction parameters list> ::=
<Simple label restriction parameters> | <Simple label restriction parameters> |
skipping to change at page 17, line 9 skipping to change at page 16, line 21
(<LabelSet> ...) (<LabelSet> ...)
<Simple+channel restriction parameters> ::= <MaxNumChannels> <Simple+channel restriction parameters> ::= <MaxNumChannels>
(<LabelSet> ...) (<LabelSet> ...)
<Exclusive label restriction parameters> ::= <LabelSet> ... <Exclusive label restriction parameters> ::= <LabelSet> ...
Where Where
MatrixID is the ID of the corresponding connectivity matrix (section MatrixID is the ID of the corresponding connectivity matrix (Section
4.1. 4.1).
The RestrictionType parameter is used to specify general port The RestrictionType parameter is used to specify general port
restrictions and matrix specific restrictions. It can take the restrictions and matrix-specific restrictions. It can take the
following values and meanings: following values and meanings:
SIMPLE_LABEL: Simple label (wavelength) set restriction; The label SIMPLE_LABEL: Simple label (wavelength) set restriction; the
set parameter is required. LabelSet parameter is required.
CHANNEL_COUNT: The number of channels is restricted to be less than CHANNEL_COUNT: The number of channels is restricted to be less
or equal to the Max number of channels parameter (which is than or equal to the MaxNumChannels parameter (which is
required). required).
LABEL_RANGE: Used to indicate a restriction on a range of labels LABEL_RANGE: Used to indicate a restriction on a range of labels
that can be switched. For example, a waveband device with a tunable that can be switched. For example, a waveband device with a
center frequency and passband. This constraint is characterized by tunable center frequency and passband. This constraint is
the MaxLabelRange parameter which indicates the maximum range of the characterized by the MaxLabelRange parameter, which indicates
labels, e.g., which may represent a waveband in terms of channels. the maximum range of the labels, e.g., which may represent a
Note that an additional parameter can be used to indicate the waveband in terms of channels. Note that an additional
overall tuning range. Specific center frequency tuning information parameter can be used to indicate the overall tuning range.
can be obtained from dynamic channel in use information. It is Specific center frequency tuning information can be obtained
assumed that both center frequency and bandwidth (Q) tuning can be from information about the dynamic channel in use. It is
done without causing faults in existing signals. assumed that both center frequency and bandwidth (Q) tuning can
be done without causing faults in existing signals.
SIMPLE LABEL & CHANNEL COUNT: In this case, the accompanying label SIMPLE LABEL and CHANNEL COUNT: In this case, the accompanying
set and MaxNumChannels indicate labels permitted on the port and the label set and MaxNumChannels indicate labels permitted on the
maximum number of labels that can be simultaneously used on the port and the maximum number of labels that can be
port. simultaneously used on the port.
LINK LABEL_EXCLUSIVITY: A label (wavelength) can be used at most LINK LABEL_EXCLUSIVITY: A label (wavelength) can be used at most
once among a given set of ports. The set of ports is specified as a once among a given set of ports. The set of ports is specified
parameter to this constraint. as a parameter to this constraint.
Restriction specific parameters are used with one or more of the Restriction-specific parameters are used with one or more of the
previously listed restriction types. The currently defined previously listed restriction types. The currently defined
parameters are: parameters are:
LabelSet is a conceptual set of labels (wavelengths). LabelSet is a conceptual set of labels (wavelengths).
MaxNumChannels is the maximum number of channels that can be MaxNumChannels is the maximum number of channels that can be
simultaneously used (relative to either a port or a matrix). simultaneously used (relative to either a port or a matrix).
LinkSet is a conceptual set of ports. LinkSet is a conceptual set of ports.
MaxLabelRange indicates the maximum range of the labels. For MaxLabelRange indicates the maximum range of the labels. For
example, if the port is a "colored" drop port of a ROADM then there example, if the port is a "colored" drop port of a ROADM, then there
are two restrictions: (a) CHANNEL_COUNT, with MaxNumChannels = 1, are two restrictions: (a) CHANNEL_COUNT, with MaxNumChannels = 1, and
and (b) SIMPLE_WAVELENGTH, with the wavelength set consisting of a (b) SIMPLE_WAVELENGTH, with the wavelength set consisting of a single
single member corresponding to the frequency of the permitted member corresponding to the frequency of the permitted wavelength.
wavelength. See [Switch] for a complete waveband example. See [Switch] for a complete waveband example.
This information model for port wavelength (label) restrictions is This information model for port wavelength (label) restrictions is
fairly general in that it can be applied to ports that have label fairly general in that it can be applied to ports that have label
restrictions only or to ports that are part of an asymmetric switch restrictions only or to ports that are part of an asymmetric switch
and have label restrictions. In addition, the types of label and have label restrictions. In addition, the types of label
restrictions that can be supported are extensible. restrictions that can be supported are extensible.
6.6.1. Port-Wavelength Exclusivity Example 6.6.1. Port-Wavelength Exclusivity Example
Although there can be many different ROADM or switch architectures Although there can be many different ROADM or switch architectures
that can lead to the constraint where a lambda (label) maybe used at that can lead to the constraint where a lambda (label) maybe used at
most once on a set of ports Figure 3 shows a ROADM architecture most once on a set of ports, Figure 3 shows a ROADM architecture
based on components known as a Wavelength Selective Switch based on components known as Wavelength Selective Switches (WSSes)
(WSS)[OFC08]. This ROADM is composed of splitters, combiners, and [OFC08]. This ROADM is composed of splitters, combiners, and WSSes.
WSSes. This ROADM has 11 output ports, which are numbered in the This ROADM has 11 output ports, which are numbered in the diagram.
diagram. Output ports 1-8 are known as drop ports and are intended Output ports 1-8 are known as drop ports and are intended to support
to support a single wavelength. Drop ports 1-4 output from WSS #2, a single wavelength. Drop ports 1-4 output from WSS 2, which is fed
which is fed from WSS #1 via a single fiber. Due to this internal from WSS 1 via a single fiber. Due to this internal structure, a
structure a constraint is placed on the output ports 1-4 that a constraint is placed on the output ports 1-4 that a lambda can be
lambda can be only used once over the group of ports (assuming uni- used only once over the group of ports (assuming unicast and not
cast and not multi-cast operation). Similarly the output ports 5-8 multicast operation). The output ports 5-8 have a similar constraint
have a similar constraint due to the internal structure. due to the internal structure.
| A | A
v 10 | v 10 |
+-------+ +-------+ +-------+ +-------+
| Split | |WSS 6 | | Split | |WSS 6 |
+-------+ +-------+ +-------+ +-------+
+----+ | | | | | | | | +----+ | | | | | | | |
| W | | | | | | | | +-------+ +----+ | W | | | | | | | | +-------+ +----+
| S |--------------+ | | | +-----+ | +----+ | | S | | S |--------------+ | | | +-----+ | +----+ | | S |
9 | S |----------------|---|----|-------|------|----|---| p | 9 | S |----------------|---|----|-------|------|----|---| p |
<--| |----------------|---|----|-------|----+ | +---| l |< --| |----------------|---|----|-------|----+ | +---| l |<
| 5 |--------------+ | | | +-----+ | | +--| i | | 5 |--------------+ | | | +-----+ | | +--| i |
+----+ | | | | | +------|-|-----|--| t | +----+ | | | | | +------|-|-----|--| t |
+--------|-+ +----|-|---|------|----+ | +----+ +--------|-+ +----|-|---|------|----+ | +----+
+----+ | | | | | | | | | +----+ | | | | | | | | |
| S |-----|--------|----------+ | | | | | | +----+ | S |-----|--------|----------+ | | | | | | +----+
| p |-----|--------|------------|---|------|----|--|--| W | | p |-----|--------|------------|---|------|----|--|--| W |
-->| l |-----|-----+ | +----------+ | | | +--|--| S |11 ->| l |-----|-----+ | +----------+ | | | +--|--| S |11
| i |---+ | | | | +------------|------|-------|--| S |-> | i |---+ | | | | +------------|------|-------|--| S |->
| t | | | | | | | | | | +---|--| | | t | | | | | | | | | | +---|--| |
+----+ | | +---|--|-|-|------------|------|-|-|---+ | 7 | +----+ | | +---|--|-|-|------------|------|-|-|---+ | 7 |
| | | +--|-|-|--------+ | | | | | +----+ | | | +--|-|-|--------+ | | | | | +----+
| | | | | | | | | | | | | | | | | | | | | | | |
+------+ +------+ +------+ +------+ +------+ +------+ +------+ +------+
| WSS 1| | Split| | WSS 3| | Split| | WSS 1| | Split| | WSS 3| | Split|
+--+---+ +--+---+ +--+---+ +--+---+ +--+---+ +--+---+ +--+---+ +--+---+
| A | A | A | A
v | v | v | v |
+-------+ +--+----+ +-------+ +--+----+ +-------+ +--+----+ +-------+ +--+----+
| WSS 2 | | Comb. | | WSS 4 | | Comb. | | WSS 2 | | Comb. | | WSS 4 | | Comb. |
+-------+ +-------+ +-------+ +-------+ +-------+ +-------+ +-------+ +-------+
1|2|3|4| A A A A 5|6|7|8| A A A A 1|2|3|4| A A A A 5|6|7|8| A A A A
v v v v | | | | v v v v | | | | v v v v | | | | v v v v | | | |
Figure 3 A ROADM composed from splitter, combiners, and WSSs. Figure 3: A ROADM Composed from Splitter, Combiners, and WSSes
7. Dynamic Components of the Information Model 7. Dynamic Components of the Information Model
In the previously presented information model there are a limited In the previously presented information model, there are a limited
number of information elements that are dynamic, i.e., subject to number of information elements that are dynamic, i.e., subject to
change with subsequent establishment and teardown of connections. change with subsequent establishment and teardown of connections.
Depending on the protocol used to convey this overall information Depending on the protocol used to convey this overall information
model it may be possible to send this dynamic information separate model, it may be possible to send this dynamic information separately
from the relatively larger amount of static information needed to from the relatively larger amount of static information needed to
characterize WSON's and their network elements. characterize WSONs and their network elements.
7.1. Dynamic Link Information (General) 7.1. Dynamic Link Information (General)
For WSON links wavelength availability and wavelengths in use for For WSON links, the wavelength availability and which wavelengths are
shared backup purposes can be considered dynamic information and in use for shared backup purposes can be considered dynamic
hence are grouped with the dynamic information in the following set: information and hence are grouped with the dynamic information in the
following set:
<DynamicLinkInfo> ::= <LinkID> <DynamicLinkInfo> ::= <LinkID>
<AvailableLabels> <AvailableLabels>
[<SharedBackupLabels>] [<SharedBackupLabels>]
AvailableLabels is a set of labels (wavelengths) currently available AvailableLabels is a set of labels (wavelengths) currently available
on the link. Given this information and the port wavelength on the link. Given this information and the port wavelength
restrictions one can also determine which wavelengths are currently restrictions, one can also determine which wavelengths are currently
in use. This parameter could potential be used with other in use. This parameter could potentially be used with other
technologies that GMPLS currently covers or may cover in the future. technologies that GMPLS currently covers or may cover in the future.
SharedBackupLabels is a set of labels (wavelengths) currently used SharedBackupLabels is a set of labels (wavelengths) currently used
for shared backup protection on the link. An example usage of this for shared backup protection on the link. An example usage of this
information in a WSON setting is given in [Shared]. This parameter information in a WSON setting is given in [Shared]. This parameter
could potential be used with other technologies that GMPLS currently could potentially be used with other technologies that GMPLS
covers or may cover in the future. currently covers or may cover in the future.
Note that the above does not dictate a particular encoding or Note that the above does not dictate a particular encoding or
placement for available label information. In some routing protocols placement for available label information. In some routing
it may be advantageous or required to place this information within protocols, it may be advantageous or required to place this
another information element such as the interface switching information within another information element such as the Interface
capability descriptor (ISCD). Consult routing protocol specific Switching Capability Descriptor (ISCD). Consult the extensions that
extensions for details of placement of information elements. are specific to each routing protocol for details of placement of
information elements.
7.2. Dynamic Node Information (WSON Specific) 7.2. Dynamic Node Information (WSON Specific)
Currently the only node information that can be considered dynamic Currently the only node information that can be considered dynamic is
is the resource pool state and can be isolated into a dynamic node the resource pool state, and it can be isolated into a dynamic node
information element as follows: information element as follows:
<DynamicNodeInfo> ::= <NodeID> [<ResourcePool>] <DynamicNodeInfo> ::= <NodeID> [<ResourcePool>]
8. Security Considerations 8. Security Considerations
This document discussed an information model for RWA computation in This document discusses an information model for RWA computation in
WSONs. Such a model is very similar from a security standpoint of WSONs. From a security standpoint, such a model is very similar to
the information that can be currently conveyed via GMPLS routing the information that can be currently conveyed via GMPLS routing
protocols. Such information includes network topology, link state protocols. Such information includes network topology, link state
and current utilization, and well as the capabilities of switches and current utilization, as well as the capabilities of switches and
and routers within the network. As such this information should be routers within the network. As such, this information should be
protected from disclosure to unintended recipients. In addition, protected from disclosure to unintended recipients. In addition, the
the intentional modification of this information can significantly intentional modification of this information can significantly affect
affect network operations, particularly due to the large capacity of network operations, particularly due to the large capacity of the
the optical infrastructure to be controlled. A general discussion on optical infrastructure to be controlled. A general discussion on
security in GMPLS networks can be found in [RFC5920]. security in GMPLS networks can be found in [RFC5920].
9. IANA Considerations 9. References
This informational document does not make any requests for IANA
action.
10. Acknowledgments
This document was prepared using 2-Word-v2.0.template.dot.
11. References
11.1. Normative References 9.1. Normative References
[G.7715] ITU-T Recommendation G.7715, Architecture and requirements [G.7715] ITU-T, "Architecture and requirements for routing in the
for routing in the automatically switched optical automatically switched optical networks", ITU-T
networks, June 2002. Recommendation G.7715, June 2002.
[RBNF] A. Farrel, "Reduced Backus-Naur Form (RBNF) A Syntax Used [RBNF] Farrel, A., "Routing Backus-Naur Form (RBNF): A Syntax Used
in Various Protocol Specifications", RFC 5511, April 2009. to Form Encoding Rules in Various Routing Protocol
Specifications", RFC 5511, April 2009,
<http://www.rfc-editor.org/info/rfc5511>.
[RFC3471] Berger, L., Ed., "Generalized Multi-Protocol Label [RFC3471] Berger, L., Ed., "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Functional Description", RFC Switching (GMPLS) Signaling Functional Description", RFC
3471, January 2003. 3471, January 2003,
<http://www.rfc-editor.org/info/rfc3471>.
[RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering
(TE) Extensions to OSPF Version 2", RFC 3630, September
2003.
[RFC5305] T. Li, and H. SMIT, "Intermediate System to Intermediate
System (IS-IS) Extensions for Traffic Engineering (TE)",
RFC 5305, October 2008.
[RFC4202] Kompella, K., Ed., and Y. Rekhter, Ed., "Routing [RFC3630] van der Meer, J., Mackie, D., Swaminathan, V., Singer, D.,
Extensions in Support of Generalized Multi-Protocol Label and P. Gentric, "RTP Payload Format for Transport of MPEG-4
Switching (GMPLS)", RFC 4202, October 2005 Elementary Streams", RFC 3640, November 2003,
<http://www.rfc-editor.org/info/rfc3640>.
[RFC4203] Kompella, K., Ed., and Y. Rekhter, Ed., "OSPF Extensions [RFC4202] Kompella, K., Ed., and Y. Rekhter, Ed., "Routing Extensions
in Support of Generalized Multi-Protocol Label Switching in Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 4203, October 2005. (GMPLS)", RFC 4202, October 2005,
<http://www.rfc-editor.org/info/rfc4202>.
[RFC4203] Kompella, K., Ed., and Y. Rekhter, Ed., "OSPF Extensions in
Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 4203, October 2005,
<http://www.rfc-editor.org/info/rfc4203>.
[RFC4328] Papadimitriou, D., Ed., "Generalized Multi-Protocol Label [RFC4328] Papadimitriou, D., Ed., "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Extensions for G.709 Optical Switching (GMPLS) Signaling Extensions for G.709 Optical
Transport Networks Control", RFC 4328, January 2006. Transport Networks Control", RFC 4328, January 2006,
<http://www.rfc-editor.org/info/rfc4328>.
[RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic
Engineering", RFC 5305, October 2008,
<http://www.rfc-editor.org/info/rfc5305>.
[RFC5307] Kompella, K., Ed., and Y. Rekhter, Ed., "IS-IS Extensions [RFC5307] Kompella, K., Ed., and Y. Rekhter, Ed., "IS-IS Extensions
in Support of Generalized Multi-Protocol Label Switching in Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 5307, October 2008. (GMPLS)", RFC 5307, October 2008,
<http://www.rfc-editor.org/info/rfc5307>.
[RFC6163] Y. Lee, G. Bernstein, W. Imajuku, "Framework for GMPLS and [RFC6163] Lee, Y., Ed., Bernstein, G., Ed., and W. Imajuku,
PCE Control of Wavelength Switched Optical Networks", RFC "Framework for GMPLS and Path Computation Element (PCE)
6163, April 2011. Control of Wavelength Switched Optical Networks (WSONs)",
RFC 6163, April 2011,
<http://www.rfc-editor.org/info/rfc6163>.
[RFC7308] E. Osborne, "Extended Administrative Groups in MPLS [RFC7308] Osborne, E., "Extended Administrative Groups in MPLS
Traffic Engineering (MPLS-TE)", RFC 7308, July 2014. Traffic Engineering (MPLS-TE)", RFC 7308, July 2014,
<http://www.rfc-editor.org/info/rfc7308>.
11.2. Informative References 9.2. Informative References
[OFC08] P. Roorda and B. Collings, "Evolution to Colorless and [OFC08] Roorda, P., and B. Collings, "Evolution to Colorless and
Directionless ROADM Architectures," Optical Fiber Directionless ROADM Architectures", Optical Fiber
communication/National Fiber Optic Engineers Conference, Communication / National Fiber Optic Engineers Conference
2008. OFC/NFOEC 2008. Conference on, 2008, pp. 1-3. (OFC/NFOEC), 2008, pp. 1-3.
[Shared] G. Bernstein, Y. Lee, "Shared Backup Mesh Protection in [RFC5920] Fang, L., Ed., "Security Framework for MPLS and GMPLS
PCE-based WSON Networks", iPOP 2008. Networks", RFC 5920, July 2010,
<http://www.rfc-editor.org/info/rfc5920>.
[Switch] G. Bernstein, Y. Lee, A. Gavler, J. Martensson, "Modeling [Shared] Bernstein, G., and Y. Lee, "Shared Backup Mesh Protection
WDM Wavelength Switching Systems for Use in GMPLS and in PCE-based WSON Networks", iPOP 2008.
Automated Path Computation", Journal of Optical
Communications and Networking, vol. 1, June, 2009, pp.
187-195.
[RFC5920] L. Fang, Ed., "Security Framework for MPLS and GMPLS [Switch] Bernstein, G., Lee, Y., Gavler, A., and J. Martensson,
Networks", RFC 5920, July 2010. "Modeling WDM Wavelength Switching Systems for Use in GMPLS
and Automated Path Computation", Journal of Optical
Communications and Networking, vol. 1, June 2009, pp.
187-195.
12. Contributors Contributors
Diego Caviglia Diego Caviglia
Ericsson Ericsson
Via A. Negrone 1/A 16153 Via A. Negrone 1/A 16153
Genoa Italy Genoa, Italy
Phone: +39 010 600 3736 Phone: +39 010 600 3736
Email: diego.caviglia@(marconi.com, ericsson.com) EMail: diego.caviglia@(marconi.com, ericsson.com)
Anders Gavler Anders Gavler
Acreo AB Acreo AB
Electrum 236 Electrum 236
SE - 164 40 Kista Sweden SE - 164 40 Kista
Sweden
Email: Anders.Gavler@acreo.se EMail: Anders.Gavler@acreo.se
Jonas Martensson Jonas Martensson
Acreo AB Acreo AB
Electrum 236 Electrum 236
SE - 164 40 Kista, Sweden SE - 164 40 Kista
Sweden
Email: Jonas.Martensson@acreo.se EMail: Jonas.Martensson@acreo.se
Itaru Nishioka Itaru Nishioka
NEC Corp. NEC Corp.
1753 Simonumabe, Nakahara-ku, Kawasaki, Kanagawa 211-8666 1753 Simonumabe, Nakahara-ku, Kawasaki, Kanagawa 211-8666
Japan Japan
Phone: +81 44 396 3287 Phone: +81 44 396 3287
Email: i-nishioka@cb.jp.nec.com EMail: i-nishioka@cb.jp.nec.com
Lyndon Ong Lyndon Ong
Ciena Ciena
Email: lyong@ciena.com EMail: lyong@ciena.com
Cyril Margaria Cyril Margaria
Email: cyril.margaria@gmail.com EMail: cyril.margaria@gmail.com
Authors' Addresses Authors' Addresses
Greg M. Bernstein (ed.) Young Lee (editor)
Grotto Networking
Fremont California, USA
Phone: (510) 573-2237
Email: gregb@grotto-networking.com
Young Lee (ed.)
Huawei Technologies Huawei Technologies
5369 Legacy Drive, Building 3 5369 Legacy Drive, Building 3
Plano, TX 75023 Plano, TX 75023
USA United States
Phone: (469) 277-5838 Phone: (469) 277-5838
Email: leeyoung@huawei.com EMail: leeyoung@huawei.com
Greg M. Bernstein (editor)
Grotto Networking
Fremont, CA
United States
Phone: (510) 573-2237
EMail: gregb@grotto-networking.com
Dan Li Dan Li
Huawei Technologies Co., Ltd. Huawei Technologies Co., Ltd.
F3-5-B R&D Center, Huawei Base, F3-5-B R&D Center, Huawei Base,
Bantian, Longgang District Bantian, Longgang District
Shenzhen 518129 P.R.China Shenzhen 518129
China
Phone: +86-755-28973237 Phone: +86-755-28973237
Email: danli@huawei.com EMail: danli@huawei.com
Wataru Imajuku Wataru Imajuku
NTT Network Innovation Labs NTT Network Innovation Labs
1-1 Hikari-no-oka, Yokosuka, Kanagawa 1-1 Hikari-no-oka, Yokosuka, Kanagawa
Japan Japan
Phone: +81-(46) 859-4315 Phone: +81-(46) 859-4315
Email: imajuku.wataru@lab.ntt.co.jp EMail: imajuku.wataru@lab.ntt.co.jp
Intellectual Property Statement
The IETF Trust takes no position regarding the validity or scope of
any Intellectual Property Rights or other rights that might be
claimed to pertain to the implementation or use of the technology
described in any IETF Document or the extent to which any license
under such rights might or might not be available; nor does it
represent that it has made any independent effort to identify any
such rights.
Copies of Intellectual Property disclosures made to the IETF
Secretariat and any assurances of licenses to be made available, or
the result of an attempt made to obtain a general license or
permission for the use of such proprietary rights by implementers or
users of this specification can be obtained from the IETF on-line
IPR repository at http://www.ietf.org/ipr
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
any standard or specification contained in an IETF Document. Please
address the information to the IETF at ietf-ipr@ietf.org.
Disclaimer of Validity
All IETF Documents and the information contained therein are
provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION
HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY,
THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE
ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 180 change blocks. 
501 lines changed or deleted 516 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/