draft-ietf-ccamp-rwa-wson-encode-04.txt   draft-ietf-ccamp-rwa-wson-encode-05.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 2010 D. Li Expires: January 2011 D. Li
Huawei Huawei
W. Imajuku W. Imajuku
NTT NTT
February 18, 2010 July 12, 2010
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-04.txt draft-ietf-ccamp-rwa-wson-encode-05.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 August 18, 2010. This Internet-Draft will expire on January 12, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 43 skipping to change at page 2, line 43
information to a path computation element (PCE). information to a path computation element (PCE).
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119 [RFC2119]. document are to be interpreted as described in RFC-2119 [RFC2119].
Table of Contents Table of Contents
1. Introduction...................................................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
2. Terminology....................................................5 1.1.5. Changes from 04 draft......................... 5
3. WSON Encoding Usage Recommendations............................6 2. Terminology ......................................... 5
3.1. WSON Node TLV.............................................6 3. WSON Encoding Usage Recommendations...................... 6
3.2. WSON Dynamic Node TLV.....................................6 3.1. WSON Node TLV.................................... 6
4. Resource Accessibility/Availability............................6 3.2. WSON Dynamic Node TLV............................. 6
4.1. Resource Block Accessibility Sub-TLV......................8 4. Resource Accessibility/Availability...................... 7
4.2. Resource Wavelength Constraints Sub-TLV..................10 4.1. Block Accessibility Sub-TLV........................ 8
4.3. Resource Block Pool State Sub-TLV........................10 4.2. Wavelength Constraints Sub-TLV..................... 10
5. Resource Properties Encoding..................................12 4.3. Block Pool State Sub-TLV.......................... 10
5.1. Resource Block Information Sub-TLV.......................12 4.4. Block Shared Access Wavelength Availability sub-TLV ... 12
5.2. Input Modulation Format List Sub-Sub-TLV.................13 5. Resource Properties Encoding .......................... 13
5.2.1. Modulation Format Field.............................13 5.1. Resource Block Information Sub-TLV ................. 13
5.3. Input FEC Type List Sub-Sub-TLV..........................15 5.2. Input Modulation Format List Sub-Sub-TLV ............ 14
5.3.1. FEC Type Field......................................16 5.2.1. Modulation Format Field ...................... 15
5.4. Input Bit Range List Sub-Sub-TLV.........................18 5.3. Input FEC Type List Sub-Sub-TLV.................... 16
5.4.1. Bit Range Field.....................................18 5.3.1. FEC Type Field.............................. 17
5.5. Input Client Signal List Sub-Sub-TLV.....................19 5.4. Input Bit Range List Sub-Sub-TLV................... 19
5.6. Processing Capability List Sub-Sub-TLV...................20 5.4.1. Bit Range Field............................. 19
5.6.1. Processing Capabilities Field.......................20 5.5. Input Client Signal List Sub-Sub-TLV................ 20
5.7. Output Modulation Format List Sub-Sub-TLV................22 5.6. Processing Capability List Sub-Sub-TLV.............. 21
5.8. Output FEC Type List Sub-Sub-TLV.........................22 5.6.1. Processing Capabilities Field ................. 21
6. Security Considerations.......................................22 5.7. Output Modulation Format List Sub-Sub-TLV............ 23
7. IANA Considerations...........................................23 5.8. Output FEC Type List Sub-Sub-TLV................... 23
8. Acknowledgments...............................................23 6. Security Considerations............................... 23
APPENDIX A: Encoding Examples....................................24 7. IANA Considerations.................................. 24
A.1. Wavelength Converter Accessibility Sub-TLV...............24 8. Acknowledgments..................................... 24
A.2. Wavelength Conversion Range Sub-TLV......................25 APPENDIX A: Encoding Examples............................ 25
A.3. An OEO Switch with DWDM Optics...........................26 A.1. Wavelength Converter Accessibility Sub-TLV........... 25
9. References....................................................29 A.2. Wavelength Conversion Range Sub-TLV................. 26
9.1. Normative References.....................................29 A.3. An OEO Switch with DWDM Optics..................... 27
9.2. Informative References...................................29 9. References......................................... 30
10. Contributors.................................................31 9.1. Normative References............................. 30
Authors' Addresses...............................................31 9.2. Informative References........................... 30
Intellectual Property Statement..................................32 10. Contributors....................................... 31
Disclaimer of Validity...........................................33 Authors' Addresses..................................... 32
Intellectual Property Statement .......................... 33
Disclaimer of Validity.................................. 33
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 22 skipping to change at page 5, line 24
Added bidirectional connectivity matrix example. Added simple link Added bidirectional connectivity matrix example. Added simple link
set example. Edited examples for consistency. set example. Edited examples for consistency.
1.1.4. Changes from 03 draft 1.1.4. Changes from 03 draft
Removed encodings for general concepts to [Gen-Encode]. Removed encodings for general concepts to [Gen-Encode].
Added in WSON signal compatibility and processing capability Added in WSON signal compatibility and processing capability
information encoding. information encoding.
1.1.5. Changes from 04 draft
Added encodings to deal with access to resource blocks via shared
fiber.
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 36 skipping to change at page 6, line 40
in section 4.1. ), and a resource pool wavelength constraint sub-TLV in section 4.1. ), and a resource pool wavelength constraint sub-TLV
(<ResourceWaveConstraints> in section 4.2. ). (<ResourceWaveConstraints> in section 4.2. ).
3.2. WSON Dynamic Node TLV 3.2. WSON Dynamic Node TLV
If the protocol supports the separation of dynamic information from If the protocol supports the separation of dynamic information from
relatively static information then the wavelength converter pool relatively static information then the wavelength converter pool
state can be separated from the general Node TLV into a dynamic Node state can be separated from the general Node TLV into a dynamic Node
TLV as follows. TLV as follows.
<NodeInfoDynamic> ::= <NodeID> [<RBPoolState>] <NodeInfoDynamic> ::= <NodeID>
[<RBPoolState>][<BlockSharedAccessWavelengthAvailability>...]
Where the resource pool state sub-TLV <RBPoolState> is defined in Where the resource pool state sub-TLV <RBPoolState> is defined in
section 4.3. Note that currently the only dynamic information modeled section 4.3. Note that currently the only dynamic information modeled
with a node is associated with the status of the wavelength converter with a node is associated with the status of the wavelength converter
pool. pool.
4. Resource Accessibility/Availability 4. Resource 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 in include the following and availability of resource blocks. These in include the following
skipping to change at page 8, line 17 skipping to change at page 8, line 24
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.
4.1. Resource Block Accessibility Sub-TLV 4.1. 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 10, line 5 skipping to change at page 10, line 5
The Link Set Field is defined in [Gen-Encode]. The Link Set Field is defined in [Gen-Encode].
Note that the direction parameter within the Link Set Field is used Note that the direction parameter within the Link Set Field is used
to indicate whether the link set is an ingress or egress link set, to indicate whether the link set is an ingress or egress link set,
and the bidirectional value for this parameter is not permitted in and the bidirectional value for this parameter is not permitted in
this sub-TLV. this sub-TLV.
See Appendix A.1 for an illustration of this encoding. See Appendix A.1 for an illustration of this encoding.
4.2. Resource Wavelength Constraints Sub-TLV 4.2. Wavelength Constraints Sub-TLV
Resources, such as wavelength converters, etc., may have a limited Resources, such as wavelength converters, etc., may have a limited
input or output wavelength ranges. Additionally, due to the structure input or output wavelength ranges. Additionally, due to the structure
of the optical system not all wavelengths can necessarily reach or of the optical system not all wavelengths can necessarily reach or
leave all the resources. These properties are described by using one leave all the resources. These properties are described by using one
or more resource wavelength restrictions sub-TLVs as defined below: or more resource wavelength restrictions sub-TLVs as defined below:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 10, line 41 skipping to change at page 10, line 41
Input Wavelength Set Field: Input Wavelength Set Field:
Indicates the wavelength input restrictions of the RBs in the Indicates the wavelength input restrictions of the RBs in the
corresponding RB set. corresponding RB set.
Output Wavelength Set Field: Output Wavelength Set Field:
Indicates the wavelength output restrictions of RBs in the Indicates the wavelength output restrictions of RBs in the
corresponding RB set. corresponding RB set.
4.3. Resource Block Pool State Sub-TLV 4.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 a resource is encoded as either a list of 16 bit
integer values or a bit map indicating whether a single resource is integer values or a bit map indicating whether a single resource is
available or in use. This information can be relatively dynamic, available or in use. This information can be relatively dynamic,
i.e., can change when a connection is established or torn down. 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 |
skipping to change at page 12, line 18 skipping to change at page 12, line 18
RB Usage state: Variable Length but must be a multiple of 4 byes. RB Usage state: Variable Length but must be a multiple of 4 byes.
Each bit indicates the usage status of one RB with 0 indicating the Each bit indicates the usage status of one RB with 0 indicating the
RB is available and 1 indicating the RB is in used. The sequence of RB is available and 1 indicating the RB is in used. The sequence of
the bit map is ordered according to the RB Set field with this sub- the bit map is ordered according to the RB Set field with this sub-
TLV. TLV.
Padding bits: Variable Length Padding bits: Variable Length
4.4. Block Shared Access Wavelength Availability sub-TLV
Resources blocks may be accessed via a shared fiber. If this is the
case then wavelength availability on these shared fiber is needed to
understand resource availability.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Resource Block ID |I|E| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Ingress Available Wavelength Set Field |
: :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Egress Available Wavelength Set Field |
: :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Resource Block ID:
The 16 bit integer used to identify a particular resource block.
I bit:
Indicates whether the ingress available wavelength set field is
included (1) or not (0).
E bit:
Indicates whether the egress available wavelength set field is
included (1) or not (0).
Ingress Available Wavelength Set Field:
Indicates the wavelengths currently available (not being used) on the
ingress fiber to this resource block.
Egress Available Wavelength Set Field:
Indicates the wavelengths currently available (not being used) on the
egress fiber from this resource block.
5. Resource Properties Encoding 5. Resource Properties Encoding
Within a WSON network element (NE) there may be resources with signal Within a WSON network element (NE) there may be resources with signal
compatibility constraints. Such resources typically come in "blocks" compatibility constraints. 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 focus on the signal electro optical switch. In this section we primarily focus on the
compatibility and processing properties of such a resource block, signal compatibility and processing properties of such a resource
i.e., <ResourceBlockInfo> of section 3.1. the accessibility aspects block, i.e., <ResourceBlockInfo> of section 3.1. the accessibility
of a resource in a shared pool were encoded in the previous section. aspects of a resource in a shared pool, except for the shared access
indicators, were encoded in the previous section.
The fundamental properties of a resource block, such as a regenerator The fundamental properties of a resource block, such as a regenerator
or wavelength converter, are: or wavelength converter, are:
(a)Input constraints (modulation, FEC, bit rate, GPID) (a)Input constraints (shared ingress, modulation, FEC, bit rate,
GPID)
(b)Processing capabilities (number of resources in a block, (b)Processing capabilities (number of resources in a block,
regeneration, performance monitoring, vendor specific) regeneration, performance monitoring, vendor specific)
(c)Output Constraints (modulation, FEC) (c)Output Constraints (shared egress, modulation, FEC)
5.1. Resource Block Information Sub-TLV 5.1. Resource Block Information Sub-TLV
Resource Block descriptor sub-TLVs are used to convey relatively Resource Block descriptor sub-TLVs are used to convey relatively
static information about individual resource blocks including the static information about individual resource blocks including the
resource block properties of section 3. and the number of resources resource block properties of section 3. and the number of resources
in a block. in a block.
This sub-TLV has the following format: This sub-TLV has the following format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB Set Field | | RB Set Field |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Shared Ingress Indicator | Shared Egress Indicator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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-TLV (opt) |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Bit Rate Range List Sub-Sub-TLV (opt) | | Input Bit Rate Range List Sub-Sub-TLV (opt) |
skipping to change at page 13, line 33 skipping to change at page 14, line 35
| 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) |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output FEC Type List Sub-Sub-TLV (opt) | | Output FEC Type List Sub-Sub-TLV (opt) |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where the shared ingress/egress indicator is set to 1 if the resource
blocks identified in the RB set field utilized a shared fiber for
ingress/egress access and set to 0 otherwise.
5.2. Input Modulation Format List Sub-Sub-TLV 5.2. Input Modulation Format List Sub-Sub-TLV
This sub-TLV contains a list of acceptable input modulation formats. This 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
5.2.1. Modulation Format Field 5.2.1. Modulation Format Field
Two different types of modulation format fields are defined: a Two different types of modulation format fields are defined: a
standard modulation field and a vendor specific modulation field. standard modulation field and a vendor specific modulation field.
Both start with the same 32 bit header shown below. Both start with the same 32 bit header shown below.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|S|I| Modulation ID | Length | |S|I| Modulation ID | Length |
skipping to change at page 23, line 8 skipping to change at page 24, line 8
However, other documents that make use of these encodings within However, other documents that make use of these encodings within
protocol extensions need to consider the issues and risks associated protocol extensions need to consider the issues and risks associated
with, inspection, interception, modification, or spoofing of any of with, inspection, interception, modification, or spoofing of any of
this information. It is expected that any such documents will this information. It is expected that any such documents will
describe the necessary security measures to provide adequate describe the necessary security measures to provide adequate
protection. protection.
7. IANA Considerations 7. IANA Considerations
TBD. Once our approach is finalized we may need identifiers for the TBD. Once our approach is finalized we may need identifiers for the
various TLVs and sub-TLVs. various sub-sub-TLVs.
8. Acknowledgments 8. Acknowledgments
This document was prepared using 2-Word-v2.0.template.dot. This document was prepared using 2-Word-v2.0.template.dot.
APPENDIX A: Encoding Examples APPENDIX A: Encoding Examples
A.1. Wavelength Converter Accessibility Sub-TLV A.1. Wavelength Converter Accessibility Sub-TLV
Example: Example:
skipping to change at page 27, line 29 skipping to change at page 28, line 29
| | | |
/| | | +-------------+ +------+ /| | | +-------------+ +------+
/D+--->| |--->|Tunable Laser|-->| | /D+--->| |--->|Tunable Laser|-->| |
+ e+--->| | +-------------+ | C | + e+--->| | +-------------+ | C |
========>| M| | | ... | o |========> ========>| M| | | ... | o |========>
Port I3 + u+--->| | +-------------+ | m | Port E3 Port I3 + u+--->| | +-------------+ | m | Port E3
\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 switch. constraints of the receivers, transmitters and the electronic switch.
The resource availability information, although very simple, tells us The resource availability information, although very simple, tells us
that all signals must traverse the electronic fabric (fixed 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>:
skipping to change at page 29, line 12 skipping to change at page 30, line 12
: (All egress links connect to resource) : : (All egress links connect to resource) :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
MIB", RFC 2863, June 2000. "Structure of Management Information Version 2 (SMIv2)",
STD 58, RFC 2578, April 1999.
[RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Functional Description", RFC 3471, (GMPLS) Signaling Functional Description", RFC 3471,
January 2003. January 2003.
[RFC4328] Papadimitriou, D., Ed., "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Extensions for G.709 Optical
Transport Networks Control", RFC 4328, January 2006.
[G.694.1] ITU-T Recommendation G.694.1, "Spectral grids for WDM [G.694.1] ITU-T Recommendation G.694.1, "Spectral grids for WDM
applications: DWDM frequency grid", June, 2002. applications: DWDM frequency grid", June, 2002.
[RFC4202] Kompella, K., Ed., and Y. Rekhter, Ed., "Routing Extensions
in Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 4202, October 2005
[RFC4203] Kompella, K., Ed., and Y. Rekhter, Ed., "OSPF Extensions in
Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 4203, October 2005.
9.2. Informative References 9.2. Informative References
[G.694.1] ITU-T Recommendation G.694.1, Spectral grids for WDM [G.694.1] ITU-T Recommendation G.694.1, Spectral grids for WDM
applications: DWDM frequency grid, June 2002. applications: DWDM frequency grid, June 2002.
[G.694.2] ITU-T Recommendation G.694.2, Spectral grids for WDM [G.694.2] ITU-T Recommendation G.694.2, Spectral grids for WDM
applications: CWDM wavelength grid, December 2003. applications: CWDM wavelength grid, December 2003.
[Gen-Encode] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "General [Gen-Encode] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "General
Network Element Constraint Encoding for GMPLS Controlled Network Element Constraint Encoding for GMPLS Controlled
Networks", work in progress: draft-ietf-ccamp-general-ext- Networks", work in progress: draft-ietf-ccamp-general-ext-
encode-00.txt. encode-00.txt.
[Otani] T. Otani, H. Guo, K. Miyazaki, D. Caviglia, "Generalized [Otani] T. Otani, H. Guo, K. Miyazaki, D. Caviglia, "Generalized
Labels for G.694 Lambda-Switching Capable Label Switching Labels for G.694 Lambda-Switching Capable Label Switching
Routers", work in progress: draft-ietf-ccamp-gmpls-g-694- Routers", work in progress: draft-ietf-ccamp-gmpls-g-694-
lambda-labels. lambda-labels.
[RFC5307] Kompella, K., Ed., and Y. Rekhter, Ed., "IS-IS Extensions
in Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 5307, October 2008.
[Switch] G. Bernstein, Y. Lee, A. Gavler, J. Martensson, " Modeling
WDM Wavelength Switching Systems for Use in GMPLS and Automated
Path Computation", Journal of Optical Communications and
Networking, vol. 1, June, 2009, pp. 187-195.
[WSON-Frame] Y. Lee, G. Bernstein, W. Imajuku, "Framework for GMPLS [WSON-Frame] Y. Lee, G. Bernstein, W. Imajuku, "Framework for GMPLS
and PCE Control of Wavelength Switched Optical Networks", and PCE Control of Wavelength Switched Optical Networks",
work in progress: draft-ietf-ccamp-wavelength-switched- work in progress: draft-ietf-ccamp-wavelength-switched-
framework, Marh 2009. framework, Marh 2009.
[WSON-Info] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "Routing and [WSON-Info] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "Routing and
Wavelength Assignment Information Model for Wavelength Wavelength Assignment Information Model for Wavelength
Switched Optical Networks", work in progress: draft-ietf- Switched Optical Networks", work in progress: draft-ietf-
ccamp-rwa-info, March 2009. ccamp-rwa-info, March 2009.
[PCEP] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation
Element (PCE) communication Protocol (PCEP) - Version 1",
RFC5440.
10. Contributors 10. Contributors
Diego Caviglia Diego Caviglia
Ericsson Ericsson
Via A. Negrone 1/A 16153 Via A. Negrone 1/A 16153
Genoa Italy Genoa Italy
Phone: +39 010 600 3736 Phone: +39 010 600 3736
Email: diego.caviglia@(marconi.com, ericsson.com) Email: diego.caviglia@(marconi.com, ericsson.com)
 End of changes. 24 change blocks. 
81 lines changed or deleted 122 lines changed or added

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