draft-ietf-ccamp-rwa-info-07.txt   draft-ietf-ccamp-rwa-info-08.txt 
Network Working Group Y. Lee Network Working Group Y. Lee
Internet Draft Huawei Internet Draft Huawei
Intended status: Informational G. Bernstein Intended status: Informational G. Bernstein
Expires: August 2010 Grotto Networking Expires: January 2011 Grotto Networking
D. Li D. Li
Huawei Huawei
W. Imajuku W. Imajuku
NTT NTT
February 18, 2010 July 12, 2010
Routing and Wavelength Assignment Information Model for Wavelength Routing and Wavelength Assignment Information Model for Wavelength
Switched Optical Networks Switched Optical Networks
draft-ietf-ccamp-rwa-info-07.txt draft-ietf-ccamp-rwa-info-08.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 39 skipping to change at page 1, line 39
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on August 18, 2010. This Internet-Draft will expire on January 12, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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
skipping to change at page 2, line 37 skipping to change at page 2, line 37
Table of Contents Table of Contents
1. Introduction...................................................3 1. Introduction...................................................3
1.1. Revision History..........................................4 1.1. Revision History..........................................4
1.1.1. Changes from 01......................................4 1.1.1. Changes from 01......................................4
1.1.2. Changes from 02......................................4 1.1.2. Changes from 02......................................4
1.1.3. Changes from 03......................................4 1.1.3. Changes from 03......................................4
1.1.4. Changes from 04......................................4 1.1.4. Changes from 04......................................4
1.1.5. Changes from 05......................................5 1.1.5. Changes from 05......................................5
1.1.6. Changes from 06......................................5 1.1.6. Changes from 06......................................5
1.1.7. Changes from 07......................................5
2. Terminology....................................................5 2. Terminology....................................................5
3. Routing and Wavelength Assignment Information Model............6 3. Routing and Wavelength Assignment Information Model............6
3.1. Dynamic and Relatively Static Information.................6 3.1. Dynamic and Relatively Static Information.................6
4. Node Information (General).....................................6 4. Node Information (General).....................................7
4.1. Connectivity Matrix.......................................7 4.1. Connectivity Matrix.......................................7
4.2. Shared Risk Node Group....................................8 4.2. Shared Risk Node Group....................................8
5. Node Information (WSON specific)...............................8 5. Node Information (WSON specific)...............................8
5.1. Resource Accessibility/Availability.......................9 5.1. Resource Accessibility/Availability.......................9
5.2. Resource Signal Constraints and Processing Capabilities..11 5.2. Resource Signal Constraints and Processing Capabilities..13
5.3. Compatibility and Capability Details.....................12 5.3. Compatibility and Capability Details.....................14
5.3.1. Modulation Type List................................12 5.3.1. Shared Ingress or Egress Indication.................14
5.3.2. FEC Type List.......................................12 5.3.2. Modulation Type List................................14
5.3.3. Bit Rate Range List.................................12 5.3.3. FEC Type List.......................................14
5.3.4. Acceptable Client Signal List.......................12 5.3.4. Bit Rate Range List.................................14
5.3.5. Processing Capability List..........................13 5.3.5. Acceptable Client Signal List.......................15
6. Link Information (General)....................................13 5.3.6. Processing Capability List..........................15
6.1. Administrative Group.....................................13 6. Link Information (General)....................................15
6.2. Interface Switching Capability Descriptor................14 6.1. Administrative Group.....................................16
6.3. Link Protection Type (for this link).....................14 6.2. Interface Switching Capability Descriptor................16
6.4. Shared Risk Link Group Information.......................14 6.3. Link Protection Type (for this link).....................16
6.5. Traffic Engineering Metric...............................14 6.4. Shared Risk Link Group Information.......................16
6.6. Port Label (Wavelength) Restrictions.....................14 6.5. Traffic Engineering Metric...............................16
7. Dynamic Components of the Information Model...................16 6.6. Port Label (Wavelength) Restrictions.....................16
7.1. Dynamic Link Information (General).......................16 7. Dynamic Components of the Information Model...................18
7.2. Dynamic Node Information (WSON Specific).................16 7.1. Dynamic Link Information (General).......................18
8. Security Considerations.......................................17 7.2. Dynamic Node Information (WSON Specific).................19
9. IANA Considerations...........................................17 8. Security Considerations.......................................19
10. Acknowledgments..............................................17 9. IANA Considerations...........................................19
11. References...................................................18 10. Acknowledgments..............................................19
11.1. Normative References....................................18 11. References...................................................20
11.2. Informative References..................................19 11.1. Normative References....................................20
12. Contributors.................................................20 11.2. Informative References..................................21
Author's Addresses...............................................20 12. Contributors.................................................22
Intellectual Property Statement..................................21 Author's Addresses...............................................22
Disclaimer of Validity...........................................22 Intellectual Property Statement..................................23
Disclaimer of Validity...........................................24
1. Introduction 1. Introduction
The purpose of the following information model for WSONs is to The purpose of the following information model for WSONs is to
facilitate constrained lightpath computation and as such is not a facilitate constrained lightpath computation and as such is not a
general purpose network management information model. This constraint general purpose network management information model. This constraint
is frequently referred to as the "wavelength continuity" constraint, is frequently referred to as the "wavelength continuity" constraint,
and the corresponding constrained lightpath computation is known as and the corresponding constrained lightpath computation is known as
the routing and wavelength assignment (RWA) problem. Hence the the routing and wavelength assignment (RWA) problem. Hence the
information model must provide sufficient topology and wavelength information model must provide sufficient topology and wavelength
skipping to change at page 5, line 23 skipping to change at page 5, line 23
Generalized Section on wavelength converter pools to include electro Generalized Section on wavelength converter pools to include electro
optical subsystems in general. This is where we added signal optical subsystems in general. This is where we added signal
compatibility modeling. compatibility modeling.
1.1.6. Changes from 06 1.1.6. Changes from 06
Simplified information model for WSON specifics, by combining similar Simplified information model for WSON specifics, by combining similar
fields and introducing simpler aggregate information elements. fields and introducing simpler aggregate information elements.
1.1.7. Changes from 07
Added shared fiber connectivity to resource pool modeling. This
includes information for determining wavelength collision on an
internal fiber providing access to resource blocks.
2. Terminology 2. Terminology
CWDM: Coarse Wavelength Division Multiplexing. CWDM: Coarse Wavelength Division Multiplexing.
DWDM: Dense Wavelength Division Multiplexing. DWDM: Dense Wavelength Division Multiplexing.
FOADM: Fixed Optical Add/Drop Multiplexer. FOADM: Fixed Optical Add/Drop Multiplexer.
ROADM: Reconfigurable Optical Add/Drop Multiplexer. A reduced port ROADM: Reconfigurable Optical Add/Drop Multiplexer. A reduced port
count wavelength selective switching element featuring ingress and count wavelength selective switching element featuring ingress and
skipping to change at page 8, line 33 skipping to change at page 8, line 39
5. Node Information (WSON specific) 5. Node Information (WSON specific)
As discussed in [WSON-Frame] a WSON node may contain electro-optical As discussed in [WSON-Frame] 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. We refer to regenerator block or wavelength converter technologies.
block as resource block.
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 [WSON-Frame] this can arranged in a shared pool. As discussed in [WSON-Frame] this can
include OEO based WDM switches as well. There are a number of include OEO based WDM switches as well. There are a number of
different approaches used in the design of WDM switches containing different approaches used in the design of WDM switches containing
regenerator or converter pools. However, from the point of view of regenerator or converter pools. However, from the point of view of
path computation we need to know the following: path computation we need to know the following:
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 ingress wavelength on a particular ingress convert from a given ingress wavelength on a particular ingress
port to a desired egress wavelength on a particular egress port. port to a desired egress wavelength on a particular egress 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.
For modeling purposes and encoding efficiency we group identical
processing resources such as regenerators or wavelength converters
into "blocks". The accessibility to and from any resource within a
block must be the same. The resource pool is composed of one or more
blocks.
This leads to the following formal high level model: This leads to the following formal high level model:
<Node_Information> ::= <Node_ID> [<ConnectivityMatrix>...] <Node_Information> ::= <Node_ID> [<ConnectivityMatrix>...]
[<ResourcePool>] [<ResourcePool>]
Where Where
<ResourcePool> ::= <ResourceBlockInfo>... <ResourcePool> ::= <ResourceBlockInfo>...
[<ResourceBlockAccessibility>...] [<ResourceWaveConstraints>...] [<ResourceBlockAccessibility>...] [<ResourceWaveConstraints>...]
[<RBPoolState>] [<RBPoolState>]
skipping to change at page 9, line 30 skipping to change at page 9, line 45
be used to model regenerator/converter accessibility. This technique be used to model regenerator/converter accessibility. This technique
was generally discussed in [WSON-Frame] and consisted of a matrix to was generally discussed in [WSON-Frame] 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 we will also want to our model to considered a scarce resource we will also want to our model to
include as a minimum the usage state (availability) of individual include as a minimum the usage state (availability) of individual
regenerators or converters in the pool. Models that incorporate more regenerators or converters in the pool. Models that incorporate more
state to further reveal blocking conditions on ingress or egress to state to further reveal blocking conditions on ingress or egress to
particular converters are for further study and not included here. particular converters are for further study and not included here.
The three stage model as shown schematically in Figure 1. In this The three stage model as shown schematically in Figure 1 and Figure
model we assume N ingress ports (fibers), P resource blocks 2. In this model we assume N ingress ports (fibers), P resource
containing one or more identical resources (e.g. wavelength blocks containing one or more identical resources (e.g. wavelength
converters), and M egress ports (fibers). Since not all ingress ports converters), and M egress ports (fibers). Since not all ingress 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 ingress matrix RI(i,p) = {0,1} whether ingress port i resource pool ingress matrix RI(i,p) = {0,1} whether ingress port i
can reach potentially reach resource block p. can reach 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 we have a set the resources may have limited input wavelength range we have a set
of ingress port constraints for each resource. Currently we assume of relatively static ingress port constraints for each resource. In
that a resource with a resource block can only take a single addition, if the access to a resource block is via a shared fiber
wavelength on input. We can model each resource block ingress port this would impose a dynamic wavelength availability constraints on
constraint via a wavelength set mechanism. that shared fiber. We can model each resource block ingress port
constraint via a static wavelength set mechanism and in the case of
shared access to a block via another dynamic wavelength set
mechanism.
Next we have a state vector RA(j) = {0,...,k} which tells us the Next we have a state vector RA(j) = {0,...,k} which tells us the
number of resources in resource block j in use. This is the only number of resources in resource block j in use. This is the only
state kept in the resource pool model. This state is not necessary state kept in the resource pool model. This state is not necessary
for modeling "fixed" transponder system or full OEO switches with WDM for modeling "fixed" transponder system or full OEO switches with WDM
interfaces, i.e., systems where there is no sharing. interfaces, i.e., systems where there is no sharing.
After that, we have a set of resource egress wavelength constraints. After that, we have a set of static resource egress wavelength
These constraints indicate what wavelengths a particular resource constraints and possibly dynamic shared egress fiber constraints. The
static constraints indicate what wavelengths a particular resource
block can generate or are restricted to generating e.g., a fixed block can generate or are restricted to generating e.g., a fixed
regenerator would be limited to a single lambda. regenerator would be limited to a single lambda. The dynamic
constraints would be used in the case where a single shared fiber is
used to egress the resource block.
Finally, we have a resource pool egress matrix RE(p,k) = {0,1} Finally, we have a resource pool egress matrix RE(p,k) = {0,1}
depending on whether the output from resource block p can reach depending on whether the output from resource block p can reach
egress port k. Examples of this method being used to model wavelength egress port k. Examples of this method being used to model wavelength
converter pools for several switch architectures from the literature converter pools for several switch architectures from the literature
are given in reference [WC-Pool]. are given in reference [WC-Pool].
I1 +-------------+ +-------------+ E1 I1 +-------------+ +-------------+ E1
----->| | +--------+ | |-----> ----->| | +--------+ | |----->
I2 | +------+ Rb #1 +-------+ | E2 I2 | +------+ Rb #1 +-------+ | E2
skipping to change at page 10, line 41 skipping to change at page 12, line 5
| | | |
| | | |
| | | |
Ingress wavelength Egress wavelength Ingress wavelength Egress wavelength
constraints for constraints for constraints for constraints for
each resource each resource each resource each resource
Figure 1 Schematic diagram of resource pool model. Figure 1 Schematic diagram of resource pool model.
I1 +-------------+ +-------------+ E1
----->| | +--------+ | |----->
I2 | +======+ Rb #1 +=======+ | E2
----->| | +--------+ | |----->
| | | |
| Resource | +--------+ | Resource |
| Pool | | Pool | | |
| |======+ Rb #2 +=======+ |
| Ingress | + | | Egress |
| Connection | +--------+ | Connection |
| Matrix | . | Matrix |
| | . | |
| | . | |
IN | | +--------+ | | EM
----->| +======+ Rb #P +=======+ |----->
| | +--------+ | |
+-------------+ ^ ^ +-------------+
| |
| |
| |
Single (shared) fibers for block ingress and egress
Ingress wavelength Egress wavelength
availability for availability for
each block ingress fiber each block egress fiber
Figure 2 Schematic diagram of resource pool model with shared block
accessibility.
Formally we can specify the model as: Formally we can specify the model as:
<ResourceBlockAccessibility ::= <PoolIngressMatrix> <ResourceBlockAccessibility ::= <PoolIngressMatrix>
<PoolEgressMatrix> <PoolEgressMatrix>
[<ResourceWaveConstraints> ::= <IngressWaveConstraints> [<ResourceWaveConstraints> ::= <IngressWaveConstraints>
<EgressWaveConstraints> <EgressWaveConstraints>
<ResourcePoolState> ::=(<ResourceBlockID><NumResourcesInUse>)... <ResourcePoolState>
::=(<ResourceBlockID><NumResourcesInUse><InAvailableWavelengths><OutA
vailableWavelengths>)...
Note that except for <ResourcePoolState> all the other components of Note that except for <ResourcePoolState> all the other components of
<ResourcePool> are relatively static. <ResourcePool> are relatively static. Also the
<InAvailableWavelengths> and <OutAvailableWavelengths> are only used
in the cases of shared ingress or egress access to the particular
block. See the resource block information in the next section to see
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 <EgressWaveConstraints> wavelength converter) were modeled in the <EgressWaveConstraints>
previously discussed. As discussed in [WSON-Frame] we can model the previously discussed. As discussed in [WSON-Frame] we can model the
constraints on an electro-optical resource in terms of input constraints on an electro-optical resource in terms of input
constraints, processing capabilities, and output constraints: constraints, processing capabilities, and output constraints:
<ResourceBlockInfo> ::= <ResourceBlockInfo> ::=
([<ResourceSet>]<InputConstraints><ProcessingCapabilities><OutputCons ([<ResourceSet>]<InputConstraints><ProcessingCapabilities><OutputCons
traints>)* traints>)*
Where <ResourceSet> is a list of resource block identifiers with the Where <ResourceSet> is a list of resource block identifiers with the
same characteristics. If this set is missing the constraints are same characteristics. If this set is missing the constraints are
applied to the entire network element. applied to the entire network element.
The <InputConstraints> are signal compatibility based constraints. The <InputConstraints> are signal compatibility based constraints
The details of these constraints are defined in section 5.3. and/or shared access constraint indication. The details of these
constraints are defined in section 5.3.
<InputConstraints> ::= <ModulationTypeList> <FECTypeList> <InputConstraints> ::= <SharedIngress><ModulationTypeList>
<BitRateRange> <ClientSignalList> <FECTypeList> <BitRateRange> <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> <FaultPerfMon> <VendorSpecific> <RegenerationCapabilities> <FaultPerfMon> <VendorSpecific>
The <OutputConstraints> are either restrictions on the properties of The <OutputConstraints> are either restrictions on the properties of
the signal leaving the resource or network element or options the signal leaving the block, options concerning the signal
concerning the signal properties when leaving the resource or network properties when leaving the resource or shared fiber egress
element. constraint indication.
<OutputConstraints> := <ModulationTypeList><FECTypeList> <OutputConstraints> :=
<SharedEgress><ModulationTypeList><FECTypeList>
5.3. Compatibility and Capability Details 5.3. Compatibility and Capability Details
5.3.1. Modulation Type List 5.3.1. Shared Ingress or Egress Indication
As discussed in the previous section and shown in Figure 2 the
ingress or egress access to a resource block may be via a shared
fiber. The <SharedIngress> and <SharedEgress> elements are indicators
for this condition with respect to the block being described.
5.3.2. Modulation Type List
Modulation type, also known as optical tributary signal class, Modulation type, also known as optical tributary signal class,
comes in two distinct flavors: (i) ITU-T standardized types; (ii) comes in two distinct flavors: (i) ITU-T standardized types; (ii)
vendor specific types. The permitted modulation type list can vendor specific types. The permitted modulation type list can
include any mixture of standardized and vendor specific types. include any mixture of standardized and vendor specific types.
<modulation-list>::= <modulation-list>::=
[<STANDARD_MODULATION>|<VENDOR_MODULATION>]... [<STANDARD_MODULATION>|<VENDOR_MODULATION>]...
Where the STANDARD_MODULATION object just represents one of the Where the STANDARD_MODULATION object just represents one of the
ITU-T standardized optical tributary signal class and the ITU-T standardized optical tributary signal class and the
VENDOR_MODULATION object identifies one vendor specific modulation VENDOR_MODULATION object identifies one vendor specific modulation
type. type.
5.3.2. FEC Type List 5.3.3. FEC Type List
Some devices can handle more than one FEC type and hence a list is Some devices can handle more than one FEC type and hence a list is
needed. needed.
<fec-list>::= [<FEC>] <fec-list>::= [<FEC>]
Where the FEC object represents one of the ITU-T standardized FECs Where the FEC object represents one of the ITU-T standardized FECs
defined in [G.709], [G.707], [G.975.1] or a vendor-specific FEC. defined in [G.709], [G.707], [G.975.1] or a vendor-specific FEC.
5.3.3. Bit Rate Range List 5.3.4. Bit Rate Range List
Some devices can handle more than one particular bit rate range Some devices can handle more than one particular bit rate range
and hence a list is needed. and hence a list is needed.
<rate-range-list>::= [<rate-range>]... <rate-range-list>::= [<rate-range>]...
<rate-range>::=<START_RATE><END_RATE> <rate-range>::=<START_RATE><END_RATE>
Where the START_RATE object represents the lower end of the range Where the START_RATE object represents the lower end of the range
and the END_RATE object represents the higher end of the range. and the END_RATE object represents the higher end of the range.
5.3.4. Acceptable Client Signal List 5.3.5. Acceptable Client Signal List
The list is simply: The list is simply:
<client-signal-list>::=[<GPID>]... <client-signal-list>::=[<GPID>]...
Where the Generalized Protocol Identifiers (GPID) object Where the Generalized Protocol Identifiers (GPID) object
represents one of the IETF standardized GPID values as defined in represents one of the IETF standardized GPID values as defined in
[RFC3471] and [RFC4328]. [RFC3471] and [RFC4328].
5.3.5. Processing Capability List 5.3.6. Processing Capability List
We have defined ProcessingCapabilities in Section 5.2 as follows: We have defined ProcessingCapabilities in Section 5.2 as follows:
<ProcessingCapabilities> ::= <NumResources> <ProcessingCapabilities> ::= <NumResources>
<RegenerationCapabilities> <FaultPerfMon> <VendorSpecific> <RegenerationCapabilities> <FaultPerfMon> <VendorSpecific>
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:
 End of changes. 26 change blocks. 
59 lines changed or deleted 122 lines changed or added

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