draft-ietf-ccamp-rwa-wson-encode-07.txt   draft-ietf-ccamp-rwa-wson-encode-08.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: June 2011 D. Li Expires: September 2011 D. Li
Huawei Huawei
W. Imajuku W. Imajuku
NTT NTT
December 1, 2010 March 1, 2011
Routing and Wavelength Assignment Information Encoding for Routing and Wavelength Assignment Information Encoding for
Wavelength Switched Optical Networks Wavelength Switched Optical Networks
draft-ietf-ccamp-rwa-wson-encode-07.txt draft-ietf-ccamp-rwa-wson-encode-08.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on June 1, 2011. This Internet-Draft will expire on September 1, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 8 skipping to change at page 3, line 8
1. Introduction...................................................3 1. Introduction...................................................3
1.1. Revision History..........................................4 1.1. Revision History..........................................4
1.1.1. Changes from 00 draft................................4 1.1.1. Changes from 00 draft................................4
1.1.2. Changes from 01 draft................................4 1.1.2. Changes from 01 draft................................4
1.1.3. Changes from 02 draft................................5 1.1.3. Changes from 02 draft................................5
1.1.4. Changes from 03 draft................................5 1.1.4. Changes from 03 draft................................5
1.1.5. Changes from 04 draft................................5 1.1.5. Changes from 04 draft................................5
1.1.6. Changes from 05 draft................................5 1.1.6. Changes from 05 draft................................5
1.1.7. Changes from 06 draft................................5 1.1.7. Changes from 06 draft................................5
2. Terminology....................................................5 1.1.8. Changes from 07 draft................................5
3. Resource Accessibility/Availability............................6 2. Terminology....................................................6
3.1. Block Accessibility Sub-TLV...............................7 3. Resource Pool Accessibility/Availability.......................6
3.2. Wavelength Constraints Sub-TLV............................9 3.1. Resource Pool Block Accessibility Sub-TLV.................8
3.3. Block Pool State Sub-TLV..................................9 3.2. Resource Block Wavelength Constraints Sub-TLV.............9
3.4. Block Shared Access Wavelength Availability sub-TLV......11 3.3. Block Pool State Sub-TLV.................................10
4. Resource Properties Encoding..................................12 3.4. Block Shared Access Wavelength Availability sub-TLV......12
4.1. Resource Block Information Sub-TLV.......................12 4. Resource Properties Encoding..................................13
4.2. Input Modulation Format List Sub-Sub-TLV.................13 4.1. Resource Block Information Sub-TLV.......................13
4.2.1. Modulation Format Field.............................14 4.2. Input Modulation Format List Sub-Sub-TLV.................14
4.3. Input FEC Type List Sub-Sub-TLV..........................15 4.2.1. Modulation Format Field.............................15
4.3.1. FEC Type Field......................................16 4.3. Input FEC Type List Sub-Sub-TLV..........................16
4.4. Input Bit Range List Sub-Sub-TLV.........................18 4.3.1. FEC Type Field......................................17
4.4.1. Bit Range Field.....................................18 4.4. Input Bit Range List Sub-Sub-TLV.........................19
4.5. Input Client Signal List Sub-Sub-TLV.....................19 4.4.1. Bit Range Field.....................................19
4.6. Processing Capability List Sub-Sub-TLV...................20 4.5. Input Client Signal List Sub-Sub-TLV.....................20
4.6.1. Processing Capabilities Field.......................20 4.6. Processing Capability List Sub-Sub-TLV...................21
4.7. Output Modulation Format List Sub-Sub-TLV................22 4.6.1. Processing Capabilities Field.......................21
4.8. Output FEC Type List Sub-Sub-TLV.........................22 4.7. Output Modulation Format List Sub-Sub-TLV................23
5. Security Considerations.......................................22 4.8. Output FEC Type List Sub-Sub-TLV.........................23
6. IANA Considerations...........................................23 5. Security Considerations.......................................23
7. Acknowledgments...............................................23 6. IANA Considerations...........................................24
APPENDIX A: Encoding Examples....................................24 7. Acknowledgments...............................................24
A.1. Wavelength Converter Accessibility Sub-TLV...............24 APPENDIX A: Encoding Examples....................................25
A.2. Wavelength Conversion Range Sub-TLV......................25 A.1. Wavelength Converter Accessibility Sub-TLV...............25
A.3. An OEO Switch with DWDM Optics...........................26 A.2. Wavelength Conversion Range Sub-TLV......................26
8. References....................................................30 A.3. An OEO Switch with DWDM Optics...........................27
8.1. Normative References.....................................30 8. References....................................................31
8.2. Informative References...................................30 8.1. Normative References.....................................31
9. Contributors..................................................31 8.2. Informative References...................................31
Authors' Addresses...............................................32 9. Contributors..................................................32
Intellectual Property Statement..................................33 Authors' Addresses...............................................33
Disclaimer of Validity...........................................33 Intellectual Property Statement..................................34
Disclaimer of Validity...........................................34
1. Introduction 1. Introduction
A Wavelength Switched Optical Network (WSON) is a Wavelength Division A Wavelength Switched Optical Network (WSON) is a Wavelength Division
Multiplexing (WDM) optical network in which switching is performed Multiplexing (WDM) optical network in which switching is performed
selectively based on the center wavelength of an optical signal. selectively based on the center wavelength of an optical signal.
[WSON-Frame] describes a framework for Generalized Multiprotocol [WSON-Frame] describes a framework for Generalized Multiprotocol
Label Switching (GMPLS) and Path Computation Element (PCE) control of Label Switching (GMPLS) and Path Computation Element (PCE) control of
a WSON. Based on this framework, [WSON-Info] describes an information a WSON. Based on this framework, [WSON-Info] describes an information
skipping to change at page 5, line 36 skipping to change at page 5, line 38
1.1.6. Changes from 05 draft 1.1.6. Changes from 05 draft
Revised the encoding for the "shared access" indicators to only use Revised the encoding for the "shared access" indicators to only use
one bit each for ingress and egress. one bit each for ingress and egress.
1.1.7. Changes from 06 draft 1.1.7. Changes from 06 draft
Removed section on "WSON Encoding Usage Recommendations" 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.
2. Terminology 2. Terminology
CWDM: Coarse Wavelength Division Multiplexing. CWDM: Coarse Wavelength Division Multiplexing.
DWDM: Dense Wavelength Division Multiplexing. DWDM: Dense Wavelength Division Multiplexing.
FOADM: Fixed Optical Add/Drop Multiplexer. FOADM: Fixed Optical Add/Drop Multiplexer.
ROADM: Reconfigurable Optical Add/Drop Multiplexer. A reduced port ROADM: Reconfigurable Optical Add/Drop Multiplexer. A reduced port
count wavelength selective switching element featuring ingress and count wavelength selective switching element featuring ingress and
skipping to change at page 6, line 17 skipping to change at page 6, line 31
"equivalent" content centered at a different wavelength. Wavelength "equivalent" content centered at a different wavelength. Wavelength
conversion can be implemented via an optical-electronic-optical (OEO) conversion can be implemented via an optical-electronic-optical (OEO)
process or via a strictly optical process. process or via a strictly optical process.
WDM: Wavelength Division Multiplexing. WDM: Wavelength Division Multiplexing.
Wavelength Switched Optical Network (WSON): A WDM based optical Wavelength Switched Optical Network (WSON): A WDM based optical
network in which switching is performed selectively based on the network in which switching is performed selectively based on the
center wavelength of an optical signal. center wavelength of an optical signal.
3. Resource Accessibility/Availability 3. Resource Pool Accessibility/Availability
In this section we define the sub-TLVs for dealing with accessibility In this section we define the sub-TLVs for dealing with accessibility
and availability of resource blocks. These include the and availability of resource blocks within a pool of resources. These
ResourceBlockAccessibility, ResourceWaveConstraints, and RBPoolState include the ResourceBlockAccessibility, ResourceWaveConstraints, and
sub-TLVs. All these sub-TLVs are concerned with sets of resources. RBPoolState sub-TLVs. All these sub-TLVs are concerned with sets of
resources. As described in [WSON-Info] a resource pool is composed of
blocks of resources with similar properties and accessibility
characteristics.
In a WSON node that includes resource blocks (RB) we will want to In a WSON node that includes resource blocks (RB) we will want to
denote subsets these blocks to efficiently describe common properties denote subsets these blocks to efficiently describe common properties
the blocks and to describe the structure, if non-trivial, of the the blocks and to describe the structure, if non-trivial, of the
resource pool. The RB Set field is defined in a similar manner to the resource pool. The RB Set field is defined in a similar manner to the
label set concept of [RFC3471]. label set concept of [RFC3471].
The information carried in a RB set field is defined by: The information carried in a RB set field is defined by:
0 1 2 3 0 1 2 3
skipping to change at page 7, line 36 skipping to change at page 8, line 10
Length: 16 bits Length: 16 bits
The total length of this field in bytes. The total length of this field in bytes.
RB Identifier: RB Identifier:
The RB identifier represents the ID of the resource block which is a The RB identifier represents the ID of the resource block which is a
16 bit integer. 16 bit integer.
3.1. Block Accessibility Sub-TLV 3.1. Resource Pool Block Accessibility Sub-TLV
This sub-TLV describes the structure of the resource pool in relation This sub-TLV describes the structure of the resource pool in relation
to the switching device. In particular it indicates the ability of an to the switching device. In particular it indicates the ability of an
ingress port to reach a resource block and of a resource block to ingress port to reach a resource block and of a resource block to
reach a particular egress port. This is the PoolIngressMatrix and reach a particular egress port. This is the PoolIngressMatrix and
PoolEgressMatrix of [WSON-Info]. PoolEgressMatrix of [WSON-Info].
The resource block accessibility sub-TLV is defined by: The resource block accessibility sub-TLV is defined by:
0 1 2 3 0 1 2 3
skipping to change at page 9, line 5 skipping to change at page 9, line 16
The Link Set Field is defined in [Gen-Encode]. The Link Set Field is defined in [Gen-Encode].
Note that the direction parameter within the Link Set Field is used Note that the direction parameter within the Link Set Field is used
to indicate whether the link set is an ingress or egress link set, to indicate whether the link set is an ingress or egress link set,
and the bidirectional value for this parameter is not permitted in and the bidirectional value for this parameter is not permitted in
this sub-TLV. this sub-TLV.
See Appendix A.1 for an illustration of this encoding. See Appendix A.1 for an illustration of this encoding.
3.2. Wavelength Constraints Sub-TLV 3.2. Resource Block Wavelength Constraints Sub-TLV
Resources, such as wavelength converters, etc., may have a limited Resources, such as wavelength converters, etc., may have a limited
input or output wavelength ranges. Additionally, due to the structure input or output wavelength ranges. Additionally, due to the structure
of the optical system not all wavelengths can necessarily reach or of the optical system not all wavelengths can necessarily reach or
leave all the resources. These properties are described by using one leave all the resources. These properties are described by using one
or more resource wavelength restrictions sub-TLVs as defined below: or more resource wavelength restrictions sub-TLVs as defined below:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 9, line 43 skipping to change at page 10, line 10
Indicates the wavelength input restrictions of the RBs in the Indicates the wavelength input restrictions of the RBs in the
corresponding RB set. corresponding RB set.
Output Wavelength Set Field: Output Wavelength Set Field:
Indicates the wavelength output restrictions of RBs in the Indicates the wavelength output restrictions of RBs in the
corresponding RB set. corresponding RB set.
3.3. Block Pool State Sub-TLV 3.3. Block Pool State Sub-TLV
The usage state of a resource is encoded as either a list of 16 bit The usage state of resources within a block is encoded as either a
integer values or a bit map indicating whether a single resource is list of 16 bit integer values or a bit map indicating whether a
available or in use. This information can be relatively dynamic, single resource is available or in use. The bit map encoding is
i.e., can change when a connection is established or torn down. appropriate when resource blocks consist of a single resource. This
information can be relatively dynamic, i.e., can change when a
connection is established or torn down.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Action | Reserved | | Action | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB Set Field | | RB Set Field |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB Usage state | | RB Usage state |
skipping to change at page 11, line 21 skipping to change at page 12, line 21
Each bit indicates the usage status of one RB with 0 indicating the Each bit indicates the usage status of one RB with 0 indicating the
RB is available and 1 indicating the RB is in used. The sequence of RB is available and 1 indicating the RB is in used. The sequence of
the bit map is ordered according to the RB Set field with this sub- the bit map is ordered according to the RB Set field with this sub-
TLV. TLV.
Padding bits: Variable Length Padding bits: Variable Length
3.4. Block Shared Access Wavelength Availability sub-TLV 3.4. Block Shared Access Wavelength Availability sub-TLV
Resources blocks may be accessed via a shared fiber. If this is the Resources blocks may be accessed via a shared fiber. If this is the
case then wavelength availability on these shared fiber is needed to case then wavelength availability on these shared fibers is needed to
understand resource availability. 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Resource Block ID |I|E| Reserved | | Resource Block ID |I|E| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Ingress Available Wavelength Set Field | | Ingress Available Wavelength Set Field |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 12, line 25 skipping to change at page 13, line 25
4. Resource Properties Encoding 4. Resource Properties Encoding
Within a WSON network element (NE) there may be resources with signal Within a WSON network element (NE) there may be resources with signal
compatibility constraints. Such resources typically come in "blocks" compatibility constraints. Such resources typically come in "blocks"
which contain a group on identical and indistinguishable individual which contain a group on identical and indistinguishable individual
resources. These resource blocks may consist of regenerators, resources. These resource blocks may consist of regenerators,
wavelength converters, etc... Such resource blocks may also wavelength converters, etc... Such resource blocks may also
constitute the network element as a whole as in the case of an constitute the network element as a whole as in the case of an
electro optical switch. In this section we primarily focus on the electro optical switch. In this section we primarily focus on the
signal compatibility and processing properties of such a resource signal compatibility and processing properties of such a resource
block, i.e., <ResourceBlockInfo> of section Error! Reference source block, the accessibility aspects of a resource in a shared pool,
not found. the accessibility aspects of a resource in a shared pool,
except for the shared access indicators, were encoded in the previous except for the shared access indicators, were encoded in the previous
section. section.
The fundamental properties of a resource block, such as a regenerator The fundamental properties of a resource block, such as a regenerator
or wavelength converter, are: or wavelength converter, are:
(a)Input constraints (shared ingress, modulation, FEC, bit rate, (a)Input constraints (shared ingress, modulation, FEC, bit rate,
GPID) GPID)
(b)Processing capabilities (number of resources in a block, (b)Processing capabilities (number of resources in a block,
skipping to change at page 13, line 19 skipping to change at page 14, line 19
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I|E| Reserved | |I|E| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Modulation Type List Sub-Sub-TLV (opt) | | Input Modulation Type List Sub-Sub-TLV (opt) |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input FEC Type List Sub-Sub-TLV (opt) | | Input FEC Type List Sub-Sub-TLV (opt) |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Client Signal Type Sub-TLV (opt) | | Input Client Signal Type Sub-Sub-TLV (opt) |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Bit Rate Range List Sub-Sub-TLV (opt) | | Input Bit Rate Range List Sub-Sub-TLV (opt) |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Processing Capabilities List Sub-Sub-TLV (opt) | | Processing Capabilities List Sub-Sub-TLV (opt) |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Modulation Type List Sub-Sub-TLV (opt) | | Output Modulation Type List Sub-Sub-TLV (opt) |
: : : :
skipping to change at page 13, line 41 skipping to change at page 14, line 41
| Output FEC Type List Sub-Sub-TLV (opt) | | Output FEC Type List Sub-Sub-TLV (opt) |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where I and E, the shared ingress/egress indicator, is set to 1 if Where I and E, the shared ingress/egress indicator, is set to 1 if
the resource blocks identified in the RB set field utilized a shared the resource blocks identified in the RB set field utilized a shared
fiber for ingress/egress access and set to 0 otherwise. fiber for ingress/egress access and set to 0 otherwise.
4.2. Input Modulation Format List Sub-Sub-TLV 4.2. Input Modulation Format List Sub-Sub-TLV
This sub-TLV contains a list of acceptable input modulation formats. This sub-sub-TLV contains a list of acceptable input modulation
formats.
Type := Input Modulation Format List Type := Input Modulation Format List
Value:= A list of Modulation Format Fields Value := A list of Modulation Format Fields
4.2.1. Modulation Format Field 4.2.1. Modulation Format Field
Two different types of modulation format fields are defined: a Two different types of modulation format fields are defined: a
standard modulation field and a vendor specific modulation field. standard modulation field and a vendor specific modulation field.
Both start with the same 32 bit header shown below. Both start with the same 32 bit header shown below.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|S|I| Modulation ID | Length | |S|I| Modulation ID | Length |
skipping to change at page 15, line 45 skipping to change at page 16, line 45
Enterprise Numbers are assigned by IANA and managed through an IANA Enterprise Numbers are assigned by IANA and managed through an IANA
registry [RFC2578]. registry [RFC2578].
Vendor Specific Additional parameters Vendor Specific Additional parameters
There can be potentially additional parameters characterizing the There can be potentially additional parameters characterizing the
vendor specific modulation. vendor specific modulation.
4.3. Input FEC Type List Sub-Sub-TLV 4.3. Input FEC Type List Sub-Sub-TLV
This sub-TLV contains a list of acceptable FEC types. This sub-sub-TLV contains a list of acceptable FEC types.
Type := Input FEC Type field List Type := Input FEC Type field List
Value:= A list of FEC type Fields Value:= A list of FEC type Fields
4.3.1. FEC Type Field 4.3.1. FEC Type Field
The FEC type Field may consist of two different formats of fields: a The FEC type Field may consist of two different formats of fields: a
standard FEC field or a vendor specific FEC field. Both start with standard FEC field or a vendor specific FEC field. Both start with
the same 32 bit header shown below. the same 32 bit header shown below.
skipping to change at page 18, line 32 skipping to change at page 19, line 32
Enterprise Numbers are assigned by IANA and managed through an IANA Enterprise Numbers are assigned by IANA and managed through an IANA
registry [RFC2578]. registry [RFC2578].
Vendor Specific Additional FEC parameters Vendor Specific Additional FEC parameters
There can be potentially additional parameters characterizing the There can be potentially additional parameters characterizing the
vendor specific FEC. vendor specific FEC.
4.4. Input Bit Range List Sub-Sub-TLV 4.4. Input Bit Range List Sub-Sub-TLV
This sub-TLV contains a list of acceptable input bit rate ranges. This sub-sub-TLV contains a list of acceptable input bit rate ranges.
Type := Input Bit Range List Type := Input Bit Range List
Value:= A list of Bit Range Fields Value:= A list of Bit Range Fields
4.4.1. Bit Range Field 4.4.1. Bit Range Field
The bit rate range list sub-TLV makes use of the following bit rate The bit rate range list sub-TLV makes use of the following bit rate
range field: range field:
skipping to change at page 19, line 35 skipping to change at page 20, line 35
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: : : : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+ Bit Range Field #M +-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+ Bit Range Field #M +-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
4.5. Input Client Signal List Sub-Sub-TLV 4.5. Input Client Signal List Sub-Sub-TLV
This sub-TLV contains a list of acceptable input client signal types. This sub-sub-TLV contains a list of acceptable input client signal
types.
Type := Input Client Signal List Type := Input Client Signal List
Value:= A list of GPIDs Value:= A list of GPIDs
The acceptable client signal list sub-TLV is a list of Generalized The acceptable client signal list sub-TLV is a list of Generalized
Protocol Identifiers (GPIDs). GPIDs are assigned by IANA and many are Protocol Identifiers (GPIDs). GPIDs are assigned by IANA and many are
defined in [RFC3471] and [RFC4328]. defined in [RFC3471] and [RFC4328].
0 1 2 3 0 1 2 3
skipping to change at page 20, line 19 skipping to change at page 21, line 19
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: | : : | :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| GPID #N | | | GPID #N | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where the number of GPIDs is an integer greater than or equal to one. Where the number of GPIDs is an integer greater than or equal to one.
4.6. Processing Capability List Sub-Sub-TLV 4.6. Processing Capability List Sub-Sub-TLV
This sub-TLV contains a list of resource block processing This sub-sub-TLV contains a list of resource block processing
capabilities. capabilities.
Type := Processing Capabilities List Type := Processing Capabilities List
Value:= A list of Processing Capabilities Fields Value:= A list of Processing Capabilities Fields
The processing capability list sub-TLV is a list of WSON network The processing capability list sub-TLV is a list of WSON network
element (NE) that can perform signal processing functions including: element (NE) that can perform signal processing functions including:
1. Number of Resources within the block 1. Number of Resources within the block
skipping to change at page 22, line 18 skipping to change at page 23, line 18
C=2: Selective Regeneration Point C=2: Selective Regeneration Point
Note that when the capability of regenerator is indicated to be Note that when the capability of regenerator is indicated to be
Selective Regeneration Pools, regeneration pool properties such as Selective Regeneration Pools, regeneration pool properties such as
ingress and egress restrictions and availability need to be ingress and egress restrictions and availability need to be
specified. This encoding is to be determined in the later revision. specified. This encoding is to be determined in the later revision.
4.7. Output Modulation Format List Sub-Sub-TLV 4.7. Output Modulation Format List Sub-Sub-TLV
This sub-TLV contains a list of available output modulation formats. This sub-sub-TLV contains a list of available output modulation
formats.
Type := Output Modulation Format List Type := Output Modulation Format List
Value:= A list of Modulation Format Fields Value:= A list of Modulation Format Fields
4.8. Output FEC Type List Sub-Sub-TLV 4.8. Output FEC Type List Sub-Sub-TLV
This sub-TLV contains a list of output FEC types. This sub-sub-TLV contains a list of output FEC types.
Type := Output FEC Type field List Type := Output FEC Type field List
Value:= A list of FEC type Fields Value:= A list of FEC type Fields
5. Security Considerations 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.
 End of changes. 23 change blocks. 
60 lines changed or deleted 78 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/