draft-ietf-ccamp-rwa-wson-encode-27.txt   draft-ietf-ccamp-rwa-wson-encode-28.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: August 2015 D. Li Expires: August 2015 D. Li
Huawei Huawei
W. Imajuku W. Imajuku
NTT NTT
February 4, 2015 February 24, 2015
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-27.txt draft-ietf-ccamp-rwa-wson-encode-28.txt
Abstract
A wavelength switched optical network (WSON) requires that certain
key information fields are made available to facilitate path
computation and the establishment of label switching paths (LSPs).
The information model described in "Routing and Wavelength
Assignment Information for Wavelength Switched Optical Networks"
shows what information is required at specific points in the WSON.
Part of the WSON information model contains aspects that may be of
general applicability to other technologies, while other parts are
specific to WSONs.
This document provides efficient, protocol-agnostic encodings for
the WSON-specific information fields. It is intended that protocol-
specific documents will reference this memo to describe how
information is carried for specific uses. Such encodings can be used
to extend GMPLS signaling and routing protocols. In addition these
encodings could be used by other mechanisms to convey this same
information to a path computation element (PCE).
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 2, line 18
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 August 4, 2015. This Internet-Draft will expire on August 24, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License. warranty as described in the Simplified BSD License.
Abstract
A wavelength switched optical network (WSON) requires that certain
key information elements are made available to facilitate path
computation and the establishment of label switching paths (LSPs).
The information model described in "Routing and Wavelength
Assignment Information for Wavelength Switched Optical Networks"
shows what information is required at specific points in the WSON.
Part of the WSON information model contains aspects that may be of
general applicability to other technologies, while other parts are
specific to WSONs.
This document provides efficient, protocol-agnostic encodings for
the WSON specific information elements. It is intended that
protocol-specific documents will reference this memo to describe how
information is carried for specific uses. Such encodings can be used
to extend GMPLS signaling and routing protocols. In addition these
encodings could be used by other mechanisms to convey this same
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...................................................3 1. Introduction...................................................3
1.1. Terminology..................................................4 1.1. Terminology..................................................4
skipping to change at page 3, line 32 skipping to change at page 3, line 35
7. Acknowledgments...............................................28 7. Acknowledgments...............................................28
APPENDIX A: Encoding Examples....................................29 APPENDIX A: Encoding Examples....................................29
A.1. Wavelength Converter Accessibility Field.................29 A.1. Wavelength Converter Accessibility Field.................29
A.2. Wavelength Conversion Range Field........................31 A.2. Wavelength Conversion Range Field........................31
A.3. An OEO Switch with DWDM Optics...........................31 A.3. An OEO Switch with DWDM Optics...........................31
8. References....................................................35 8. References....................................................35
8.1. Normative References.....................................35 8.1. Normative References.....................................35
8.2. Informative References...................................35 8.2. Informative References...................................35
9. Contributors..................................................37 9. Contributors..................................................37
Authors' Addresses...............................................38 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
skipping to change at page 4, line 25 skipping to change at page 4, line 25
In parallel to this document, [Gen-Encode] provides efficient In parallel to this document, [Gen-Encode] provides efficient
encodings of information needed by the routing and label assignment encodings of information needed by the routing and label assignment
process that are potentially applicable to a wider range of process that are potentially applicable to a wider range of
technologies. technologies.
1.1. Terminology 1.1. Terminology
Refer to [RFC6163] for CWDM, DWDM, RWA, WDM. Refer to [RFC6163] for CWDM, DWDM, RWA, WDM.
Refer to Section 5 of [RWA-Info] for the terminology of Resources, Refer to Section 5 of [RWA-Info] for the terminology of Resources,
Resources Blocks, and Resource Pool. Resource Blocks, and Resource Pool.
2. Resources, Resource Blocks, and the Resource Pool 2. Resources, Resource Blocks, and the Resource Pool
This section provides encodings for the information elements defined This section provides encodings for the information fields defined
in [RWA-Info] that have applicability to WSON. The encodings are in [RWA-Info] that have applicability to WSON. The encodings are
designed to be suitable for use in the GMPLS routing protocols OSPF designed to be suitable for use in the GMPLS routing protocols OSPF
[RFC4203] and IS-IS [RFC5307] and in the PCE protocol (PCEP) [RFC4203] and IS-IS [RFC5307] and in the PCE protocol (PCEP)
[RFC5440]. Note that the information distributed in [RFC4203] and [RFC5440]. Note that the information distributed in [RFC4203] and
[RFC5307] is arranged via the nesting of sub-TLVs within TLVs and [RFC5307] is arranged via the nesting of sub-TLVs within TLVs and
this document defines elements to be used within such constructs. this document defines elements to be used within such constructs.
Specific constructs of sub-TLVs and the nesting of sub-TLVs of the Specific constructs of sub-TLVs and the nesting of sub-TLVs of the
information element defined by this document will be defined in the information field defined by this document will be defined in the
respective protocol enhancement documents. respective protocol enhancement documents.
This document defines the following information elements pertaining This document defines the following information fields pertaining to
to resources within an optical node: resources within an optical node:
. Resource Accessibility <ResourceAccessibility> . Resource Accessibility <ResourceAccessibility>
. Resource Wavelength Constraints <ResourceWaveConstraints> . Resource Wavelength Constraints <ResourceWaveConstraints>
. Resource Block Pool State <RBPoolState> . Resource Block Pool State <RBPoolState>
. Resource Block Shared Access Wavelength Availability . Resource Block Shared Access Wavelength Availability
<RBSharedAccessWaveAvailability> <RBSharedAccessWaveAvailability>
. Resource Block Information <ResourceBlockInfo> . Resource Block Information <ResourceBlockInfo>
Each of these information elements works with one or more sets of Each of these information fields works with one or more sets of
resources rather than just a single resource block. This motivates resources rather than just a single resource block. This motivates
the 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 an 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 |C| Reserved | Length | | Action |C| Reserved | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB Identifier 1 | | RB Identifier 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: : : : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 5, line 45 skipping to change at page 5, line 45
Action: 8 bits Action: 8 bits
0 - Inclusive List 0 - Inclusive List
Indicates that the TLV contains one or more RB elements that are Indicates that the TLV contains one or more RB elements that are
included in the list. included in the list.
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 Accessibility field. Ignored connectivity. Used in Resource Accessibility field. Ignored
elsewhere. elsewhere.
Reserved: 7 bits Reserved: 7 bits
skipping to change at page 6, line 28 skipping to change at page 6, line 28
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
32 bit integer. The scope of the RB identifier is local to the node 32 bit integer. The scope of the RB identifier is local to the node
on which it is applied. on which it is applied.
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 advantageous 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 Accessibility/Availability 3. Resource Accessibility/Availability
This section defines the information elements for dealing with This section defines the information fields for dealing with
accessibility and availability of resource blocks within a pool of accessibility and availability of resource blocks within a pool of
resources. These include the ResourceAccessibility, resources. These include the ResourceAccessibility,
ResourceWaveConstraints, and RBPoolState fields. ResourceWaveConstraints, and RBPoolState fields.
3.1. Resource Accessibility Field 3.1. Resource Accessibility Field
This information element describes the structure of the resource This information field describes the structure of the resource pool
pool in relation to the switching device. In particular it indicates in relation to the switching device. In particular it indicates the
the ability of an input port to reach sets of resources and of sets ability of an input port to reach sets of resources and of sets of
of resources to reach a particular output port. This is the resources to reach a particular output port. This is the
PoolInputMatrix and PoolOutputMatrix of [RWA-Info]. PoolInputMatrix and PoolOutputMatrix of [RWA-Info].
The Resource Accessibility is defined by: The Resource Accessibility 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Reserved(8bits)|C| Reserved (23 bits) | |Reserved(8bits)|C| Reserved (23 bits) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Link Set Field A #1 | | Input Link Set Field A #1 |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB Set Field A #1 | | RB Set Field A #1 |
skipping to change at page 7, line 40 skipping to change at page 7, line 40
C (Connectivity bit): Connectivity indicates how the input/output C (Connectivity bit): Connectivity indicates how the input/output
ports connect to the 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 For the Input and Output Link Set Fields, the Link Set Field
encoding defined in [Gen-Encode] is to be used. A Label Set Field encoding defined in [Gen-Encode] is to be used. A Label Set Field
MUST carry a label as defined in [RFC6205]. 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
field. field.
See Appendix A.1 for an illustration of this encoding. See Appendix A.1 for an illustration of this encoding.
3.2. Resource Wavelength Constraints Field 3.2. Resource Wavelength Constraints Field
Resources, such as wavelength converters, etc., may have a limited Resources, such as wavelength converters, etc., may have 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 fields as defined using one or more resource wavelength restrictions fields as 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 |
skipping to change at page 8, line 36 skipping to change at page 8, line 36
| RB Set Field | | RB Set Field |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Wavelength Constraints | | Input Wavelength Constraints |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Wavelength Constraints | | Output Wavelength Constraints |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
I = 1 or 0 indicates the presence or absence of the Input Wavelength I = 1 indicates the presence of the Input Wavelength Constraints
Constraints Field. Field and I = 0 indicates otherwise.
O = 1 or 0 indicates the presence or absence of the Output O = 1 indicates the presence of the Output Wavelength Constraints
Wavelength Constraints Field. Field and O = 0 indicates otherwise.
B = 1 indicates that a single wavelength constraints field B = 1 indicates that a single wavelength constraints field
represents both Input and Output Wavelength Constraints Fields. 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
skipping to change at page 10, line 46 skipping to change at page 10, line 46
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 use. The sequence of
the bit map is ordered according to the RB Set field with this the bit map is ordered according to the RB Set field with this
element. element.
Padding bits: Variable Length Padding bits: Variable Length
3.4. Resource Block Shared Access Wavelength Availability 3.4. Resource Block Shared Access Wavelength Availability
(RBSharedAccessWaveAvailability) Field (RBSharedAccessWaveAvailability) Field
Resources blocks may be accessed via a shared fiber. If this is the Resource 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|O|B| Reserved | |I|O|B| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB Set Field | | RB Set Field |
: : : :
skipping to change at page 13, line 28 skipping to change at page 13, line 28
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Optional subfield N | | Optional subfield N |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
RB Set Field is described in Section 2.1. RB Set Field is described in Section 2.1.
The shared input or output indication is indicated by the first bit The shared input or output indication is indicated by the first bit
(I), the second bit (O) and the third bit (B): (I), the second bit (O) and the third bit (B):
I = 1 or 0 indicates if the resource blocks identified in the RB set I = 1 indicates if the resource blocks identified in the RB set
field utilized a shared fiber for input access and set to 0 field utilized a shared fiber for input access and and I = 0
otherwise. indicates otherwise.
O = 1 or 0 indicates if the resource blocks identified in the RB set O = 1 indicates if the resource blocks identified in the RB set
field utilized a shared fiber for output access and set to 0 field utilized a shared fiber for output access and O = 0 indicates
otherwise. otherwise.
B = 1 indicates if the resource blocks identified in the RB set B = 1 indicates if the resource blocks identified in the RB set
field utilized a shared fiber for both input and output access and field utilized a shared fiber for both input and output access and B
set to 0 otherwise. = 0 indicates otherwise.
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).
Zero or more Optional subfields MAY be present. Optional subfields Zero or more Optional subfields MAY be present. Optional subfields
have following format: have 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value... | | Value... |
. . . .
. . . .
. . . .
skipping to change at page 14, line 38 skipping to change at page 14, line 38
1 variable Optical Interface Class List 1 variable Optical Interface Class List
2 variable Acceptable Client Signal List 2 variable Acceptable Client Signal List
3 variable Input Bit Rate List 3 variable Input Bit Rate List
4 variable Processing Capability List 4 variable Processing Capability List
See the IANA Considerations section for allocation of new Types. See the IANA Considerations section for allocation of new Types.
4.1. Optical Interface Class List Subfield 4.1. Optical Interface Class List Subfield
The list of Optical Interface Class subfield has the following The Optical Interface Class subfield 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved |I|O| | Reserved |I|O|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Optical Interface Classes | | Optical Interface Classes |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 15, line 27 skipping to change at page 15, line 27
0 0 Invalid 0 0 Invalid
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 the
input/output flags. input/output flags.
The Optical Interface Classes Format is defined as follows: The Optical Interface Classes format is defined 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|S| Reserved | OI Code Points | |S| Reserved | OI Code Points |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Optical Interface Class | | Optical Interface Class |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Optical Interface Class (Cont.) | | Optical Interface Class (Cont.) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where the first 32 bits of the encoding shall be used to identify Where the first 32 bits of the encoding shall be used to identify
the semantic of the Optical Interface Class in the following way: the semantics of the Optical Interface Class in the following way:
S Standard bit. S Standard bit.
S=0, identify non ITU code points S=0, identify non-ITU code points
S=1, identify ITU application codes S=1, identify ITU application codes
With S=0, the OI Code Points field can take the following With S=0, the OI Code Points field can take the following
values: value:
0: reserved 0: reserved
Future work may add support for vendor-specific AI once the Future work may add support for vendor-specific AI once the
ITU-T has completed its work in that area. ITU-T has completed its work in that area.
With S=1, the OI Code Points field can take the following With S=1, the OI Code Points field can take the following
values: values:
0: reserved 0: reserved
1: [G.698.1] application code. 1: [G.698.1] application code.
2: [G.698.2] application code. 2: [G.698.2] application code.
3: [G.959.1] application code. 3: [G.959.1] application code.
4: [G.695] application code. 4: [G.695] application code.
In case of ITU Application Code, the mapping between the string In the case of ITU Application Codes, the mapping between the string
defining the application code and the 64 bits number implementing defining the application code and the 64 bits implementing the
the optical interface class is given in the following sections. optical interface class is given in the following sections.
4.1.1. ITU-G.698.1 Application Code Mapping 4.1.1. ITU-G.698.1 Application Code Mapping
[698.1] defines the Application Codes: DScW-ytz(v) and B-DScW- [698.1] defines the Application Codes: DScW-ytz(v) and B-DScW-
ytz(v). Where: ytz(v). Where:
B: means Bidirectionals. B: means Bidirectional.
D: means a DWDM application. D: means a DWDM application.
S: take values N (narrow spectral excursion), W (wide spectral S: takes values N (narrow spectral excursion), W (wide spectral
excursion). excursion).
c: Channel Spacing (GHz). c: Channel Spacing (GHz).
W: take values S (short-haul), L (long-haul). W: takes values S (short-haul), L (long-haul).
y: take values 1 (NRZ 2.5G), 2 (indicating NRZ 10G). y: takes values 1 (NRZ 2.5G), 2 (indicating NRZ 10G).
t: take only D value is defined (link does not contain optical t: only D value is defined (link does not contain optical
amplifier) amplifier)
z: take values 2 ([G.652] fibre), 3 ([G.653] fibre), 5 z: takes values 2 ([G.652] fibre), 3 ([G.653] fibre), 5
(indicating [G.655] fibre). (indicating [G.655] fibre).
v: take values S (Short wavelength), C (Conventional), L (Long v: takes values S (Short wavelength), C (Conventional), L (Long
wavelength). wavelength).
The F flag indicates the presence or not of an optional FEC The F flag indicates the presence or absence of an optional FEC
Encoding suffix. Encoding suffix.
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| D |S| c | W | y | t | z | v | F | |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 parentheses refer to ITU defined values as
reported above: reported above:
B: = 1 bidirectional, 0 otherwise B: = 1 bidirectional, 0 otherwise
D (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 the same
in Figure 2 in Section 3.2 of [RFC6205] (note that DWDM spacing definition as in Figure 2 in Section 3.2 of [RFC6205] (note that
apply here) DWDM spacing applies 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)
F (suffix): = 0 No FEC Encoding suffix present, = 1 FEC F (suffix): = 0 No FEC Encoding suffix present, = 1 FEC
Encoding suffix present Encoding suffix present
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.1.2. ITU-G.698.2 Application Code Mapping 4.1.2. ITU-G.698.2 Application Code Mapping
[G.698.2] defines the Application Codes: DScW-ytz(v) and B-DScW- [G.698.2] defines the Application Codes: DScW-ytz(v) and B-DScW-
ytz(v). 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: takes values N (narrow spectral excursion), W (wide spectral
excursion). excursion).
c: Channel Spacing (GHz). c: Channel Spacing (GHz).
W: take values C (link is dispersion compensated), U (link is W: takes values C (link is dispersion compensated), U (link is
dispersion uncompensated). dispersion uncompensated).
y: take values 1 (NRZ 2.5G), 2 (indicating NRZ 10G). y: takes values 1 (NRZ 2.5G), 2 (indicating NRZ 10G).
t: take value A (link may contains optical amplifier) t: takes value A (link may contains optical amplifier)
z: take values 2 ([G.652] fibre), 3 ([G.653] fibre), 5 z: takes values 2 ([G.652] fibre), 3 ([G.653] fibre), 5
(indicating [G.655] fibre). (indicating [G.655] fibre).
v: take values S (Short wavelength), C (Conventional), L (Long v: takes 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| D |S| c | W | y | t | z | v | F | |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 parentheses refer to ITU defined values as
reported above): reported above):
B: = 1 bidirectional, 0 otherwise B: = 1 bidirectional, 0 otherwise
D (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 the same
in Figure 2 in Section 3.2 of [RFC6205] (note that DWDM spacing definition as in Figure 2 in Section 3.2 of [RFC6205] (note that
apply here) DWDM spacing applies 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)
F (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.1.3. ITU-G.959.1 Application Code Mapping 4.1.3. ITU-G.959.1 Application Code Mapping
[G.959.1] defines the Application Codes: PnWx-ytz and BnWx-ytz. [G.959.1] defines the Application Codes: PnWx-ytz and BnWx-ytz.
Where: 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: takes values I (intra-office), S (short-haul), L (long-haul),
(very long-haul), U (ultra long-haul). V (very long-haul), U (ultra long-haul).
x: maximum number of spans allowed within the application code x: maximum number of spans allowed within the application code
(i.e. an integer number) (i.e., an integer number)
y: take values 1 (NRZ 2.5G), 2 (NRZ 10G), 9 (NRZ 25G), 3 (NRZ y: takes values 1 (NRZ 2.5G), 2 (NRZ 10G), 9 (NRZ 25G), 3 (NRZ
40G), 7 (RZ 40G). 40G), 7 (RZ 40G).
t: take values A (power levels suitable for a booster amplifier t: takes values A (power levels suitable for a booster amplifier
in the originating ONE and power levels suitable for a pre-amplifier in the originating ONE and power levels suitable for a pre-amplifier
in the terminating ONE), B (booster amplifier only), C (pre- in the terminating ONE), B (booster amplifier only), C (pre-
amplifier only), D (no amplifiers). amplifier only), D (no amplifiers).
z: take values 1 (1310 nm sources on [G.652] fibre), 2 (1550 z: takes values 1 (1310 nm sources on [G.652] fibre), 2 (1550
nm sources on [G.652] fibre), 3 (1550 nm sources on [G.653] fibre), nm sources on [G.652] fibre), 3 (1550 nm sources on [G.653] fibre),
5 (1550 nm sources on [G.655] fibre). 5 (1550 nm sources on [G.655] fibre).
The following list of suffixes can be added to these application The following list of suffixes can be added to these application
codes: codes:
F: FEC encoding. F: FEC encoding.
D: Adaptive dispersion compensation. D: Adaptive dispersion compensation.
skipping to change at page 21, line 13 skipping to change at page 21, line 13
These values are encoded as follows: These values are 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| p | P | n | W | x | reserved | | p | P | n | W | x | reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| y | t | z | suffix | reserved | | y | t | z | suffix | reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where (values between parenthesis refer to ITU defined values as Where (values between parentheses refer to ITU defined values as
reported above): reported above):
p (prefix) = 0 otherwise, = 1 Bidirectional (B) p (prefix) = 0 otherwise, = 1 Bidirectional (B)
P (optional): = 0 not present, = 2 (P). P (optional): = 0 not present, = 2 (P).
n: maximum number of channels (10 bits, up to 1023 channels) n: maximum number of channels (10 bits, up to 1023 channels)
W: = 0 reserved, = 1 (I), = 2 (S), = 3 (L), = 4 (V), = 5 (U) W: = 0 reserved, = 1 (I), = 2 (S), = 3 (L), = 4 (V), = 5 (U)
x: = number of spans (6 bits, up to 64 spans) x: = number of spans (6 bits, up to 64 spans)
y: = 0 reserved, = 1 (1), = 2 (2), = 3 (3), = 7 (7), = 9 (9) y: = 0 reserved, = 1 (1), = 2 (2), = 3 (3), = 7 (7), = 9 (9)
t: = 0 reserved, = 1 (A), = 2 (B), = 3 (C), = 4 (D) t: = 0 reserved, = 1 (A), = 2 (B), = 3 (C), = 4 (D)
z: = 0 reserved, = 1 (1), = 2 (2), = 3 (3), = 5 (5) z: = 0 reserved, = 1 (1), = 2 (2), = 3 (3), = 5 (5)
suffix is an 6 bit, bit map: suffix is a 6-bit bitmap:
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.1.4. ITU-G.695 Application Code Mapping 4.1.4. ITU-G.695 Application Code Mapping
[G.695] defines the Application Codes: CnWx-ytz and B-CnWx-ytz and [G.695] defines the Application Codes: CnWx-ytz and B-CnWx-ytz and
S-CnWx-ytz. S-CnWx-ytz.
Where the optional prefixed are: Where the optional prefixes are:
B: Bidirectional B: Bidirectional
S: a system using a black link approach S: a system using a black link approach
And the rest of the application code is defined as: And the rest of the application code is defined as:
C: CWDM (Coarse WDM) application C: CWDM (Coarse WDM) application
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 S (short-haul), L (long-haul). W: takes values S (short-haul), L (long-haul).
x: maximum number of spans allowed x: maximum number of spans allowed
y: take values 0 (NRZ 1.25G), 1 (NRZ 2.5G), 2 (NRZ 10G). y: takes values 0 (NRZ 1.25G), 1 (NRZ 2.5G), 2 (NRZ 10G).
t: take values D (link does not contain any optical amplifier). t: takes value D (link does not contain any optical amplifier).
z: take values 1 (1310 nm region for [G.652] fibre), 2 (ITU-T z: takes values 1 (1310 nm region for [G.652] fibre), 2 (ITU-T
[G.652] fibre), 3 ([G.653] fibre), 5 ([G.655] fibre). [G.652] fibre), 3 ([G.653] fibre), 5 ([G.655] fibre).
The following list of suffixes can be added to these application The following list of suffixes can be added to these application
codes: codes:
F: FEC encoding. F: FEC encoding.
Since the application codes are very similar to the one from the Since the application codes are very similar to the ones from the
[G.959] section most of the fields are reused. The 64 bit OIC field [G.959] section most of the fields are reused. The 64-bit OIC field
is encoded as follows: is 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| p | C | n | W | x | reserved | | p | C | n | W | x | reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| y | t | z | suffix | reserved | | y | t | z | suffix | reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where (values between parenthesis refer to ITU defined values as Where (values between parentheses refer to ITU defined values as
reported above): reported above):
p: = 0 no prefix, 1 = B bidirectional, = 2 S black link p: = 0 no prefix, = 1 B bidirectional, = 2 S black link
C: = 0 reserved, = 3 (C). C: = 0 reserved, = 3 (C).
n: maximum number of channels (10 bits, up to 1023 channels) n: maximum number of channels (10 bits, up to 1023 channels)
W: = 0 reserved, = 1 reserved, = 2 (S), = 3 (L), > 3 reserved W: = 0 reserved, = 1 reserved, = 2 (S), = 3 (L), > 3 reserved
x: = number of spans (6 bits, up to 64 spans) x: = number of spans (6 bits, up to 64 spans)
y: = 0 (0), = 1 (1), =2 (2), > 2 reserved y: = 0 (0), = 1 (1), =2 (2), > 2 reserved
t: = 4 (D), all other values are reserved t: = 4 (D), all other values are reserved
z: = 0 reserved, = 1 (1), = 2 (2), = 3 (3) z: = 0 reserved, = 1 (1), = 2 (2), = 3 (3)
suffix is an 6 bit, bit map: suffix is a 6-bit bitmap:
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.2. Acceptable Client Signal List Subfield 4.2. Acceptable Client Signal List Subfield
skipping to change at page 24, line 37 skipping to change at page 24, line 37
Length (16 bits): The Length field defines the length of the value Length (16 bits): The Length field defines the length of the value
portion in octets. portion in octets.
The number of G-PIDs is an integer greater than or equal to one. The number of G-PIDs is an integer greater than or equal to one.
G-PIDs are assigned by IANA and many are defined in [RFC3471] and G-PIDs are assigned by IANA and many are defined in [RFC3471] and
[RFC4328]. [RFC4328].
4.3. Input Bit Rate List Subfield 4.3. Input Bit Rate List Subfield
This subfield contains a list of bit rate of each input client This subfield contains a list of bit rates of each input client
signal types specified in the Input Client Signal List. signal type specified in the Input Client Signal List.
The number of Input Bit Rate MUST match the number of G-PID. The number of Input Bit Rates MUST match the number of G-PIDs.
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 G-PID #1 | | Input Bit Rate of G-PID #1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Bit Rate of G-PID #N | | Input Bit Rate of G-PID #N |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Input Bit Rates are in IEEE floating point format [IEEE]. Input Bit Rates are in IEEE 754 floating point format [IEEE].
4.4. Processing Capability List Subfield 4.4. Processing Capability List Subfield
This subfield contains a list of resource processing capabilities.
The processing capability list field is a list of capabilities that The processing capability list field is a list of capabilities that
can be achieved through the referred resources: 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
Fault and performance monitoring and vendor Specific capability have Fault and performance monitoring and Vendor specific capability have
no additional capability parameters. no additional capability parameters.
The processing capability list field is then given by: The processing capability list 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Processing Cap ID | | Reserved | Processing Cap ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Possible additional capability parameters depending upon | | Possible additional capability parameters depending upon |
skipping to change at page 26, line 14 skipping to change at page 26, line 14
The processing capability ID field defines the following processing The processing capability ID field defines the following processing
capabilities: capabilities:
0: Reserved 0: Reserved
1: Regeneration capability 1: Regeneration capability
2: Fault and performance monitoring 2: Fault and performance monitoring
3: Vendor Specific capability 3: Vendor specific capability
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 following additional capability parameters are provided in the
following field: following 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| T | C | Reserved | | T | C | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where T bit indicates the type of regenerator: Where the T bit indicates the type of regenerator:
T=0: Reserved T=0: Reserved
T=1: 1R Regenerator T=1: 1R Regenerator
T=2: 2R Regenerator T=2: 2R Regenerator
T=3: 3R Regenerator T=3: 3R Regenerator
Where C bit indicates the capability of regenerator: Where the C bit indicates the capability of the regenerator:
C=0: Reserved C=0: Reserved
C=1: Fixed Regeneration Point C=1: Fixed Regeneration Point
C=2: Selective Regeneration Point C=2: Selective Regeneration Pools
Note that when the capability of regenerator is indicated to be Note that when the capability of the regenerator is indicated to be
Selective Regeneration Pools, regeneration pool properties such as Selective Regeneration Pools, regeneration pool properties such as
input and output restrictions and availability need to be specified. input and output restrictions and availability need to be specified.
These properties will be encoded in the capabilities field starting These properties will be encoded in the capabilities field starting
with the bits marked Reserved in the figure. An additional with the bits marked Reserved in the figure. An additional
specification describing the encoding of these parameters is specification describing the encoding of these parameters is
required before the value C=2 can be used. required before the value C=2 can be used.
5. Security Considerations 5. 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. A general discussion on security in GMPLS networks can protection. A general discussion on security in GMPLS networks can
be found in [RFC5920]. be found in [RFC5920].
6. IANA Considerations 6. IANA Considerations
This document introduces a new registry for GMPLS routing parameters This document introduces a new top-level registry for GMPLS routing
for WSON encoding. This new IANA registry will be created to make parameters for WSON encoding. This new IANA registry will be created
the assignment of a new type and new values for the new "GMPLS to make the assignment of a new type and new values for the new
Routing Parameters for WSON." Note that this registry is only used "GMPLS Routing Parameters for WSON". Note that this registry is only
in routing, not in signaling. used in routing, not in signaling.
6.1. Types for subfields of WSON Resource Block Information 6.1. Types for subfields of WSON Resource Block Information
Under this new GMPLS Routing Parameters for WSON, a new IANA Under this new GMPLS Routing Parameters for WSON, a new IANA
registry will be created for nested subfields of the Resource Block registry will be created for nested subfields of the Resource Block
Information field to create a new section named "Types for subfields Information field to create a new section named "Types for subfields
of WSON Resource Block Information" and allocate new values as of WSON Resource Block Information Registry". The new registry will
follows: be maintained via Standards Action as defined by [RFC5226].
There are initial values in the new registry as follows:
Value Length Sub-TLV Type Reference Value Length Sub-TLV Type Reference
0 Reserved 0 Reserved
1 variable Optical Interface Class List [This.I-D] 1 variable Optical Interface Class List [This.I-D]
2 variable Acceptable Client 2 variable Acceptable Client
Signal List [This.I-D] Signal List [This.I-D]
3 variable Input Bit Rate List [This.I-D] 3 variable Input Bit Rate List [This.I-D]
4 variable Processing Capability List [This.I-D] 4 variable Processing Capability List [This.I-D]
5-65535 Unassigned 5-65535 Unassigned
Types are to be assigned via Standards Action as defined in
[RFC5226].
7. Acknowledgments 7. 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 Field A.1. Wavelength Converter Accessibility Field
Example: Example:
Figure 1 shows a wavelength converter pool architecture know as Figure 1 shows a wavelength converter pool architecture known as
"shared per fiber". In this case the input and output pool matrices "shared per fiber". In this case the input and output pool matrices
are simply: are simply:
+-----+ +-----+ +-----+ +-----+
| 1 1 | | 1 0 | | 1 1 | | 1 0 |
WI =| |, WE =| | WI =| |, WE =| |
| 1 1 | | 0 1 | | 1 1 | | 0 1 |
+-----+ +-----+ +-----+ +-----+
+-----------+ +------+ +-----------+ +------+
skipping to change at page 32, line 7 skipping to change at page 32, line 7
<Node_Info> ::= <Node_ID> <Node_Info> ::= <Node_ID>
[Other GMPLS info-elements] [Other GMPLS info-elements]
[<ConnectivityMatrix>...] [<ConnectivityMatrix>...]
[<ResourcePool>] [<ResourcePool>]
[<RBPoolState>] [<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> field: Hence the attention will be focused on the <ResourcePool> field:
<ResourcePool> ::= <ResourceBlockInfo> <ResourcePool> ::= <ResourceBlockInfo>
[<RBAccessibility>...] [<RBAccessibility>...]
skipping to change at page 32, line 48 skipping to change at page 32, line 48
+ e+--->| | +-------------+ | C | + e+--->| | +-------------+ | C |
========>| M| | | ... | o |=======> ========>| M| | | ... | o |=======>
Port I3 + u+--->| | +-------------+ | m | Port O3 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
connectivity). The resource wavelength constraints are not needed connectivity). The resource wavelength constraints are not needed
since there are no special wavelength constraints for the resources since there are no special wavelength constraints for the resources
that would not appear as port/wavelength constraints. that would not appear as port/wavelength constraints.
<ResourceBlockInfo>: <ResourceBlockInfo>:
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 39, line 29 skipping to change at line 1523
Email: imajuku.wataru@lab.ntt.co.jp Email: imajuku.wataru@lab.ntt.co.jp
Jianrui Han Jianrui Han
Huawei Technologies Co., Ltd. Huawei Technologies Co., Ltd.
F3-5-B R&D Center, Huawei Base, F3-5-B R&D Center, Huawei Base,
Bantian, Longgang District Bantian, Longgang District
Shenzhen 518129 P.R.China Shenzhen 518129 P.R.China
Phone: +86-755-28972916 Phone: +86-755-28972916
Email: hanjianrui@huawei.com Email: hanjianrui@huawei.com
Intellectual Property Statement
The IETF Trust takes no position regarding the validity or scope of
any Intellectual Property Rights or other rights that might be
claimed to pertain to the implementation or use of the technology
described in any IETF Document or the extent to which any license
under such rights might or might not be available; nor does it
represent that it has made any independent effort to identify any
such rights.
Copies of Intellectual Property disclosures made to the IETF
Secretariat and any assurances of licenses to be made available, or
the result of an attempt made to obtain a general license or
permission for the use of such proprietary rights by implementers or
users of this specification can be obtained from the IETF on-line
IPR repository at http://www.ietf.org/ipr
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
any standard or specification contained in an IETF Document. Please
address the information to the IETF at ietf-ipr@ietf.org.
Disclaimer of Validity
All IETF Documents and the information contained therein are
provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION
HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY,
THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE
ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 92 change blocks. 
138 lines changed or deleted 133 lines changed or added

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