draft-ietf-ccamp-rwa-wson-encode-21.txt   draft-ietf-ccamp-rwa-wson-encode-22.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: March 2014 D. Li Expires: May 2014 D. Li
Huawei Huawei
W. Imajuku W. Imajuku
NTT NTT
September 30, 2013 November 12, 2013
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-21.txt draft-ietf-ccamp-rwa-wson-encode-22.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with This Internet-Draft is submitted to IETF in full conformance with
the provisions of BCP 78 and BCP 79. the 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
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference 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 30, 2013. This Internet-Draft will expire on May 12, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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 43 skipping to change at page 2, line 43
information to a path computation element (PCE). information to a path computation element (PCE).
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119 [RFC2119]. document are to be interpreted as described in RFC-2119 [RFC2119].
Table of Contents Table of Contents
1. Introduction...................................................4 1. Introduction...................................................3
1.1. Revision History..........................................4 1. Terminology....................................................4
1.1.1. Changes from 00 draft................................4 2. Resources, Resource Blocks, and the Resource Pool..............4
1.1.2. Changes from 01 draft................................5 2.1. Resource Block Set Field..................................5
1.1.3. Changes from 02 draft................................5 3. Resource Accessibility/Availability............................6
1.1.4. Changes from 03 draft................................5 3.1. Resource Accessibility Field..............................6
1.1.5. Changes from 04 draft................................5 3.2. Resource Wavelength Constraints Field.....................8
1.1.6. Changes from 05 draft................................5 3.3. Resource Block Pool State (RBPoolState) Field............10
1.1.7. Changes from 06 draft................................6 3.4. Resource Block Shared Access Wavelength Availability
1.1.8. Changes from 07 draft................................6 (RBSharedAccessWaveAvailability) Field........................11
1.1.9. Changes from 08 draft................................6 4. Resource Signal Constraints and Processing Capabilities.......13
1.1.10. Changes from 09 draft...............................6 4.1. Resource Block Information (ResourceBlockInfo) Field.....13
1.1.11. Changes from 10 draft...............................6 4.2. Shared Input or Output Indication........................14
1.1.12. Changes from 11 draft...............................6 4.3. Optical Interface Class List(s) Sub-Sub-TLV..............14
1.1.13. Changes from 12 draft...............................6 4.3.1. Optical Interface Class Format......................15
1.1.14. Changes from 13 draft...............................7 4.3.2. ITU-G.698.1 Application Code Mapping................16
1.1.15. Changes from 14 draft...............................7 4.3.3. ITU-G.698.2 Application Code Mapping................18
1.1.16. Changes from 15 draft...............................7 4.3.4. ITU-G.959.1 Application Code Mapping................19
1.1.17. Changes from 16 draft...............................7 4.3.5. ITU-G.695 Application Code Mapping..................21
1.1.18. Changes from 17 draft...............................7 4.4. Acceptable Client Signal List Sub-Sub-TLV................23
1.1.19. Changes from 18 draft...............................7 4.5. Input Bit Rate List Sub-Sub-TLV..........................24
1.1.20. Changes from 19 draft...............................7 4.6. Processing Capability List Sub-Sub-TLV...................24
1.1.21. Changes from 20 draft...............................8 4.6.1. Processing Capabilities Field.......................25
1. Terminology....................................................8 5. Security Considerations.......................................26
2. Resources, Blocks, Sets, and the Resource Pool.................8 6. IANA Considerations...........................................26
2.1. Resource Block Set Field..................................9 7. Acknowledgments...............................................26
3. Resource Pool Accessibility/Availability......................10 APPENDIX A: Encoding Examples....................................27
3.1. Resource Pool Accessibility Sub-TLV......................11 A.1. Wavelength Converter Accessibility Sub-TLV...............27
3.2. Resource Block Wavelength Constraints Sub-TLV............12 A.2. Wavelength Conversion Range Sub-TLV......................28
3.3. Resource Pool State Sub-TLV..............................14 A.3. An OEO Switch with DWDM Optics...........................29
3.4. Block Shared Access Wavelength Availability sub-TLV......15 8. References....................................................32
4. Resource Properties Encoding..................................16 8.1. Normative References.....................................32
4.1. Resource Block Information Sub-TLV.......................17 8.2. Informative References...................................32
4.2. Optical Interface Class List(s) Sub-Sub-TLV..............17 9. Contributors..................................................34
4.2.1. Optical Interface Class Format......................18 Authors' Addresses...............................................35
4.2.2. ITU-G.698.1 Application Code Mapping................19 Intellectual Property Statement..................................36
4.2.3. ITU-G.698.2 Application Code Mapping................21 Disclaimer of Validity...........................................37
4.2.4. ITU-G.959.1 Application Code Mapping................22
4.2.5. ITU-G.695 Application Code Mapping..................24
4.3. Input Client Signal List Sub-Sub-TLV.....................26
4.4. Input Bit Rate List Sub-Sub-TLV..........................27
4.5. Processing Capability List Sub-Sub-TLV...................27
4.5.1. Processing Capabilities Field.......................28
5. Security Considerations.......................................29
6. IANA Considerations...........................................29
7. Acknowledgments...............................................29
APPENDIX A: Encoding Examples....................................30
A.1. Wavelength Converter Accessibility Sub-TLV...............30
A.2. Wavelength Conversion Range Sub-TLV......................31
A.3. An OEO Switch with DWDM Optics...........................32
8. References....................................................35
8.1. Normative References.....................................35
8.2. Informative References...................................35
9. Contributors..................................................37
Authors' Addresses...............................................38
Intellectual Property Statement..................................39
Disclaimer of Validity...........................................40
1. Introduction 1. Introduction
A Wavelength Switched Optical Network (WSON) is a Wavelength A Wavelength Switched Optical Network (WSON) is a Wavelength
Division Multiplexing (WDM) optical network in which switching is Division Multiplexing (WDM) optical network in which switching is
performed selectively based on the center wavelength of an optical performed selectively based on the center wavelength of an optical
signal. signal.
[RFC6163] describes a framework for Generalized Multiprotocol Label [RFC6163] describes a framework for Generalized Multiprotocol Label
Switching (GMPLS) and Path Computation Element (PCE) control of a Switching (GMPLS) and Path Computation Element (PCE) control of a
WSON. Based on this framework, [WSON-Info] describes an information WSON. Based on this framework, [RWA-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
efficient they can provide more accurate analysis of the control efficient they can provide more accurate analysis of the control
plane communications/processing load for WSONs looking to utilize a plane communications/processing load for WSONs looking to utilize a
GMPLS control plane. GMPLS control plane.
Note that encodings of information needed by the routing and label
assignment process applicable to general networks beyond WSON are
addressed in a separate document [Gen-Encode]. This document makes
use of the Label Set Field encoding of [Gen-Encode] and refers to it
as a Wavelength Set Field.
1.1. Revision History
1.1.1. Changes from 00 draft
Edits to make consistent with update to [RFC6205], i.e., removal of
sign bit.
Clarification of TBD on connection matrix type and possibly
numbering.
New sections for wavelength converter pool encoding: Wavelength
Converter Set Sub-TLV, Wavelength Converter Accessibility Sub-TLV,
Wavelength Conversion Range Sub-TLV, WC Usage State Sub-TLV.
Added optional wavelength converter pool TLVs to the composite node
TLV.
1.1.2. Changes from 01 draft
The encoding examples have been moved to an appendix. Classified and
corrected information elements as either reusable fields or sub-
TLVs. Updated Port Wavelength Restriction sub-TLV. Added available
wavelength and shared backup wavelength sub-TLVs. Changed the title
and scope of section 6 to recommendations since the higher level
TLVs that this encoding will be used in is somewhat protocol
specific.
1.1.3. Changes from 02 draft
Removed inconsistent text concerning link local identifiers and the
link set field.
Added E bit to the Wavelength Converter Set Field.
Added bidirectional connectivity matrix example. Added simple link
set example. Edited examples for consistency.
1.1.4. Changes from 03 draft
Removed encodings for general concepts to [Gen-Encode].
Added in WSON signal compatibility and processing capability
information encoding.
1.1.5. Changes from 04 draft
Added encodings to deal with access to resource blocks via shared
fiber.
1.1.6. Changes from 05 draft
Revised the encoding for the "shared access" indicators to only use
one bit each for input and output.
1.1.7. Changes from 06 draft
Removed section on "WSON Encoding Usage Recommendations"
1.1.8. Changes from 07 draft
Section 3: Enhanced text to clarify relationship between pools,
blocks and resources. Section 3.1, 3.2: Change title to clarify
Pool-Block relationship. Section 3.3: clarify block-resource state.
Section 4: Deleted reference to previously removed RBNF element.
Fixed TLV figures and descriptions for consistent sub-sub-TLV
nomenclature.
1.1.9. Changes from 08 draft
Fixed ordering of fields in second half of sub-TLV example in
Appendix A.1.
Clarifying edits in section 3 on pools, blocks, and resources.
1.1.10. Changes from 09 draft
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.
Removed all 1st person idioms.
1.1.11. Changes from 10 draft
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.
1.1.13. Changes from 12 draft
Replaced all instances of "ingress" with "input" and all instances
of "egress" with "output".
1.1.14. Changes from 13 draft
C bit of Resource Block Set Field is redundant and was removed,
i.e., has been returned to "Reserved" block and appendix examples
were updated to reflect the change.
Enhanced section 4.2 encoding to allow for optionality of input or
output wavelength set fields.
Clarified that wavelength set fields use the Label Set field
encoding from [Gen-Encode].
Enhanced section 5.1 encoding to simplify the Modulation and FEC
input and output cases.
1.1.15. Changes from 14 draft
OIC changes per workgroup request. Removed FEC type and modulation
type. Fixed versioning error and return RB identifiers to 32 bits.
1.1.16. Changes from 15 draft
Edits of OIC related text per CCAMP list email.
1.1.17. Changes from 16 draft
Added full ITU-T string to 64 bit mapping to text from OIC draft.
1.1.18. Changes from 17 draft
Action value for Inclusive Range(s) changed to 1 from 2 for the
Resource Block Set Field encoding in Section 3.1.
Added a list of contributors who provided texts for the Optical
Interface Class (OIC) description.
1.1.19. Changes from 18 draft
Added Section 5.2.5 to include ITU-G.695 Application Code Mapping.
1.1.20. Changes from 19 draft
Added the definition and encoding of Input Bit Rate List Sub-Sub-TLV
in Section 4.4.
1.1.21. Changes from 20 draft
Revived the expired version with no change of content.
1. Terminology 1. Terminology
CWDM: Coarse Wavelength Division Multiplexing. Refer to [RFC6163] for CWDM, DWDM, RWA, WDM.
DWDM: Dense Wavelength Division Multiplexing.
FOADM: Fixed Optical Add/Drop Multiplexer.
ROADM: Reconfigurable Optical Add/Drop Multiplexer. A reduced port
count wavelength selective switching element featuring input and
output line side ports as well as add/drop side ports.
RWA: Routing and Wavelength Assignment.
Wavelength Conversion. The process of converting an information
bearing optical signal centered at a given wavelength to one with
"equivalent" content centered at a different wavelength. Wavelength
conversion can be implemented via an optical-electronic-optical
(OEO) process or via a strictly optical process.
WDM: Wavelength Division Multiplexing.
Wavelength Switched Optical Network (WSON): A WDM based optical
network in which switching is performed selectively based on the
center wavelength of an optical signal.
2. Resources, Blocks, Sets, and the Resource Pool Refer to Section 5 of [Gen-Encode] for the terminology of Resources,
Resources Blocks, and Resource Pool.
The optical system to be encoded may contain a pool of resources of 2. Resources, Resource Blocks, and the Resource Pool
different types and properties for processing optical signals. For
the purposes here a "resource" is an individual entity such as a
wavelength converter or regenerator within the optical node that
acts on an individual wavelength signal.
Since resources tend to be packaged together in blocks of similar This section provides encodings for the information elements defined
devices, e.g., on line cards or other types of modules, the in [RWA-INFO] that have applicability to WSON. The encodings are
fundamental unit of identifiable resource in this document is the designed to be suitable for use in the GMPLS routing protocols OSPF
"resource block". A resource block may contain one or more [RFC4203] and IS-IS [RFC5307] and in the PCE protocol (PCEP)
resources. As resource blocks are the smallest identifiable unit of [RFC5440]. Note that the information distributed in [RFC4203] and
processing resource, one should group together resources into blocks [RFC5307] is arranged via the nesting of sub-TLVs within TLVs and
if they have similar characteristics relevant to the optical system this document defines elements to be used within such constructs.
being modeled, e.g., processing properties, accessibility, etc.
This document defines the following sub-TLVs pertaining to resources This document defines the following information elements pertaining
within an optical node: to resources within an optical node:
. Resource Pool Accessibility Sub-TLV . Resource Accessibility <ResourceAccessibility>
. Resource Block Wavelength Constraints Sub-TLV . Resource Wavelength Constraints <ResourceWaveConstraints>
. Resource Pool State Sub-TLV . Resource Block Pool State <RBPoolState>
. Block Shared Access Wavelength Availability Sub-TLV . Resource Block Shared Access Wavelength Availability
<RBSharedAccessWaveAvailability>
. Resource Block Information Sub-TLV . Resource Block Information <ResourceBlockInfo>
Each of these sub-TLVs works with one or more sets of resources Each of these information elements works with one or more sets of
rather than just a single resource block. This motivates the resources rather than just a single resource block. This motivates
following field definition. the following field definition.
2.1. Resource Block Set Field 2.1. Resource Block Set Field
In a WSON node that includes resource blocks (RB), denoting subsets In a WSON node that includes resource blocks (RB), denoting subsets
of these blocks allows one to efficiently describe common properties of these blocks allows one to efficiently describe common properties
of the blocks and to describe the structure and characteristics, if of the blocks and to describe the structure and characteristics, if
non-trivial, of the resource pool. The RB Set field is defined in a non-trivial, of the resource pool. The RB Set field is defined in a
similar manner to the label set concept of [RFC3471]. 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:
skipping to change at page 10, line 19 skipping to change at page 6, line 4
1 - Inclusive Range(s) 1 - Inclusive Range(s)
Indicates that the TLV contains one or more ranges of RBs. Each Indicates that the TLV contains one or more ranges of RBs. Each
individual range is denoted by two 32 bit RB identifier. The first individual range is denoted by two 32 bit RB identifier. The first
32 bits is the RB identifier for the start of the range and the next 32 bits is the RB identifier for the start of the range and the next
32 bits is the RB identifier for the end of the range. Note that the 32 bits is the RB identifier for the end of the range. Note that the
Length field is used to determine the number of ranges. Length field is used to determine the number of ranges.
C (Connectivity bit): Set to 0 to denote fixed (possibly multi- C (Connectivity bit): Set to 0 to denote fixed (possibly multi-
cast) connectivity; Set to 1 to denote potential (switched) cast) connectivity; Set to 1 to denote potential (switched)
connectivity. Used in resource pool accessibility sub-TLV. Ignored connectivity. Used in Resource Accessibility sub-TLV. Ignored
elsewhere. elsewhere.
Reserved: 7 bits Reserved: 7 bits
This field is reserved. It MUST be set to zero on transmission and This field is reserved. It MUST be set to zero on transmission and
MUST be ignored on receipt. MUST be ignored on receipt.
Length: 16 bits Length: 16 bits
The total length of this field in bytes. The total length of this field in bytes.
skipping to change at page 10, line 41 skipping to change at page 6, line 26
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
32 bit integer. 32 bit integer.
Usage Note: the inclusive range "Action" can result in very compact Usage Note: the inclusive range "Action" can result in very compact
encoding of resource sets and it can be advantages to number encoding of resource sets and it can be advantages to number
resource blocks in such a way so that status updates (dynamic resource blocks in such a way so that status updates (dynamic
information) can take advantage of this efficiency. information) can take advantage of this efficiency.
3. Resource Pool Accessibility/Availability 3. Resource Accessibility/Availability
This section defines the sub-TLVs for dealing with accessibility and This section defines the information elements for dealing with
availability of resource blocks within a pool of resources. These accessibility and availability of resource blocks within a pool of
include the ResourceBlockAccessibility, ResourceWaveConstraints, and resources. These include the ResourceAccessibility,
RBPoolState sub-TLVs. ResourceWaveConstraints, and RBPoolState fields.
3.1. Resource Pool Accessibility Sub-TLV 3.1. Resource Accessibility Field
This sub-TLV describes the structure of the resource pool in This information element describes the structure of the resource
relation to the switching device. In particular it indicates the pool in relation to the switching device. In particular it indicates
ability of an input port to reach sets of resources and of a sets of the ability of an input port to reach sets of resources and of sets
resources to reach a particular output port. This is the of resources to reach a particular output port. This is the
PoolInputMatrix and PoolOutputMatrix of [WSON-Info]. PoolInputMatrix and PoolOutputMatrix of [RWA-Info].
The resource pool accessibility sub-TLV is defined by: The Resource Accessibility 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 | | Reserved |C| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Link Set Field A #1 | | Input Link Set Field A #1 |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB Set Field A #1 | | RB Set Field A #1 |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Additional Link set and RB set pairs as needed to | | Additional Link set and RB set pairs as needed to |
: specify PoolInputMatrix : : specify PoolInputMatrix :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 11, line 41 skipping to change at page 7, line 31
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB Set B Field #1 (for output connectivity) | | RB Set B Field #1 (for output connectivity) |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Additional Link Set and RB set pairs as needed to | | Additional Link Set and RB set pairs as needed to |
: specify PoolOutputMatrix : : specify PoolOutputMatrix :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where Where
Connectivity indicates how the input/output ports connect to the C (Connectivity bit): Connectivity indicates how the input/output
resource blocks. ports connect to the resource blocks.
0 -- the device is fixed (e.g., a connected port must go 0 -- the device is fixed (e.g., a connected port must go
through the resource block) through the resource block)
1 -- the device is switched (e.g., a port can be configured to 1 -- the device is switched (e.g., a port can be configured to
go through a resource but isn't required) go through a resource but isn't required)
The For the Input and Output Link Set Fields, the Link Set Field The For the Input and Output Link Set Fields, the Link Set Field
encoding defined in [Gen-Encode] is to be used. encoding defined in [Gen-Encode] is to be used. A Label Set Field
MUST carry a label as defined in [RFC6205].
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 input or output link set, and to indicate whether the link set is an input or output link set, and
the bidirectional value for this parameter is not permitted in this the bidirectional value for this parameter is not permitted in this
sub-TLV. 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 3.2. Resource Wavelength Constraints Field
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 input or output wavelength ranges. Additionally, due to the
structure of the optical system not all wavelengths can necessarily structure of the optical system not all wavelengths can necessarily
reach or leave all the resources. These properties are described by reach or leave all the resources. These properties are described by
using one or more resource wavelength restrictions sub-TLVs as using one or more resource wavelength restrictions fields as defined
defined below: 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I|O|B| Reserved | |I|O|B| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB Set Field | | RB Set Field |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Wavelength Set Field | | Input Wavelength Constraints |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Wavelength Set Field | | Output Wavelength Constraints |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
I = 1 or 0 indicates the presence or absence of the Input Wavelength I = 1 or 0 indicates the presence or absence of the Input Wavelength
Set Field. Constraints Field.
O = 1 or 0 indicates the presence or absence of the Output O = 1 or 0 indicates the presence or absence of the Output
Wavelength Set Field. Wavelength Constraints Field.
B = 1 indicates that a single wavelength set field represents both B = 1 indicates that a single wavelength constraints field
input and output wavelength constraints. represents both Input and Output Wavelength Constraints Fields.
Currently the only valid combinations of (I,O,B) are (1,0,0), Currently the only valid combinations of (I,O,B) are (1,0,0),
(0,1,0), (1,1,0), (0,0,1). (0,1,0), (1,1,0), (0,0,1).
RB Set Field: RB Set Field:
A set of resource blocks (RBs) which have the same wavelength A set of resource blocks (RBs) which have the same wavelength
restrictions. restrictions.
Input Wavelength Set Field: Input Wavelength Constraints Field:
Indicates the wavelength input restrictions of the RBs in the Indicates the wavelength input restrictions of the RBs in the
corresponding RB set. This field is encoded via the Label Set field corresponding RB set. This field is encoded via the Label Set field
of [Gen-Encode]. of [Gen-Encode].
Output Wavelength Set Field: Output Wavelength Constraints Field:
Indicates the wavelength output restrictions of RBs in the Indicates the wavelength output restrictions of RBs in the
corresponding RB set. This field is encoded via the Label Set field corresponding RB set. This field is encoded via the Label Set field
of [Gen-Encode]. of [Gen-Encode].
3.3. Resource Pool State Sub-TLV 3.3. Resource Block Pool State (RBPoolState) Field
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
with particular characteristics. A resource block set is used to with particular characteristics. A resource block set is used to
encode all or a subset of the resources of interest. The usage state encode all or a subset of the resources of interest. The usage state
of resources within a resource block set is encoded as either a list of resources within a resource block set is encoded as either a list
of 16 bit integer values or a bit map indicating whether a single of 16 bit integer values or a bit map indicating whether a single
resource is available or in use. The bit map encoding is appropriate resource is available or in use. The bit map encoding is appropriate
when resource blocks consist of a single resource. This information when resource blocks consist of a single resource. This information
can be relatively dynamic, i.e., can change when a connection (LSP can be relatively dynamic, i.e., can change when a connection (LSP
is established or torn down. is established or torn down.
skipping to change at page 15, line 23 skipping to change at page 11, line 23
| RB Usage state bitmap | | RB Usage state bitmap |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ...... | Padding bits | | ...... | Padding bits |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
TLV. element.
Padding bits: Variable Length Padding bits: Variable Length
3.4. Block Shared Access Wavelength Availability sub-TLV 3.4. Resource Block Shared Access Wavelength Availability
(RBSharedAccessWaveAvailability) Field
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 case, then wavelength availability on these shared fibers is needed
to 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|O| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB Set Field | | RB Set Field |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Available Wavelength Set Field | | Input Available Wavelength Set Field |
: (Optional) : : (Optional) :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Available Wavelength Set Field | | Output Available Wavelength Set Field |
: (Optional) : : (Optional) :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 16, line 4 skipping to change at page 12, line 19
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB Set Field | | RB Set Field |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Available Wavelength Set Field | | Input Available Wavelength Set Field |
: (Optional) : : (Optional) :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Available Wavelength Set Field | | Output Available Wavelength Set Field |
: (Optional) : : (Optional) :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
I bit: I bit:
Indicates whether the input available wavelength set field is Indicates whether the input available wavelength set field is
included (1) or not (0). included (1) or not (0).
E bit: O bit:
Indicates whether the output available wavelength set field is Indicates whether the output available wavelength set field is
included (1) or not (0). included (1) or not (0).
RB Set Field: RB Set Field:
A Resource Block set in which all the members share the same input A Resource Block set in which all the members share the same input
or output fiber or both. or output fiber or both.
Input Available Wavelength Set Field: Input Available Wavelength Set Field:
skipping to change at page 16, line 31 skipping to change at page 13, line 5
Indicates the wavelengths currently available (not being used) on Indicates the wavelengths currently available (not being used) on
the input fiber to this resource block. This field is encoded via the input fiber to this resource block. This field is encoded via
the Label Set field of [Gen-Encode]. the Label Set field of [Gen-Encode].
Output Available Wavelength Set Field: Output Available Wavelength Set Field:
Indicates the wavelengths currently available (not being used) on Indicates the wavelengths currently available (not being used) on
the output fiber from this resource block. This field is encoded via the output fiber from this resource block. This field is encoded via
the Label Set field of [Gen-Encode]. the Label Set field of [Gen-Encode].
4. Resource Properties Encoding 4. Resource Signal Constraints and Processing Capabilities
Within a WSON network element (NE) there may be resources with Within a WSON network element (NE) there may be resources with
signal compatibility constraints. These resources be regenerators, signal compatibility constraints. These resources be regenerators,
wavelength converters, etc... Such resources may also constitute the wavelength converters, etc... Such resources may also constitute the
network element as a whole as in the case of an electro optical network element as a whole as in the case of an electro optical
switch. This section primarily focuses on the signal compatibility switch. This section primarily focuses on the signal compatibility
and processing properties of such a resource block. and processing properties of such a resource block.
The fundamental properties of a resource block, such as a The fundamental properties of a resource block, such as a
regenerator or wavelength converter, are: regenerator or wavelength converter, are:
(a) Input constraints (shared input, modulation, FEC, bit rate, (a) Optical Interface Class List(s)
GPID) (b) Acceptable Client Signal (shared input, modulation, FEC, bit
rate, G-PID)
(b) Processing capabilities (number of resources in a block, (c) Input Bit Rate
(d) Processing Capabilities (number of resources in a block,
regeneration, performance monitoring, vendor specific) regeneration, performance monitoring, vendor specific)
(c) Output Constraints (shared output, modulation, FEC) 4.1. Resource Block Information (ResourceBlockInfo) Field
4.1. Resource Block Information Sub-TLV
Resource Block descriptor sub-TLVs are used to convey relatively Resource Block information fields are used to convey relatively
static information about individual resource blocks including the static information about individual resource blocks including the
resource block compatibility properties, processing properties, and resource block compatibility properties, processing properties, and
the number of resources in a block. the number of resources in a block.
This sub-TLV has the following format: There can be more than one Resource Block field as resources are
packaged together in blocks of similar devices and its
characteristics.
This field 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|O| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Optical Interface Class List(s) Sub-Sub-TLV (opt) | | Optical Interface Class List(s) Sub-Sub-TLV (opt) |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Client Signal Type Sub-Sub-TLV (opt) | | Acceptable Client Signal Type Sub-Sub-TLV (opt) |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Bit Rate List Sub-Sub-TLV (opt) | | Input Bit Rate List Sub-Sub-TLV (opt) |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Processing Capabilities List Sub-Sub-TLV (opt) | | Processing Capabilities List Sub-Sub-TLV (opt) |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where I and E, the shared input/output indicator, is set to 1 if the RB Set Field is described in Section 2.1.
resource blocks identified in the RB set field utilized a shared
fiber for input/output access and set to 0 otherwise.
4.2. Optical Interface Class List(s) Sub-Sub-TLV 4.2. Shared Input or Output Indication
The shared input or output indication is indicated by the first bit
(I) and the second bit (O):
where I and O are set to 1 if the resource blocks identified in the
RB set field utilized a shared fiber for input/output access and set
to 0 otherwise.
4.3. Optical Interface Class List(s) Sub-Sub-TLV
The list of Optical Interface Class sub-sub-TLV has the following The list of Optical Interface Class sub-sub-TLV has the following
format: 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved |I|E| | Type | Length | Reserved |I|E|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Optical Interface Classes | | Optical Interface Classes |
skipping to change at page 18, line 30 skipping to change at page 15, line 30
1 0 Optical Interface Class List acceptable in input 1 0 Optical Interface Class List acceptable in input
0 1 Optical Interface Class List available in output 0 1 Optical Interface Class List available in output
1 1 Optical Interface Class List available on both input and 1 1 Optical Interface Class List available on both input and
output. output.
The Resource Block MAY contain one or more lists according to The Resource Block MAY contain one or more lists according to
input/output flags. input/output flags.
4.2.1. Optical Interface Class Format 4.3.1. Optical Interface Class 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|S| Reserved | OI Code Points | |S| Reserved | OI Code Points |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Optical Interface Class | | Optical Interface Class |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Optical Interface Class (Cont.) | | Optical Interface Class (Cont.) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 19, line 29 skipping to change at page 16, line 29
values: values:
0: reserved 0: reserved
1: [ITU-G.698.1] application code. 1: [ITU-G.698.1] application code.
2: [ITU-G.698.2] application code. 2: [ITU-G.698.2] application code.
3: [ITU-G.959.1] application code. 3: [ITU-G.959.1] application code.
4: [ITU-G.695.1] application code. 4: [ITU-G.695] application code.
In case of ITU Application Code, the mapping between the string In case of ITU Application Code, the mapping between the string
defining the application code and the 64 bits number implementing defining the application code and the 64 bits number implementing
the optical interface class is given in the following sections. the optical interface class is given in the following sections.
4.2.2. ITU-G.698.1 Application Code Mapping 4.3.2. ITU-G.698.1 Application Code Mapping
Recommendation ITU-G.698.1 defines the Application Codes: DScW- Recommendation ITU-G.698.1 defines the Application Codes: DScW-
ytz(v) and B-DScW-ytz(v). Where: ytz(v) and B-DScW-ytz(v). Where:
B: means Bidirectionals. B: means Bidirectionals.
D: means a DWDM application. D: means a DWDM application.
S: take values N (narrow spectral excursion), W (wide spectral S: take values N (narrow spectral excursion), W (wide spectral
excursion). excursion).
skipping to change at page 20, line 23 skipping to change at page 17, line 23
v: take values S (Short wavelength), C (Conventional), L (Long v: take values S (Short wavelength), C (Conventional), L (Long
wavelength). wavelength).
An Optional F can be added indicating a FEC Encoding. An Optional F can be added indicating a FEC Encoding.
These get mapped into the 64 bit OIC field as follows: These get mapped into the 64 bit OIC field as follows:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|B| p |S| c | W | y | t | z | v | s | |B| D |S| c | W | y | t | z | v | F |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| reserved | | reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where (values between parenthesis refer to ITU defined values as Where (values between parenthesis refer to ITU defined values as
reported above): reported above):
B: = 1 bidirectional, 0 otherwise B: = 1 bidirectional, 0 otherwise
p (prefix): = 0 reserved, = 1 (D) D (prefix): = 0 reserved, = 1 (D)
S: = 0 (N), = 1 (W) S: = 0 (N), = 1 (W)
c: Channel Spacing, 4 bits mapped according to same definition c: Channel Spacing, 4 bits mapped according to same definition
in [RFC6205] (note that DWDM spacing apply here) in [RFC6205] (note that DWDM spacing apply here)
W: = 0 reserved, = 2 (S), = 3 (L) W: = 0 reserved, = 2 (S), = 3 (L)
y: = 0 reserved, = 1 (1), = 2 (2) y: = 0 reserved, = 1 (1), = 2 (2)
t: = 0 reserved, = 4 (D) t: = 0 reserved, = 4 (D)
z: = 0 reserved, = 2 (2), = 3 (3), = 5 (5) z: = 0 reserved, = 2 (2), = 3 (3), = 5 (5)
v: = 0 reserved, = 1 (S), = 2 (C), = 3 (L) v: = 0 reserved, = 1 (S), = 2 (C), = 3 (L)
s (suffix): = 0 reserved, = 1 Fec Encoding F (suffix): = 0 reserved, = 1 Fec Encoding
Values not mentioned here are not allowed in this application Values not mentioned here are not allowed in this application
code, the last 32 bits are reserved and shall be set to zero. code, the last 32 bits are reserved and shall be set to zero.
4.2.3. ITU-G.698.2 Application Code Mapping 4.3.3. ITU-G.698.2 Application Code Mapping
Recommendation ITU-G.698.2 defines the Application Codes: DScW- Recommendation ITU-G.698.2 defines the Application Codes: DScW-
ytz(v) and B-DScW-ytz(v). ytz(v) and B-DScW-ytz(v).
B: means Bidirectional. B: means Bidirectional.
D: means a DWDM application. D: means a DWDM application.
S: take values N (narrow spectral excursion), W (wide spectral S: take values N (narrow spectral excursion), W (wide spectral
excursion). excursion).
skipping to change at page 21, line 45 skipping to change at page 18, line 45
v: take values S (Short wavelength), C (Conventional), L (Long v: take values S (Short wavelength), C (Conventional), L (Long
wavelength). wavelength).
An Optional F can be added indicating a FEC Encoding. An Optional F can be added indicating a FEC Encoding.
These get mapped into the 64 bit OIC field as follows: These get mapped into the 64 bit OIC field as follows:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|B| p |S| c | W | y | t | z | v | s | |B| D |S| c | W | y | t | z | v | F |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| reserved | | reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where (values between parenthesis refer to ITU defined values as Where (values between parenthesis refer to ITU defined values as
reported above): reported above):
B: = 1 bidirectional, 0 otherwise B: = 1 bidirectional, 0 otherwise
p (prefix): = 0 reserved, = 1 (D) D (prefix): = 0 reserved, = 1 (D)
S: = 0 (N), = 1 (W) S: = 0 (N), = 1 (W)
c: Channel Spacing, 4 bits mapped according to same definition c: Channel Spacing, 4 bits mapped according to same definition
in [RFC6205] (note that DWDM spacing apply here) in [RFC6205] (note that DWDM spacing apply here)
W: = 0 reserved, = 10 (C), = 11 (U) W: = 0 reserved, = 10 (C), = 11 (U)
y: = 0 reserved, = 1 (1), = 2 (2) y: = 0 reserved, = 1 (1), = 2 (2)
t: = 0 reserved, = 1 (A) t: = 0 reserved, = 1 (A)
z: = 0 reserved, = 2 (2), = 3 (3), = 5 (5) z: = 0 reserved, = 2 (2), = 3 (3), = 5 (5)
v: = 0 reserved, = 1 (S), = 2 (C), = 3 (L) v: = 0 reserved, = 1 (S), = 2 (C), = 3 (L)
s (suffix): = 0 reserved, = 1 Fec Encoding F (suffix): = 0 reserved, = 1 Fec Encoding
Values not mentioned here are not allowed in this application Values not mentioned here are not allowed in this application
code, the last 32 bits are reserved and shall be set to zero. code, the last 32 bits are reserved and shall be set to zero.
4.2.4. ITU-G.959.1 Application Code Mapping 4.3.4. ITU-G.959.1 Application Code Mapping
Recommendation ITU-G.959.1 defines the Application Codes: PnWx-ytz Recommendation ITU-G.959.1 defines the Application Codes: PnWx-ytz
and BnWx-ytz. Where: and BnWx-ytz. Where:
P,B: when present indicate Plural or Bidirectional P,B: when present indicate Plural or Bidirectional
n: maximum number of channels supported by the application code n: maximum number of channels supported by the application code
(i.e. an integer number) (i.e. an integer number)
W: take values I (intra-office), S (short-haul), L (long-haul), V W: take values I (intra-office), S (short-haul), L (long-haul), V
skipping to change at page 24, line 30 skipping to change at page 21, line 30
suffix is an 6 bit, bit map: suffix is an 6 bit, bit map:
0 1 2 3 4 5 0 1 2 3 4 5
+-+-+-+-+-+-+ +-+-+-+-+-+-+
|F|D|E|r|a|b| |F|D|E|r|a|b|
+-+-+-+-+-+-+ +-+-+-+-+-+-+
where a 1 in the appropriate slot indicates that the corresponding where a 1 in the appropriate slot indicates that the corresponding
suffix has been added. suffix has been added.
4.2.5. ITU-G.695 Application Code Mapping 4.3.5. ITU-G.695 Application Code Mapping
Recommendation [ITU-G.695] defines the Application Codes: CnWx-ytz Recommendation [ITU-G.695] defines the Application Codes: CnWx-ytz
and B-CnWx-ytz and S-CnWx-ytz. and B-CnWx-ytz and S-CnWx-ytz.
Where the optional prefixed are: Where the optional prefixed are:
B: Bidirectional B: Bidirectional
S: a system using a black link approach S: a system using a black link approach
skipping to change at page 26, line 26 skipping to change at page 23, line 26
suffix is an 6 bit, bit map: suffix is an 6 bit, bit map:
0 1 2 3 4 5 0 1 2 3 4 5
+-+-+-+-+-+-+ +-+-+-+-+-+-+
|F|0|0|0|0|0| |F|0|0|0|0|0|
+-+-+-+-+-+-+ +-+-+-+-+-+-+
where a 1 in the appropriate slot indicates that the corresponding where a 1 in the appropriate slot indicates that the corresponding
suffix has been added. suffix has been added.
4.3. Input Client Signal List Sub-Sub-TLV 4.4. Acceptable 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 G-PIDs
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 Protocol Identifiers (G-PIDs). G-PIDs are assigned by IANA and many
are defined in [RFC3471] and [RFC4328]. are defined in [RFC3471] and [RFC4328].
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of GPIDs | GPID #1 | | Number of G-PIDs | G-PID #1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: | : : | :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| GPID #N | | | G-PID #N | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where the number of GPIDs is an integer greater than or equal to Where the number of G-PIDs is an integer greater than or equal to
one. one.
4.4. Input Bit Rate List Sub-Sub-TLV 4.5. Input Bit Rate List Sub-Sub-TLV
This sub-sub-TLV contains a list of bit rate of each input client This sub-sub-TLV contains a list of bit rate of each input client
signal types specified in the Input Client Signal List Sub-Sub-TLV. signal types specified in the Input Client Signal List Sub-Sub-TLV.
Type := Input Bit Rate List Type := Input Bit Rate List
Value := IEEE 32-bit IEEE Floating Point Value := IEEE 32-bit IEEE Floating Point
The number of Input Bit Rate MUST match the number of GPID. The number of Input Bit Rate MUST match the number of G-PID.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Bit Rate of GPID #1 | | Input Bit Rate of G-PID #1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Bit Rate of GPID #N | | Input Bit Rate of G-PID #N |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
4.5. Processing Capability List Sub-Sub-TLV 4.6. Processing Capability List Sub-Sub-TLV
This sub-sub-TLV contains a list of resource processing This sub-sub-TLV contains a list of resource 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-sub-TLV is a list of capabilities The processing capability list sub-sub-TLV is a list of capabilities
that can be achieved through the referred resources:: that can be achieved through the referred resources::
1. Regeneration capability 1. Regeneration capability
2. Fault and performance monitoring 2. Fault and performance monitoring
3. Vendor Specific capability 3. 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.5.1. Processing Capabilities Field 4.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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 30, line 27 skipping to change at page 27, line 27
WI =| |, WE =| | WI =| |, WE =| |
| 1 1 | | 0 1 | | 1 1 | | 0 1 |
+-----+ +-----+ +-----+ +-----+
+-----------+ +------+ +-----------+ +------+
| |--------------------->| | | |--------------------->| |
| |--------------------->| C | | |--------------------->| C |
/| | |--------------------->| o | /| | |--------------------->| o |
/D+--->| |--------------------->| m | /D+--->| |--------------------->| m |
+ e+--->| | | b |=======> + e+--->| | | b |=======>
========>| M| | Optical | +-----------+ | i | Port E1 ========>| M| | Optical | +-----------+ | i | Port O1
Port I1 + u+--->| Switch | | WC Pool | | n | Port I1 + u+--->| Switch | | WC Pool | | n |
\x+--->| | | +-----+ | | e | \x+--->| | | +-----+ | | e |
\| | +----+->|WC #1|--+---->| r | \| | +----+->|WC #1|--+---->| r |
| | | +-----+ | +------+ | | | +-----+ | +------+
| | | | +------+ | | | | +------+
/| | | | +-----+ | | | /| | | | +-----+ | | |
/D+--->| +----+->|WC #2|--+---->| C | /D+--->| +----+->|WC #2|--+---->| C |
+ e+--->| | | +-----+ | | o | + e+--->| | | +-----+ | | o |
========>| M| | | +-----------+ | m |=======> ========>| M| | | +-----------+ | m |=======>
Port I2 + u+--->| | | b | Port E2 Port I2 + u+--->| | | b | Port O2
\x+--->| |--------------------->| i | \x+--->| |--------------------->| i |
\| | |--------------------->| n | \| | |--------------------->| n |
| |--------------------->| e | | |--------------------->| e |
| |--------------------->| r | | |--------------------->| r |
+-----------+ +------+ +-----------+ +------+
Figure 1 An optical switch featuring a shared per fiber wavelength Figure 1 An optical switch featuring a shared per fiber wavelength
converter pool architecture. converter pool architecture.
This wavelength converter pool can be encoded as follows: This wavelength converter pool can be encoded as follows:
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=1| Reserved | | Reserved |1| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: I1,I2 can connect to either WC1 or WC2 Note: I1,I2 can connect to either WC1 or WC2
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Action=0 |0| Reserved | Length = 12 | | Action=0 |0| Reserved | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link Local Identifier = #1 | | Link Local Identifier = #1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link Local Identifier = #2 | | Link Local Identifier = #2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Action=0 |1| Reserved | Length = 8 | | Action=0 |1| Reserved | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB ID = #1 | | RB ID = #1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB ID = #2 | | RB ID = #2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: WC1 can only connect to E1 Note: WC1 can only connect to O1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Action=0 |1| Reserved | Length = 8 | | Action=0 |1| Reserved | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link Local Identifier = #1 | | Link Local Identifier = #1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Action=0 |0| Reserved | Length = 8 | | Action=0 |0| Reserved | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB ID = #1 | | RB ID = #1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: WC2 can only connect to E2 Note: WC2 can only connect to O2
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Action=0 |1| Reserved | Length = 8 | | Action=0 |1| Reserved | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link Local Identifier = #2 | | Link Local Identifier = #2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Action=0 |0| | Length = 8 | | Action=0 |0| | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB ID = #2 | | RB ID = #2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 32, line 49 skipping to change at page 29, line 49
TLVs][<ConnectivityMatrix>...] [<ResourcePool>][<RBPoolState>] TLVs][<ConnectivityMatrix>...] [<ResourcePool>][<RBPoolState>]
In this case there is complete port to port connectivity so the In this case there is complete port to port connectivity so the
<ConnectivityMatrix> is not required. In addition since there are <ConnectivityMatrix> is not required. In addition since there are
sufficient ports to handle all wavelength signals the <RBPoolState> sufficient ports to handle all wavelength signals the <RBPoolState>
element is not needed. element is not needed.
Hence the attention will be focused on the <ResourcePool> sub-TLV: Hence the attention will be focused on the <ResourcePool> sub-TLV:
<ResourcePool> ::= <ResourcePool> ::=
<ResourceBlockInfo>[<ResourceBlockAccessibility>...][<ResourceWaveCo <ResourceBlockInfo>[<RBAccessibility>...][<ResourceWaveConstraints>.
nstraints>...] ..]
/| +-----------+ +-------------+ +------+ /| +-----------+ +-------------+ +------+
/D+--->| +--->|Tunable Laser|-->| | /D+--->| +--->|Tunable Laser|-->| |
+ e+--->| | +-------------+ | C | + e+--->| | +-------------+ | C |
========>| M| | | ... | o |=======> ========>| M| | | ... | o |=======>
Port I1 + u+--->| | +-------------+ | m | Port E1 Port I1 + u+--->| | +-------------+ | m | Port O1
\x+--->| |--->|Tunable Laser|-->| b | \x+--->| |--->|Tunable Laser|-->| b |
\| | Electric | +-------------+ +------+ \| | Electric | +-------------+ +------+
| Switch | | Switch |
/| | | +-------------+ +------+ /| | | +-------------+ +------+
/D+--->| +--->|Tunable Laser|-->| | /D+--->| +--->|Tunable Laser|-->| |
+ e+--->| | +-------------+ | C | + e+--->| | +-------------+ | C |
========>| M| | | ... | o |=======> ========>| M| | | ... | o |=======>
Port I2 + u+--->| | +-------------+ | m | Port E2 Port I2 + u+--->| | +-------------+ | m | Port O2
\x+--->| +--->|Tunable Laser|-->| b | \x+--->| +--->|Tunable Laser|-->| b |
\| | | +-------------+ +------+ \| | | +-------------+ +------+
| | | |
/| | | +-------------+ +------+ /| | | +-------------+ +------+
/D+--->| |--->|Tunable Laser|-->| | /D+--->| |--->|Tunable Laser|-->| |
+ e+--->| | +-------------+ | C | + e+--->| | +-------------+ | C |
========>| M| | | ... | o |=======> ========>| M| | | ... | o |=======>
Port I3 + u+--->| | +-------------+ | m | Port E3 Port I3 + u+--->| | +-------------+ | m | Port O3
\x+--->| |--->|Tunable Laser|-->| b | \x+--->| |--->|Tunable Laser|-->| b |
\| +-----------+ +-------------+ +------+ \| +-----------+ +-------------+ +------+
Figure 2 An optical switch built around an electronic switching Figure 2 An optical switch built around an electronic switching
fabric. fabric.
The resource block information will tell us about the processing The resource block information will tell us about the processing
constraints of the receivers, transmitters and the electronic constraints of the receivers, transmitters and the electronic
switch. The resource availability information, although very simple, switch. The resource availability information, although very simple,
tells us that all signals must traverse the electronic fabric (fixed tells us that all signals must traverse the electronic fabric (fixed
skipping to change at page 34, line 18 skipping to change at page 31, line 18
| RB Set Field | | RB Set Field |
: (only one resource block in this example with shared | : (only one resource block in this example with shared |
| input/output case) | | input/output case) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1|1| Reserved | |1|1| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Optical Interface Class List(s) Sub-Sub-TLV | | Optical Interface Class List(s) Sub-Sub-TLV |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Client Signal Type Sub-TLV | | Input Client Signal Type Sub-TLV |
: (GPIDs for SDH and G.709) : : (G-PIDs for SDH and G.709) :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Bit Rate Range List Sub-Sub-TLV | | Input Bit Rate Range List Sub-Sub-TLV |
: (2.5Gbps, 10Gbps) : : (2.5Gbps, 10Gbps) :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Processing Capabilities List Sub-Sub-TLV | | Processing Capabilities List Sub-Sub-TLV |
: Fixed (non optional) 3R regeneration : : Fixed (non optional) 3R regeneration :
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Since there is fixed connectivity to resource blocks (the electronic Since there is fixed connectivity to resource blocks (the electronic
switch) the <ResourceBlockAccessibility> is: switch) the <RBAccessibility> is:
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=0|Reserved | | Connectivity=0|Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Link Set Field A #1 | | Input Link Set Field A #1 |
: (All input links connect to resource) : : (All input links connect to resource) :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB Set Field A #1 | | RB Set Field A #1 |
skipping to change at page 35, line 16 skipping to change at page 32, line 16
8.1. Normative References 8.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
(GMPLS) Signaling Functional Description", RFC 3471,
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.
[RWA-Info] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "Routing and
Wavelength Assignment Information Model for Wavelength
Switched Optical Networks", work in progress: draft-ietf-
ccamp-rwa-info.
[Gen-Encode] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "General
Network Element Constraint Encoding for GMPLS Controlled
Networks", work in progress: draft-ietf-ccamp-general-
constraint-encode.
8.2. Informative References 8.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.
[G.695] ITU-T Recommendation G.695, Optical interfaces for coarse [G.695] ITU-T Recommendation G.695, Optical interfaces for coarse
wavelength division multiplexing applications, October, wavelength division multiplexing applications, October,
2010. 2010.
[G.959.1] ITU-T Recommendation G.959.1, Optical transport network [G.959.1] ITU-T Recommendation G.959.1, Optical transport network
physical layer interfaces, February, 2012. physical layer interfaces, February, 2012.
[Gen-Encode] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "General [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching
Network Element Constraint Encoding for GMPLS Controlled (GMPLS) Signaling Functional Description", RFC 3471,
Networks", work in progress: draft-ietf-ccamp-general- January 2003.
constraint-encode.
[RFC4203] Kompella, L. and Y. Rekhter, Eds., "OSPF Extensions in
Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 4203, October 2005.
[RFC5307] Kompella, L. and Y. Rekhter, Eds., "IS-IS Extensions in
Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 5307, October, 2008.
[RFC5440] Vasseur, JP. and Le Roux, JL., Eds., "Path Computation
Element (PCE) Communication Protocol (PCEP)", RFC 5440,
March 2009.
[RFC6205] 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", RFC 6205, March 2011. Routers", RFC 6205, March 2011.
[RFC6163] Y. Lee, G. Bernstein, W. Imajuku, "Framework for GMPLS [RFC6163] Y. Lee, G. Bernstein, W. Imajuku, "Framework for GMPLS
and PCE Control of Wavelength Switched Optical Networks", and PCE Control of Wavelength Switched Optical Networks",
RFC 6163, April 2011. RFC 6163, April 2011.
[WSON-Info] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "Routing and
Wavelength Assignment Information Model for Wavelength
Switched Optical Networks", work in progress: draft-ietf-
ccamp-rwa-info.
9. Contributors 9. 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)
skipping to change at page 37, line 43 skipping to change at page 34, line 43
Phone: +81 44 396 3287 Phone: +81 44 396 3287
Email: i-nishioka@cb.jp.nec.com Email: i-nishioka@cb.jp.nec.com
Pierre Peloso Pierre Peloso
ALU ALU
Email: pierre.peloso@alcatel-lucent.com Email: pierre.peloso@alcatel-lucent.com
Cyril Margaria Cyril Margaria
NSN Email: cyril.margaria@gmail.com
Email: cyril.margaria@coriant.com
Giovanni Martinelli Giovanni Martinelli
Cisco Cisco
Email: giomarti@cisco.com Email: giomarti@cisco.com
Gabriele M Galimberti Gabriele M Galimberti
Cisco Cisco
Email: ggalimbe@cisco.com Email: ggalimbe@cisco.com
Lyndon Ong Lyndon Ong
Ciena Corporation Ciena Corporation
Email: lyong@ciena.com Email: lyong@ciena.com
 End of changes. 93 change blocks. 
365 lines changed or deleted 191 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/