draft-ietf-ccamp-rwa-wson-encode-11.txt   draft-ietf-ccamp-rwa-wson-encode-12.txt 
Network Working Group G. Bernstein Network Working Group G. Bernstein
Internet Draft Grotto Networking Internet Draft Grotto Networking
Intended status: Standards Track Y. Lee Intended status: Standards Track Y. Lee
Expires: September 2011 D. Li Expires: February 2012 D. Li
Huawei Huawei
W. Imajuku W. Imajuku
NTT NTT
March 14, 2011 August 8, 2011
Routing and Wavelength Assignment Information Encoding for Routing and Wavelength Assignment Information Encoding for
Wavelength Switched Optical Networks Wavelength Switched Optical Networks
draft-ietf-ccamp-rwa-wson-encode-11.txt draft-ietf-ccamp-rwa-wson-encode-12.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 38 skipping to change at page 1, line 38
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 September 14, 2011. This Internet-Draft will expire on January 8, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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 3, line 12 skipping to change at page 3, line 12
1.1.2. Changes from 01 draft................................5 1.1.2. Changes from 01 draft................................5
1.1.3. Changes from 02 draft................................5 1.1.3. Changes from 02 draft................................5
1.1.4. Changes from 03 draft................................5 1.1.4. Changes from 03 draft................................5
1.1.5. Changes from 04 draft................................5 1.1.5. Changes from 04 draft................................5
1.1.6. Changes from 05 draft................................5 1.1.6. Changes from 05 draft................................5
1.1.7. Changes from 06 draft................................5 1.1.7. Changes from 06 draft................................5
1.1.8. Changes from 07 draft................................5 1.1.8. Changes from 07 draft................................5
1.1.9. Changes from 08 draft................................6 1.1.9. Changes from 08 draft................................6
1.1.10. Changes from 09 draft...............................6 1.1.10. Changes from 09 draft...............................6
1.1.11. Changes from 10 draft...............................6 1.1.11. Changes from 10 draft...............................6
1.1.12. Changes from 11 draft...............................6
2. Terminology....................................................6 2. Terminology....................................................6
3. Resource Pool Accessibility/Availability.......................7 3. Resources, Blocks, Sets, and the Resource Pool.................7
3.1. Resource Pool Accessibility Sub-TLV.......................8 3.1. Resource Block Set Field..................................8
3.2. Resource Block Wavelength Constraints Sub-TLV............10 4. Resource Pool Accessibility/Availability.......................9
3.3. Resource Pool State Sub-TLV..............................10 4.1. Resource Pool Accessibility Sub-TLV.......................9
3.4. Block Shared Access Wavelength Availability sub-TLV......12 4.2. Resource Block Wavelength Constraints Sub-TLV............11
4. Resource Properties Encoding..................................13 4.3. Resource Pool State Sub-TLV..............................12
4.1. Resource Block Information Sub-TLV.......................13 4.4. Block Shared Access Wavelength Availability sub-TLV......13
4.2. Input Modulation Format List Sub-Sub-TLV.................14 5. Resource Properties Encoding..................................14
4.2.1. Modulation Format Field.............................15 5.1. Resource Block Information Sub-TLV.......................15
4.3. Input FEC Type List Sub-Sub-TLV..........................17 5.2. Input Modulation Format List Sub-Sub-TLV.................16
4.3.1. FEC Type Field......................................17 5.2.1. Modulation Format Field.............................16
4.4. Input Bit Range List Sub-Sub-TLV.........................19 5.3. Input FEC Type List Sub-Sub-TLV..........................18
4.4.1. Bit Range Field.....................................19 5.3.1. FEC Type Field......................................18
4.5. Input Client Signal List Sub-Sub-TLV.....................20 5.4. Input Bit Range List Sub-Sub-TLV.........................20
4.6. Processing Capability List Sub-Sub-TLV...................21 5.4.1. Bit Range Field.....................................20
4.6.1. Processing Capabilities Field.......................21 5.5. Input Client Signal List Sub-Sub-TLV.....................21
4.7. Output Modulation Format List Sub-Sub-TLV................23 5.6. Processing Capability List Sub-Sub-TLV...................22
4.8. Output FEC Type List Sub-Sub-TLV.........................23 5.6.1. Processing Capabilities Field.......................22
5. Security Considerations.......................................23 5.7. Output Modulation Format List Sub-Sub-TLV................24
6. IANA Considerations...........................................23 5.8. Output FEC Type List Sub-Sub-TLV.........................24
7. Acknowledgments...............................................23 6. Security Considerations.......................................24
APPENDIX A: Encoding Examples....................................23 7. IANA Considerations...........................................25
A.1. Wavelength Converter Accessibility Sub-TLV...............23 8. Acknowledgments...............................................25
A.2. Wavelength Conversion Range Sub-TLV......................23 APPENDIX A: Encoding Examples....................................26
A.3. An OEO Switch with DWDM Optics...........................23 A.1. Wavelength Converter Accessibility Sub-TLV...............26
8. References....................................................23 A.2. Wavelength Conversion Range Sub-TLV......................27
8.1. Normative References.....................................23 A.3. An OEO Switch with DWDM Optics...........................28
8.2. Informative References...................................23 9. References....................................................32
9. Contributors..................................................23 9.1. Normative References.....................................32
Authors' Addresses...............................................23 9.2. Informative References...................................32
Intellectual Property Statement..................................23 10. Contributors.................................................33
Disclaimer of Validity...........................................23 Authors' Addresses...............................................34
Intellectual Property Statement..................................35
Disclaimer of Validity...........................................35
1. Introduction 1. Introduction
A Wavelength Switched Optical Network (WSON) is a Wavelength Division A Wavelength Switched Optical Network (WSON) is a Wavelength Division
Multiplexing (WDM) optical network in which switching is performed Multiplexing (WDM) optical network in which switching is performed
selectively based on the center wavelength of an optical signal. selectively based on the center wavelength of an optical signal.
[WSON-Frame] describes a framework for Generalized Multiprotocol [RFC6163] describes a framework for Generalized Multiprotocol Label
Label Switching (GMPLS) and Path Computation Element (PCE) control of Switching (GMPLS) and Path Computation Element (PCE) control of a
a WSON. Based on this framework, [WSON-Info] describes an information WSON. Based on this framework, [WSON-Info] describes an information
model that specifies what information is needed at various points in model that specifies what information is needed at various points in
a WSON in order to compute paths and establish Label Switched Paths a WSON in order to compute paths and establish Label Switched Paths
(LSPs). (LSPs).
This document provides efficient encodings of information needed by This document provides efficient encodings of information needed by
the routing and wavelength assignment (RWA) process in a WSON. Such the routing and wavelength assignment (RWA) process in a WSON. Such
encodings can be used to extend GMPLS signaling and routing encodings can be used to extend GMPLS signaling and routing
protocols. In addition these encodings could be used by other protocols. In addition these encodings could be used by other
mechanisms to convey this same information to a path computation mechanisms to convey this same information to a path computation
element (PCE). Note that since these encodings are relatively element (PCE). Note that since these encodings are relatively
skipping to change at page 4, line 36 skipping to change at page 4, line 36
GMPLS control plane. GMPLS control plane.
Note that encodings of information needed by the routing and label Note that encodings of information needed by the routing and label
assignment process applicable to general networks beyond WSON are assignment process applicable to general networks beyond WSON are
addressed in a separate document [Gen-Encode]. addressed in a separate document [Gen-Encode].
1.1. Revision History 1.1. Revision History
1.1.1. Changes from 00 draft 1.1.1. Changes from 00 draft
Edits to make consistent with update to [Otani], i.e., removal of Edits to make consistent with update to [RFC6205], i.e., removal of
sign bit. sign bit.
Clarification of TBD on connection matrix type and possibly Clarification of TBD on connection matrix type and possibly
numbering. numbering.
New sections for wavelength converter pool encoding: Wavelength New sections for wavelength converter pool encoding: Wavelength
Converter Set Sub-TLV, Wavelength Converter Accessibility Sub-TLV, Converter Set Sub-TLV, Wavelength Converter Accessibility Sub-TLV,
Wavelength Conversion Range Sub-TLV, WC Usage State Sub-TLV. Wavelength Conversion Range Sub-TLV, WC Usage State Sub-TLV.
Added optional wavelength converter pool TLVs to the composite node Added optional wavelength converter pool TLVs to the composite node
skipping to change at page 6, line 24 skipping to change at page 6, line 24
Clarifying edits in section 3 on pools, blocks, and resources. Clarifying edits in section 3 on pools, blocks, and resources.
1.1.10. Changes from 09 draft 1.1.10. Changes from 09 draft
Fixed the "Block Shared Access Wavelength Availability sub-TLV" of Fixed the "Block Shared Access Wavelength Availability sub-TLV" of
section 3.4 to use an "RB set field" rather than a single RB ID. section 3.4 to use an "RB set field" rather than a single RB ID.
Removed all 1st person idioms. Removed all 1st person idioms.
1.1.11. Changes from 10 draft 1.1.11. Changes from 10 draft
Removed remaining 1st person idioms. Updated IANA section. Removed remaining 1st person idioms. Updated IANA section. Update
references for newly issued RFCs.
1.1.12. Changes from 11 draft
Fixed length fields in section 4 to be 16 bits, correcting errors in
TLV and field figures. Added a separate section on resources, blocks,
sets and the resource pool. Moved definition of the resource block
set field to this new section.
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
skipping to change at page 7, line 5 skipping to change at page 7, line 13
"equivalent" content centered at a different wavelength. Wavelength "equivalent" content centered at a different wavelength. Wavelength
conversion can be implemented via an optical-electronic-optical (OEO) conversion can be implemented via an optical-electronic-optical (OEO)
process or via a strictly optical process. process or via a strictly optical process.
WDM: Wavelength Division Multiplexing. WDM: Wavelength Division Multiplexing.
Wavelength Switched Optical Network (WSON): A WDM based optical Wavelength Switched Optical Network (WSON): A WDM based optical
network in which switching is performed selectively based on the network in which switching is performed selectively based on the
center wavelength of an optical signal. center wavelength of an optical signal.
3. Resource Pool Accessibility/Availability 3. Resources, Blocks, Sets, and the Resource Pool
This section defines the sub-TLVs for dealing with accessibility and The optical system to be encoded may contain a pool of resources of
availability of resource blocks within a pool of resources. These different types and properties for processing optical signals. For
include the ResourceBlockAccessibility, ResourceWaveConstraints, and the purposes here a "resource" is an individual entity such as a
RBPoolState sub-TLVs. All these sub-TLVs are concerned with sets of wavelength converter or regenerator within the optical node that acts
resources. As described in [WSON-Info] a resource pool is composed of on an individual wavelength signal.
blocks of resources with similar properties and accessibility
characteristics.
In a WSON node that includes resource blocks (RB) denoting subsets of Since resources tend to be packaged together in blocks of similar
these blocks allows one to efficiently describe common properties the devices, e.g., on line cards or other types of modules, the
blocks and to describe the structure, if non-trivial, of the resource fundamental unit of identifiable resource in this document is the
pool. The RB Set field is defined in a similar manner to the label "resource block". A resource block may contain one or more resources.
set concept of [RFC3471]. As resource blocks are the smallest identifiable unit of processing
resource, one should group together resources into blocks if they
have similar characteristics relevant to the optical system being
modeled, e.g., processing properties, accessibility, etc.
This document defines the following sub-TLVs pertaining to resources
within an optical node:
. Resource Pool Accessibility Sub-TLV
. Resource Block Wavelength Constraints Sub-TLV
. Resource Pool State Sub-TLV
. Block Shared Access Wavelength Availability Sub-TLV
. Resource Block Information Sub-TLV
Each of these sub-TLVs works with one or more sets of resources
rather than just a single resource block. This motivates the
following field definition.
3.1. Resource Block Set Field
In a WSON node that includes resource blocks (RB), denoting subsets
of these blocks allows one to efficiently describe common properties
the blocks and to describe the structure and characteristics, if non-
trivial, of the resource pool. The RB Set field is defined in a
similar manner to the label set concept of [RFC3471].
The information carried in a RB set field is defined by: The information carried in a RB set field is defined by:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Action |E|C| Reserved | Length | | Action |E|C| Reserved | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB Identifier 1 | RB Identifier 2 | | RB Identifier 1 | RB Identifier 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 8, line 28 skipping to change at page 9, line 19
Length: 16 bits Length: 16 bits
The total length of this field in bytes. The total length of this field in bytes.
RB Identifier: RB Identifier:
The RB identifier represents the ID of the resource block which is a The RB identifier represents the ID of the resource block which is a
16 bit integer. 16 bit integer.
3.1. Resource Pool Accessibility Sub-TLV Usage Note: the inclusive range "Action" can result in very compact
encoding of resource sets and it can be advantages to number resource
blocks in such a way so that status updates (dynamic information) can
take advantage of this efficiency.
4. Resource Pool Accessibility/Availability
This section defines the sub-TLVs for dealing with accessibility and
availability of resource blocks within a pool of resources. These
include the ResourceBlockAccessibility, ResourceWaveConstraints, and
RBPoolState sub-TLVs.
4.1. Resource Pool Accessibility Sub-TLV
This sub-TLV describes the structure of the resource pool in relation This sub-TLV describes the structure of the resource pool in relation
to the switching device. In particular it indicates the ability of an to the switching device. In particular it indicates the ability of an
ingress port to reach a resource block and of a resource block to ingress port to reach sets of resources and of a sets of resources to
reach a particular egress port. This is the PoolIngressMatrix and reach a particular egress port. This is the PoolIngressMatrix and
PoolEgressMatrix of [WSON-Info]. PoolEgressMatrix of [WSON-Info].
The resource pool accessibility sub-TLV is defined by: The resource pool accessibility sub-TLV is defined by:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Connectivity | Reserved | | Connectivity | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 10, line 5 skipping to change at page 11, line 5
The Link Set Field is defined in [Gen-Encode]. The Link Set Field is defined in [Gen-Encode].
Note that the direction parameter within the Link Set Field is used Note that the direction parameter within the Link Set Field is used
to indicate whether the link set is an ingress or egress link set, to indicate whether the link set is an ingress or egress link set,
and the bidirectional value for this parameter is not permitted in and the bidirectional value for this parameter is not permitted in
this sub-TLV. this sub-TLV.
See Appendix A.1 for an illustration of this encoding. See Appendix A.1 for an illustration of this encoding.
3.2. Resource Block Wavelength Constraints Sub-TLV 4.2. Resource Block Wavelength Constraints Sub-TLV
Resources, such as wavelength converters, etc., may have a limited Resources, such as wavelength converters, etc., may have a limited
input or output wavelength ranges. Additionally, due to the structure input or output wavelength ranges. Additionally, due to the structure
of the optical system not all wavelengths can necessarily reach or of the optical system not all wavelengths can necessarily reach or
leave all the resources. These properties are described by using one leave all the resources. These properties are described by using one
or more resource wavelength restrictions sub-TLVs as defined below: or more resource wavelength restrictions sub-TLVs as defined below:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 10, line 41 skipping to change at page 12, line 5
Input Wavelength Set Field: Input Wavelength Set Field:
Indicates the wavelength input restrictions of the RBs in the Indicates the wavelength input restrictions of the RBs in the
corresponding RB set. corresponding RB set.
Output Wavelength Set Field: Output Wavelength Set Field:
Indicates the wavelength output restrictions of RBs in the Indicates the wavelength output restrictions of RBs in the
corresponding RB set. corresponding RB set.
3.3. Resource Pool State Sub-TLV 4.3. Resource Pool State Sub-TLV
The state of the pool is given by the number of resources available The state of the pool is given by the number of resources available
in each block. The usage state of resources within a block is encoded with particular characteristics. A resource block set is used to
as either a list of 16 bit integer values or a bit map indicating encode all or a subset of the resources of interest. The usage state
whether a single resource is available or in use. The bit map of resources within a resource block set is encoded as either a list
encoding is appropriate when resource blocks consist of a single of 16 bit integer values or a bit map indicating whether a single
resource. This information can be relatively dynamic, i.e., can resource is available or in use. The bit map encoding is appropriate
change when a connection is established or torn down. when resource blocks consist of a single resource. This information
can be relatively dynamic, i.e., can change when a connection (LSP is
established or torn down.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Action | Reserved | | Action | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB Set Field | | RB Set Field |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB Usage state | | RB Usage state |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 12, line 18 skipping to change at page 13, line 28
RB Usage state: Variable Length but must be a multiple of 4 byes. RB Usage state: Variable Length but must be a multiple of 4 byes.
Each bit indicates the usage status of one RB with 0 indicating the Each bit indicates the usage status of one RB with 0 indicating the
RB is available and 1 indicating the RB is in used. The sequence of RB is available and 1 indicating the RB is in used. The sequence of
the bit map is ordered according to the RB Set field with this sub- the bit map is ordered according to the RB Set field with this sub-
TLV. TLV.
Padding bits: Variable Length Padding bits: Variable Length
3.4. Block Shared Access Wavelength Availability sub-TLV 4.4. Block Shared Access Wavelength Availability sub-TLV
Resources blocks may be accessed via a shared fiber. If this is the Resources blocks may be accessed via a shared fiber. If this is the
case then wavelength availability on these shared fibers is needed to case, then wavelength availability on these shared fibers is needed
understand resource availability. to understand resource availability.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I|E| Reserved | |I|E| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB Set Field | | RB Set Field |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Ingress Available Wavelength Set Field | | Ingress Available Wavelength Set Field |
skipping to change at page 13, line 20 skipping to change at page 14, line 29
Ingress Available Wavelength Set Field: Ingress Available Wavelength Set Field:
Indicates the wavelengths currently available (not being used) on the Indicates the wavelengths currently available (not being used) on the
ingress fiber to this resource block. ingress fiber to this resource block.
Egress Available Wavelength Set Field: Egress Available Wavelength Set Field:
Indicates the wavelengths currently available (not being used) on the Indicates the wavelengths currently available (not being used) on the
egress fiber from this resource block. egress fiber from this resource block.
4. Resource Properties Encoding 5. Resource Properties Encoding
Within a WSON network element (NE) there may be resources with signal Within a WSON network element (NE) there may be resources with signal
compatibility constraints. Such resources typically come in "blocks" compatibility constraints. These resources be regenerators,
which contain a group on identical and indistinguishable individual wavelength converters, etc... Such resources may also constitute the
resources. These resource blocks may consist of regenerators, network element as a whole as in the case of an electro optical
wavelength converters, etc... Such resource blocks may also switch. This section primarily focuses on the signal compatibility
constitute the network element as a whole as in the case of an and processing properties of such a resource block.
electro optical switch. This section primarily focuses on the signal
compatibility and processing properties of such a resource block, the
accessibility aspects of a resource in a shared pool, except for the
shared access indicators, were encoded in the previous section.
The fundamental properties of a resource block, such as a regenerator The fundamental properties of a resource block, such as a regenerator
or wavelength converter, are: or wavelength converter, are:
(a)Input constraints (shared ingress, modulation, FEC, bit rate, (a)Input constraints (shared ingress, modulation, FEC, bit rate,
GPID) GPID)
(b)Processing capabilities (number of resources in a block, (b)Processing capabilities (number of resources in a block,
regeneration, performance monitoring, vendor specific) regeneration, performance monitoring, vendor specific)
(c)Output Constraints (shared egress, modulation, FEC) (c)Output Constraints (shared egress, modulation, FEC)
4.1. Resource Block Information Sub-TLV 5.1. Resource Block Information Sub-TLV
Resource Block descriptor sub-TLVs are used to convey relatively Resource Block descriptor sub-TLVs are used to convey relatively
static information about individual resource blocks including the static information about individual resource blocks including the
resource block properties of section 3. and the number of resources resource block compatibility properties, processing properties, and
in a block. the number of resources in a block.
This sub-TLV has the following format: This sub-TLV has the following format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB Set Field | | RB Set Field |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I|E| Reserved | |I|E| Reserved |
skipping to change at page 14, line 43 skipping to change at page 16, line 5
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output FEC Type List Sub-Sub-TLV (opt) | | Output FEC Type List Sub-Sub-TLV (opt) |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where I and E, the shared ingress/egress indicator, is set to 1 if Where I and E, the shared ingress/egress indicator, is set to 1 if
the resource blocks identified in the RB set field utilized a shared the resource blocks identified in the RB set field utilized a shared
fiber for ingress/egress access and set to 0 otherwise. fiber for ingress/egress access and set to 0 otherwise.
4.2. Input Modulation Format List Sub-Sub-TLV 5.2. Input Modulation Format List Sub-Sub-TLV
This sub-sub-TLV contains a list of acceptable input modulation This sub-sub-TLV contains a list of acceptable input modulation
formats. formats.
Type := Input Modulation Format List Type := Input Modulation Format List
Value := A list of Modulation Format Fields Value := A list of Modulation Format Fields
4.2.1. Modulation Format Field 5.2.1. Modulation Format Field
Two different types of modulation format fields are defined: a Two different types of modulation format fields are defined: a
standard modulation field and a vendor specific modulation field. standard modulation field and a vendor specific modulation field.
Both start with the same 32 bit header shown below. Both start with the same 32 bit header shown below.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|S|I| Modulation ID | Length | |S|I| Modulation ID | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where S bit set to 1 indicates a standardized modulation format and S Where S bit set to 1 indicates a standardized modulation format and S
bit set to 0 indicates a vendor specific modulation format. The bit set to 0 indicates a vendor specific modulation format. The
length is the length in bytes of the entire modulation type field. length is the length in bytes of the entire modulation type field.
Where I bit set to 1 indicates it is an input modulation constraint Where I bit set to 1 indicates it is an input modulation constraint
and I bit set to 0 indicates it is an output modulation constraint. and I bit set to 0 indicates it is an output modulation constraint.
Note that if an output modulation is not specified then it is implied Note that if an output modulation is not specified then it is implied
that it is the same as the input modulation. In such case, no that it is the same as the input modulation. In such case, no
modulation conversion is performed. modulation conversion is performed.
The format for the standardized type for the input modulation is The format for the standardized type for the input modulation is
given by: given by:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1|1| Modulation ID | Length | |1|1| Modulation ID | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Possible additional modulation parameters depending upon | | Possible additional modulation parameters depending upon |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: the modulation ID : : the modulation ID :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Modulation ID (S bit = 1); Input modulation (I bit = 1) Modulation ID (S bit = 1); Input modulation (I bit = 1)
Takes on the following currently defined values: Takes on the following currently defined values:
0 Reserved 0 Reserved
1 optical tributary signal class NRZ 1.25G 1 optical tributary signal class NRZ 1.25G
2 optical tributary signal class NRZ 2.5G 2 optical tributary signal class NRZ 2.5G
3 optical tributary signal class NRZ 10G 3 optical tributary signal class NRZ 10G
4 optical tributary signal class NRZ 40G 4 optical tributary signal class NRZ 40G
5 optical tributary signal class RZ 40G 5 optical tributary signal class RZ 40G
skipping to change at page 16, line 41 skipping to change at page 18, line 4
This is a vendor assigned identifier for the modulation type. This is a vendor assigned identifier for the modulation type.
Enterprise Number Enterprise Number
A unique identifier of an organization encoded as a 32-bit integer. A unique identifier of an organization encoded as a 32-bit integer.
Enterprise Numbers are assigned by IANA and managed through an IANA Enterprise Numbers are assigned by IANA and managed through an IANA
registry [RFC2578]. registry [RFC2578].
Vendor Specific Additional parameters Vendor Specific Additional parameters
There can be potentially additional parameters characterizing the There can be potentially additional parameters characterizing the
vendor specific modulation. vendor specific modulation.
4.3. Input FEC Type List Sub-Sub-TLV 5.3. Input FEC Type List Sub-Sub-TLV
This sub-sub-TLV contains a list of acceptable FEC types. This sub-sub-TLV contains a list of acceptable FEC types.
Type := Input FEC Type field List Type := Input FEC Type field List
Value := A list of FEC type Fields Value := A list of FEC type Fields
4.3.1. FEC Type Field 5.3.1. FEC Type Field
The FEC type Field may consist of two different formats of fields: a The FEC type Field may consist of two different formats of fields: a
standard FEC field or a vendor specific FEC field. Both start with standard FEC field or a vendor specific FEC field. Both start with
the same 32 bit header shown below. the same 32 bit header shown below.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|S|I| FEC ID | Length | |S|I| FEC ID | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Possible additional FEC parameters depending upon | | Possible additional FEC parameters depending upon |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: the FEC ID : : the FEC ID :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where S bit set to 1 indicates a standardized FEC format and S bit Where S bit set to 1 indicates a standardized FEC format and S bit
set to 0 indicates a vendor specific FEC format. The length is the set to 0 indicates a vendor specific FEC format. The length is the
length in bytes of the entire FEC type field. length in bytes of the entire FEC type field.
skipping to change at page 18, line 8 skipping to change at page 19, line 8
it is the same as the input FEC. In such case, no FEC conversion is it is the same as the input FEC. In such case, no FEC conversion is
performed. performed.
The length is the length in bytes of the entire FEC type field. The length is the length in bytes of the entire FEC type field.
The format for input standard FEC field is given by: The format for input standard FEC field is given by:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1|1| FEC ID | Length | |1|1| FEC ID | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Possible additional FEC parameters depending upon | | Possible additional FEC parameters depending upon |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: the FEC ID : : the FEC ID :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Takes on the following currently defined values for the standard Takes on the following currently defined values for the standard
FEC ID: FEC ID:
0 Reserved 0 Reserved
skipping to change at page 19, line 8 skipping to change at page 20, line 8
(1020,988) codes) (1020,988) codes)
Where RS stands for Reed-Solomon and BCH for Bose-Chaudhuri- Where RS stands for Reed-Solomon and BCH for Bose-Chaudhuri-
Hocquengham. Hocquengham.
The format for input vendor-specific FEC field is given by: The format for input vendor-specific FEC field is given by:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|1| Vendor FEC ID | Length | |0|1| Vendor FEC ID | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Enterprise Number | | Enterprise Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Any vendor specific additional FEC parameters : : Any vendor specific additional FEC parameters :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Vendor FEC ID Vendor FEC ID
This is a vendor assigned identifier for the FEC type. This is a vendor assigned identifier for the FEC type.
skipping to change at page 19, line 30 skipping to change at page 20, line 30
A unique identifier of an organization encoded as a 32-bit integer. A unique identifier of an organization encoded as a 32-bit integer.
Enterprise Numbers are assigned by IANA and managed through an IANA Enterprise Numbers are assigned by IANA and managed through an IANA
registry [RFC2578]. registry [RFC2578].
Vendor Specific Additional FEC parameters Vendor Specific Additional FEC parameters
There can be potentially additional parameters characterizing the There can be potentially additional parameters characterizing the
vendor specific FEC. vendor specific FEC.
4.4. Input Bit Range List Sub-Sub-TLV 5.4. Input Bit Range List Sub-Sub-TLV
This sub-sub-TLV contains a list of acceptable input bit rate ranges. This sub-sub-TLV contains a list of acceptable input bit rate ranges.
Type := Input Bit Range List Type := Input Bit Range List
Value := A list of Bit Range Fields Value := A list of Bit Range Fields
4.4.1. Bit Range Field 5.4.1. Bit Range Field
The bit rate range list sub-TLV makes use of the following bit rate The bit rate range list sub-TLV makes use of the following bit rate
range field: range field:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Starting Bit Rate | | Starting Bit Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Ending Bit Rate | | Ending Bit Rate |
skipping to change at page 20, line 33 skipping to change at page 21, line 33
+-+-+-+-+-+-+-+-+-+-+-+-+ Bit Range Field #1 +-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+ Bit Range Field #1 +-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: : : : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+ Bit Range Field #M +-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+ Bit Range Field #M +-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
4.5. Input Client Signal List Sub-Sub-TLV 5.5. Input Client Signal List Sub-Sub-TLV
This sub-sub-TLV contains a list of acceptable input client signal This sub-sub-TLV contains a list of acceptable input client signal
types. types.
Type := Input Client Signal List Type := Input Client Signal List
Value := A list of GPIDs Value := A list of GPIDs
The acceptable client signal list sub-TLV is a list of Generalized The acceptable client signal list sub-TLV is a list of Generalized
Protocol Identifiers (GPIDs). GPIDs are assigned by IANA and many are Protocol Identifiers (GPIDs). GPIDs are assigned by IANA and many are
skipping to change at page 21, line 17 skipping to change at page 22, line 17
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of GPIDs | GPID #1 | | Number of GPIDs | GPID #1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: | : : | :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| GPID #N | | | GPID #N | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where the number of GPIDs is an integer greater than or equal to one. Where the number of GPIDs is an integer greater than or equal to one.
4.6. Processing Capability List Sub-Sub-TLV 5.6. Processing Capability List Sub-Sub-TLV
This sub-sub-TLV contains a list of resource block processing This sub-sub-TLV contains a list of resource block processing
capabilities. capabilities.
Type := Processing Capabilities List Type := Processing Capabilities List
Value := A list of Processing Capabilities Fields Value := A list of Processing Capabilities Fields
The processing capability list sub-TLV is a list of WSON network The processing capability list sub-TLV is a list of WSON network
element (NE) that can perform signal processing functions including: element (NE) that can perform signal processing functions including:
skipping to change at page 21, line 40 skipping to change at page 22, line 40
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.
4.6.1. Processing Capabilities Field 5.6.1. Processing Capabilities Field
The processing capability field is then given by: The processing capability field is then given by:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Processing Cap ID | Length | | Processing Cap ID | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Possible additional capability parameters depending upon | | Possible additional capability parameters depending upon |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: the processing ID : : the processing ID :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
When the processing Cap ID is "number of resources" the format is When the processing Cap ID is "number of resources" the format is
simply: simply:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Processing Cap ID | Length = 8 | | Processing Cap ID | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of resources per block | | Number of resources per block |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
When the processing Cap ID is "regeneration capability", the When the processing Cap ID is "regeneration capability", the
following additional capability parameters are provided in the sub- following additional capability parameters are provided in the sub-
TLV: TLV:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
skipping to change at page 23, line 16 skipping to change at page 24, line 16
C=1: Fixed Regeneration Point C=1: Fixed Regeneration Point
C=2: Selective Regeneration Point C=2: Selective Regeneration Point
Note that when the capability of regenerator is indicated to be Note that when the capability of regenerator is indicated to be
Selective Regeneration Pools, regeneration pool properties such as Selective Regeneration Pools, regeneration pool properties such as
ingress and egress restrictions and availability need to be ingress and egress restrictions and availability need to be
specified. This encoding is to be determined in the later revision. specified. This encoding is to be determined in the later revision.
4.7. Output Modulation Format List Sub-Sub-TLV 5.7. Output Modulation Format List Sub-Sub-TLV
This sub-sub-TLV contains a list of available output modulation This sub-sub-TLV contains a list of available output modulation
formats. formats.
Type := Output Modulation Format List Type := Output Modulation Format List
Value := A list of Modulation Format Fields Value := A list of Modulation Format Fields
4.8. Output FEC Type List Sub-Sub-TLV 5.8. Output FEC Type List Sub-Sub-TLV
This sub-sub-TLV contains a list of output FEC types. This sub-sub-TLV contains a list of output FEC types.
Type := Output FEC Type field List Type := Output FEC Type field List
Value := A list of FEC type Fields Value := A list of FEC type Fields
5. Security Considerations 6. Security Considerations
This document defines protocol-independent encodings for WSON This document defines protocol-independent encodings for WSON
information and does not introduce any security issues. information and does not introduce any security issues.
However, other documents that make use of these encodings within However, other documents that make use of these encodings within
protocol extensions need to consider the issues and risks associated protocol extensions need to consider the issues and risks associated
with, inspection, interception, modification, or spoofing of any of with, inspection, interception, modification, or spoofing of any of
this information. It is expected that any such documents will this information. It is expected that any such documents will
describe the necessary security measures to provide adequate describe the necessary security measures to provide adequate
protection. protection.
6. IANA Considerations 7. IANA Considerations
This document provides general protocol independent information This document provides general protocol independent information
encodings. There is no IANA allocation request for the TLVs defined encodings. There is no IANA allocation request for the TLVs defined
in this document. IANA allocation requests will be addressed in in this document. IANA allocation requests will be addressed in
protocol specific documents based on the encodings defined here. protocol specific documents based on the encodings defined here.
7. Acknowledgments 8. Acknowledgments
This document was prepared using 2-Word-v2.0.template.dot. This document was prepared using 2-Word-v2.0.template.dot.
APPENDIX A: Encoding Examples APPENDIX A: Encoding Examples
A.1. Wavelength Converter Accessibility Sub-TLV A.1. Wavelength Converter Accessibility Sub-TLV
Example: Example:
Figure 1 shows a wavelength converter pool architecture know as Figure 1 shows a wavelength converter pool architecture know as
skipping to change at page 31, line 5 skipping to change at page 32, line 5
| Ingress Link Set Field A #1 | | Ingress Link Set Field A #1 |
: (All ingress links connect to resource) : : (All ingress links connect to resource) :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB Set Field A #1 | | RB Set Field A #1 |
: (trivial set only one resource block) : : (trivial set only one resource block) :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Egress Link Set Field B #1 | | Egress Link Set Field B #1 |
: (All egress links connect to resource) : : (All egress links connect to resource) :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
8. References 9. References
8.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Structure of Management Information Version 2 (SMIv2)", "Structure of Management Information Version 2 (SMIv2)",
STD 58, RFC 2578, April 1999. STD 58, RFC 2578, April 1999.
[RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Functional Description", RFC 3471, (GMPLS) Signaling Functional Description", RFC 3471,
January 2003. January 2003.
[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.
[G.694.1] ITU-T Recommendation G.694.1, "Spectral grids for WDM [G.694.1] ITU-T Recommendation G.694.1, "Spectral grids for WDM
applications: DWDM frequency grid", June, 2002. applications: DWDM frequency grid", June, 2002.
8.2. Informative References 9.2. Informative References
[G.694.1] ITU-T Recommendation G.694.1, Spectral grids for WDM [G.694.1] ITU-T Recommendation G.694.1, Spectral grids for WDM
applications: DWDM frequency grid, June 2002. applications: DWDM frequency grid, June 2002.
[G.694.2] ITU-T Recommendation G.694.2, Spectral grids for WDM [G.694.2] ITU-T Recommendation G.694.2, Spectral grids for WDM
applications: CWDM wavelength grid, December 2003. applications: CWDM wavelength grid, December 2003.
[Gen-Encode] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "General [Gen-Encode] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "General
Network Element Constraint Encoding for GMPLS Controlled Network Element Constraint Encoding for GMPLS Controlled
Networks", work in progress: draft-ietf-ccamp-general- Networks", work in progress: draft-ietf-ccamp-general-
constraint-encode. constraint-encode.
[Otani] T. Otani, H. Guo, K. Miyazaki, D. Caviglia, "Generalized [RFC6205] T. Otani, H. Guo, K. Miyazaki, D. Caviglia, "Generalized
Labels for G.694 Lambda-Switching Capable Label Switching Labels for G.694 Lambda-Switching Capable Label Switching
Routers", work in progress: draft-ietf-ccamp-gmpls-g-694- Routers", RFC 6205, March 2011.
lambda-labels.
[WSON-Frame] Y. Lee, G. Bernstein, W. Imajuku, "Framework for GMPLS [RFC6163] Y. Lee, G. Bernstein, W. Imajuku, "Framework for GMPLS and
and PCE Control of Wavelength Switched Optical Networks", PCE Control of Wavelength Switched Optical Networks", RFC
work in progress: draft-ietf-ccamp-wavelength-switched- 6163, April 2011.
framework.
[WSON-Info] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "Routing and [WSON-Info] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "Routing and
Wavelength Assignment Information Model for Wavelength Wavelength Assignment Information Model for Wavelength
Switched Optical Networks", work in progress: draft-ietf- Switched Optical Networks", work in progress: draft-ietf-
ccamp-rwa-info. ccamp-rwa-info, March 2009.
9. Contributors 10. 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
 End of changes. 58 change blocks. 
117 lines changed or deleted 162 lines changed or added

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