draft-ietf-ccamp-rwa-info-06.txt   draft-ietf-ccamp-rwa-info-07.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: August 2010 Grotto Networking
D. Li D. Li
Huawei Huawei
W. Imajuku W. Imajuku
NTT NTT
February 8, 2010 February 18, 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-06.txt draft-ietf-ccamp-rwa-info-07.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 8, 2010. This Internet-Draft will expire on August 18, 2010.
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 36 skipping to change at page 2, line 36
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
2. Terminology....................................................5 2. Terminology....................................................5
3. Routing and Wavelength Assignment Information Model............5 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).....................................6
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..11
5.3. Compatibility and Capability Details.....................11 5.3. Compatibility and Capability Details.....................12
5.3.1. Modulation Type List................................11 5.3.1. Modulation Type List................................12
5.3.2. FEC Type List.......................................12 5.3.2. FEC Type List.......................................12
5.3.3. Bit Rate Range List.................................12 5.3.3. Bit Rate Range List.................................12
5.3.4. Acceptable Client Signal List.......................12 5.3.4. Acceptable Client Signal List.......................12
5.3.5. Processing Capability List..........................12 5.3.5. Processing Capability List..........................13
6. Link Information (General)....................................13 6. Link Information (General)....................................13
6.1. Administrative Group.....................................13 6.1. Administrative Group.....................................13
6.2. Interface Switching Capability Descriptor................13 6.2. Interface Switching Capability Descriptor................14
6.3. Link Protection Type (for this link).....................14 6.3. Link Protection Type (for this link).....................14
6.4. Shared Risk Link Group Information.......................14 6.4. Shared Risk Link Group Information.......................14
6.5. Traffic Engineering Metric...............................14 6.5. Traffic Engineering Metric...............................14
6.6. Port Label (Wavelength) Restrictions.....................14 6.6. Port Label (Wavelength) Restrictions.....................14
7. Dynamic Components of the Information Model...................16 7. Dynamic Components of the Information Model...................16
7.1. Dynamic Link Information (General).......................16 7.1. Dynamic Link Information (General).......................16
7.2. Dynamic Node Information (WSON Specific).................16 7.2. Dynamic Node Information (WSON Specific).................16
8. Security Considerations.......................................17 8. Security Considerations.......................................17
9. IANA Considerations...........................................17 9. IANA Considerations...........................................17
10. Acknowledgments..............................................17 10. Acknowledgments..............................................17
skipping to change at page 5, line 18 skipping to change at page 5, line 18
Renumbered sections for clarity. Renumbered sections for clarity.
Updated abstract and introduction to encompass signal Updated abstract and introduction to encompass signal
compatibility/generalization. compatibility/generalization.
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
Simplified information model for WSON specifics, by combining similar
fields and introducing simpler aggregate information elements.
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 48 skipping to change at page 8, line 52
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.
This leads to the following formal high level model:
<Node_Information> ::= <Node_ID> [<ConnectivityMatrix>...] <Node_Information> ::= <Node_ID> [<ConnectivityMatrix>...]
[<ResourcePool>] [<ResourceProperties>] [<ResourcePool>]
Where
<ResourcePool> ::= <ResourceBlockInfo>...
[<ResourceBlockAccessibility>...] [<ResourceWaveConstraints>...]
[<RBPoolState>]
First we will address the accessibility of resource blocks then we
will discuss their properties.
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 [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
skipping to change at page 10, line 35 skipping to change at page 10, line 43
| | | |
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.
Formally we can specify the model as: Formally we can specify the model as:
<ResourcePool> ::= <ResourceBlockInfo><PoolIngressMatrix> <ResourceBlockAccessibility ::= <PoolIngressMatrix>
<IngressWaveConstraints> [<ResourcePoolState>] <PoolEgressMatrix>
<EgressWaveConstraints> <PoolEgressMatrix>
Where
<ResourceBlockInfo>:=(<ResourceBlockID><ResourceBlockSize>)... [<ResourceWaveConstraints> ::= <IngressWaveConstraints>
<EgressWaveConstraints>
<ResourcePoolState>:=(<ResourceBlockID><NumResourcesInUse>)... <ResourcePoolState> ::=(<ResourceBlockID><NumResourcesInUse>)...
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.
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:
<ResourceProperties> ::= <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. The details of these constraints are defined in section 5.3.
<InputConstraints> ::= <InputConstraints> ::= <ModulationTypeList> <FECTypeList>
<ModulationTypeList><FECTypeList><BitRateRange><ClientSignalList> <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> ::= <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 resource or network element or options
concerning the signal properties when leaving the resource or network concerning the signal properties when leaving the resource or network
element. element.
<OutputConstraints> := <ModulationTypeList><FECTypeList> <OutputConstraints> := <ModulationTypeList><FECTypeList>
5.3. Compatibility and Capability Details 5.3. Compatibility and Capability Details
5.3.1. Modulation Type List 5.3.1. 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>::=
skipping to change at page 13, line 5 skipping to change at page 13, line 9
<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.5. Processing Capability List
We have defined ProcessingCapabilities in Section 5.2 as follows: We have defined ProcessingCapabilities in Section 5.2 as follows:
<ProcessingCapabilities> ::= <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:
1. Regeneration capability 1. Number of Resources within the block
2. Fault and performance monitoring 2. Regeneration capability
3. Vendor Specific capability 3. Fault and performance monitoring
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 and IS-IS [RFC3630],
[RFC5305] along with GMPLS routing protocol extensions for OSPF and [RFC5305] along with GMPLS routing protocol extensions for OSPF and
IS-IS [RFC4203, RFC5307] provide the bulk of the relatively static IS-IS [RFC4203, RFC5307] provide the bulk of the relatively static
link information needed by the RWA process. However, WSON networks link information needed by the RWA process. However, WSON networks
 End of changes. 22 change blocks. 
27 lines changed or deleted 44 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/