draft-ietf-ccamp-wson-signaling-07.txt   draft-ietf-ccamp-wson-signaling-08.txt 
Network Working Group G. Bernstein Network Working Group G. Bernstein
Internet Draft Grotto Networking Internet Draft Grotto Networking
Intended status: Standards Track Sugang Xu Updates: 6205 Sugang Xu
NICT Intended status: Standards Track NICT
Expires: September 2014 Y.Lee Y.Lee
Huawei Huawei
G. Martinelli Expires: November 2015 G. Martinelli
Cisco Cisco
Hiroaki Harai Hiroaki Harai
NICT NICT
March 5, 2014 July 3, 2014
Signaling Extensions for Wavelength Switched Optical Networks Signaling Extensions for Wavelength Switched Optical Networks
draft-ietf-ccamp-wson-signaling-07.txt draft-ietf-ccamp-wson-signaling-08.txt
Abstract Abstract
This memo provides extensions to Generalized Multi-Protocol Label This memo provides extensions to Generalized Multi-Protocol Label
Switching (GMPLS) signaling for control of wavelength switched Switching (GMPLS) signaling for control of Wavelength Switched
optical networks (WSON). Such extensions are applicable in WSONs Optical Networks (WSON). Such extensions are applicable in WSONs
under a number of conditions including: (a) when optional under a number of conditions including: (a) when optional
processing, such as regeneration, must be configured to occur at processing, such as regeneration, must be configured to occur at
specific nodes along a path, (b) where equipment must be configured specific nodes along a path, (b) where equipment must be configured
to accept an optical signal with specific attributes, or (c) where to accept an optical signal with specific attributes, or (c) where
equipment must be configured to output an optical signal with equipment must be configured to output an optical signal with
specific attributes. In addition this memo provides mechanisms to specific attributes. In addition this memo provides mechanisms to
support distributed wavelength assignment with choice in distributed support distributed wavelength assignment with choice in distributed
wavelength assignment algorithms. These extensions build on previous wavelength assignment algorithms. These extensions build on previous
work for the control of lambda and G.709 based networks. This work for the control of lambda and G.709 based networks, i.e. update
document updates [RFC6205] as make it applicable to WSON-LSC capable RFC6205, to make it applicable to WSON-LSC capable equipment.
equipment.
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 2, line 4 skipping to change at page 1, line 48
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.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on September 5, 2014. This Internet-Draft will expire on January 3, 2007.
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
skipping to change at page 2, line 39 skipping to change at page 2, line 36
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 [RFC2119]. document are to be interpreted as described in [RFC2119].
Table of Contents Table of Contents
1. Introduction...................................................3 1. Introduction...................................................3
2. Terminology....................................................3 2. Terminology....................................................3
3. Requirements for WSON Signaling................................4 3. Requirements for WSON Signaling................................4
3.1. WSON Signal Characterization..............................4 3.1. WSON Signal Characterization..............................4
3.2. Per LSP Network Element Processing Configuration..........5 3.2. Per Node Processing Configuration.........................5
3.3. Bidirectional WSON LSPs...................................6 3.3. Bidirectional WSON LSPs...................................6
3.4. Distributed Wavelength Assignment Selection Method........6 3.4. Distributed Wavelength Assignment Selection Method........6
3.5. Optical Impairments.......................................6 3.5. Optical Impairments.......................................6
4. WSON Signal Traffic Parameters, Attributes and Processing......6 4. WSON Signal Traffic Parameters, Attributes and Processing......6
4.1. Traffic Parameters for Optical Tributary Signals..........7 4.1. Traffic Parameters for Optical Tributary Signals..........7
4.2. WSON Processing HOP Attribute TLV Encoding................7 4.2. WSON Processing HOP Attribute TLV Encoding................7
4.3. Signal Attributes and Processing Capabilities.............8 4.3. Resource Block Information Sub-TLV........................8
4.4. Wavelength Assignment Method Selection TLV Encoding.......9 4.4. Wavelength Selection Sub-TLV..............................9
5. Security Considerations.......................................11
5. Security Considerations.......................................10 6. IANA Considerations...........................................12
6. IANA Considerations...........................................10 7. Acknowledgments...............................................13
7. Acknowledgments...............................................11 8. References....................................................14
8. References....................................................12 8.1. Normative References.....................................14
8.1. Normative References.....................................12 8.2. Informative References...................................15
8.2. Informative References...................................13 Author's Addresses...............................................16
Author's Addresses...............................................15 Intellectual Property Statement..................................17
Intellectual Property Statement..................................16 Disclaimer of Validity...........................................18
Disclaimer of Validity...........................................17
1. Introduction 1. Introduction
This memo provides extensions to Generalized Multi-Protocol Label This memo provides extensions to Generalized Multi-Protocol Label
Switching (GMPLS) signaling for control of wavelength switched Switching (GMPLS) signaling for control of Wavelength Switched
optical networks (WSON). Fundamental extensions are given to permit Optical Networks (WSON). Fundamental extensions are given to permit
simultaneous bidirectional wavelength assignment while more advanced simultaneous bidirectional wavelength assignment while more advanced
extensions are given to support the networks described in [RFC6163] extensions are given to support the networks described in [RFC6163]
which feature connections requiring configuration of input, output, which feature connections requiring configuration of input, output,
and general signal processing capabilities at a node along a LSP. and general signal processing capabilities at a node along a Label
Switched Path (LSP).
These extensions build on previous work for the control of lambda These extensions build on previous work for the control of lambda
and G.709 based networks [RFC3471]. and G.709 based networks. This document updates [RFC6205] as make it
applicable to WSON-LSC capable equipment.
Related references with this document are [WSON-info] that provides Related references with this document are [WSON-Info] that provides
a high-level information model and and [WSON-Encode] that provides a high-level information model and and [WSON-Encode] that provides
common encodings that can be applicable to other protocol extensions common encodings that can be applicable to other protocol extensions
such as routing. such as routing.
2. Terminology 2. Terminology
CWDM: Coarse Wavelength Division Multiplexing. CWDM: Coarse Wavelength Division Multiplexing.
DWDM: Dense Wavelength Division Multiplexing. DWDM: Dense Wavelength Division Multiplexing.
skipping to change at page 4, line 42 skipping to change at page 4, line 39
multiplexers/demultiplexer (e.g. AWG), optical transponder, etc., multiplexers/demultiplexer (e.g. AWG), optical transponder, etc.,
which are employed to transmit/terminate the optical signals for which are employed to transmit/terminate the optical signals for
data transmission. data transmission.
3. Requirements for WSON Signaling 3. Requirements for WSON Signaling
The following requirements for GMPLS based WSON signaling are in The following requirements for GMPLS based WSON signaling are in
addition to the functionality already provided by existing GMPLS addition to the functionality already provided by existing GMPLS
signaling mechanisms. signaling mechanisms.
3.1. WSON Signal Characterization 3.1. WSON Signal Characterization
WSON signaling needs to convey sufficient information characterizing WSON signaling needs to convey sufficient information characterizing
the signal to allow systems along the path to determine the signal to allow systems along the path to determine
compatibility and perform any required local configuration. Examples compatibility and perform any required local configuration. Examples
of such systems include intermediate nodes (ROADMs, OXCs, Wavelength of such systems include intermediate nodes (ROADMs, OXCs, Wavelength
converters, Regenerators, OEO Switches, etc...), links (WDM systems) converters, Regenerators, OEO Switches, etc...), links (WDM systems)
and end systems (detectors, demodulators, etc...). The details of and end systems (detectors, demodulators, etc...). The details of
any local configuration processes are out of the scope of this any local configuration processes are out of the scope of this
document. document.
skipping to change at page 5, line 30 skipping to change at page 5, line 28
traverses a network with regenerators, OEO switches, or wavelength traverses a network with regenerators, OEO switches, or wavelength
converters. These parameters are summarized in the Optical Interface converters. These parameters are summarized in the Optical Interface
Class as defined in the [WSON-Info] and the assumption is that a Class as defined in the [WSON-Info] and the assumption is that a
class always includes signal compatibility information. class always includes signal compatibility information.
An ability to control wavelength conversion already exists in GMPLS An ability to control wavelength conversion already exists in GMPLS
signaling along with the ability to share client signal type signaling along with the ability to share client signal type
information (G-PID). In addition, bit rate is a standard GMPLS information (G-PID). In addition, bit rate is a standard GMPLS
signaling traffic parameter. It is referred to as Bandwidth Encoding signaling traffic parameter. It is referred to as Bandwidth Encoding
in [RFC3471]. in [RFC3471].
3.2. Per LSP Network Element Processing Configuration 3.2. Per Node Processing Configuration
In addition to configuring a network element (NE) along an LSP to In addition to configuring a node along an LSP to input or output a
input or output a signal with specific attributes, we may need to signal with specific attributes, we may need to signal the node to
signal the NE to perform specific processing, such as 3R perform specific processing, such as 3R regeneration, on the signal
regeneration, on the signal at a particular NE. In [RFC6163] we at a particular NE. [RFC6163] discussed three types of processing:
discussed three types of processing not currently covered by GMPLS:
(A) Regeneration (possibly different types) (A) Regeneration (possibly different types)
(B) Fault and Performance Monitoring (B) Fault and Performance Monitoring
(C) Attribute Conversion (C) Attribute Conversion
The extensions here MUST provide for the configuration of these The extensions here provide for the configuration of these types of
types of processing at nodes along an LSP. processing at nodes along an LSP.
3.3. Bidirectional WSON LSPs 3.3. Bidirectional WSON LSPs
WSON signaling can support LSP setup consistent with the wavelength WSON signaling can support LSP setup consistent with the wavelength
continuity constraint for bidirectional connections. The following continuity constraint for bidirectional connections. The following
cases need to be separately supported: cases need to be separately supported:
(a) Where the same wavelength is used for both upstream and (a) Where the same wavelength is used for both upstream and
downstream directions downstream directions
(b) Where different wavelengths can be used for both upstream and (b) Where different wavelengths can be used for both upstream and
downstream directions. downstream directions.
This document will review current GMPLS bidirectional solutions This document will review existing GMPLS bidirectional solutions
according to WSON case. according to WSON case.
3.4. Distributed Wavelength Assignment Selection Method 3.4. Distributed Wavelength Assignment Selection Method
WSON signaling can support the selection of a specific distributed WSON signaling can support the selection of a specific distributed
wavelength assignment method. wavelength assignment method.
This method is beneficial in cases of equipment failure, etc., where This method is beneficial in cases of equipment failure, etc., where
fast provisioning used in quick recovery is critical to protect fast provisioning used in quick recovery is critical to protect
carriers/users against system loss. This requires efficient carriers/users against system loss. This requires efficient
signaling which supports distributed wavelength assignment, in signaling which supports distributed wavelength assignment, in
particular when the centralized wavelength assignment capability is particular when the centralized wavelength assignment capability is
not available. not available.
As discussed in the [RFC6163] different computational approaches for As discussed in the [RFC6163] different computational approaches for
wavelength assignment are available. One method is the use of wavelength assignment are available. One method is the use of
distributed wavelength assignment. This feature would allow the distributed wavelength assignment. This feature would allow the
specification of a particular approach when more than one is specification of a particular approach when more than one is
implemented in the systems along the path. implemented in the systems along the path.
3.5. Optical Impairments 3.5. Optical Impairments
This draft does not address signaling information related to optical This draft does not address signaling information related to optical
impairments. impairments.
4. WSON Signal Traffic Parameters, Attributes and Processing 4. WSON Signal Traffic Parameters, Attributes and Processing
As discussed in [RFC6163] single channel optical signals used in As discussed in [RFC6163] single channel optical signals used in
WSONs are called "optical tributary signals" and come in a number of WSONs are called "optical tributary signals" and come in a number of
classes characterized by modulation format and bit rate. Although classes characterized by modulation format and bit rate. Although
WSONs are fairly transparent to the signals they carry, to ensure WSONs are fairly transparent to the signals they carry, to ensure
compatibility amongst various networks devices and end systems it compatibility amongst various networks devices and end systems, it
can be important to include key lightpath characteristics as traffic can be important to include key lightpath characteristics as traffic
parameters in signaling [RFC6163]. parameters in signaling [RFC6163].
LSPs signaled through extensions provided in this document MUST LSPs signaled through extensions provided in this document MUST
apply the following signaling parameters: apply the following signaling parameters:
. Switching Capability = WSON-LSC ([WSON-OSPF]). . Switching Capability = WSON-LSC ([WSON-OSPF]).
. Encoding Type = Lambda ([RFC3471]) . Encoding Type = Lambda ([RFC3471])
. Label Format = as defined in [RFC6205] . Label Format = as defined in [RFC6205]
[RFC6205] defines the label format as applicable to LSC capable [RFC6205] defines the label format as applicable to LSC capable
device. This document extend [RFC6205] as make its label format device. This document extends [RFC6205] as make its label format
applicable also to WSON-LSC capable devices. applicable also to WSON-LSC capable devices.
4.1. Traffic Parameters for Optical Tributary Signals 4.1. Traffic Parameters for Optical Tributary Signals
In [RFC3471] we see that the G-PID (client signal type) and bit rate In [RFC3471] we see that the G-PID (client signal type) and bit rate
(byte rate) of the signals are defined as parameters and in (byte rate) of the signals are defined as parameters and in
[RFC3473] they are conveyed Generalized Label Request object and the [RFC3473] they are conveyed Generalized Label Request object and the
RSVP SENDER_TSPEC/FLOWSPEC objects respectively. RSVP SENDER_TSPEC/FLOWSPEC objects respectively.
4.2. WSON Processing HOP Attribute TLV Encoding 4.2. WSON Processing HOP Attribute TLV Encoding
Section 3.2. provided the requirements for signaling to indicate to Section 3.2. provided the requirements for signaling to indicate to
a particular NE along an LSP what type of processing to perform on a particular node along an LSP what type of processing to perform on
an optical signal or how to configure that NE to accept or transmit an optical signal or how to configure that node to accept or
an optical signal with particular attributes. transmit an optical signal with particular attributes.
To target a specific node, this section defines a WSON_Processing To target a specific node, this section defines a WSON Processing
object as part of the LSP_REQUIRED_ATTRIBUTE and follows procedures HOP Attribute TLV, which is carried in the subobjects defined in
defined in [RSVP-RO]. [RSVP-RO]. The Type value of the WSON Processing HOP Attribute TLV
is TBD by IANA.
The content of this TLV is defined in the subsequent sections. (See The contents of this TLV is defined in the subsequent sections.
Section 4.3 for <RBInformation> TLV and Section 4.4 for Section 4.3 for ResourceBlockInfo sub-TLV and Section 4.4 for
<WavelengthSelection> TLV, respectively.) WavelengthSelection sub-TLV, respectively. The TLV can be
represented in Reduced Backus-Naur Form (RBNF) [RFC5511] syntax as:
<WSON_Processing HOP Attribute> ::= <RBInformation> <WSON Processing HOP Attribute> ::= < ResourceBlockInfo>
[<RBInformation>] [<ResourceBlockInfo>] <WavelengthSelection>
The WSON Processing carries sub-TLVs of the same format as a HOP The WSON Processing HOP Attribute TLV is a type of a HOP Attributes
Attributes TLV, as defined in [RSVP-RO]. TLV, as defined in [RSVP-RO]. If a receiving node does not recognize
a sub-TLV, it will follow the procedure defined in [RFC5420], i.e.,
it MUST generate a PathErr with a new error value of the existing
Error Code "Unknown Attributes TLV (Sub-codes - 29)".
4.3. Signal Attributes and Processing Capabilities 4.3. Resource Block Information Sub-TLV
The [WSON-Encode] already provides all necessary definitions and The Resource block information , or ResourceBlockInfo, sub-TLV
encoding for WSON information required for signaling. In particular, contains a list of available Optical Interface Classes and
the Resource block information sub-TLV contains, among others, a processing capabilities.
list of available Optical Interface Classes and processing
capabilities.
<RBInformation> is defined in Section 4.1 of [WSON-Encode]. The format of the ResourceBlockInfo sub-TLV value field is defined
in Section 4 of [WSON-Encode].
Type Sub-TLV Type Sub-TLV Name
1 (TBA) <RBInformation> 1 (TBA) ResourceBlockInfo
At least one <RBInformation> sub-TLV MUST always be present in the At least one ResourceBlockInfo sub-TLV MUST be present in the
WSON_Processing HOP Attribute TLV.. At most two <RBInformation> sub- WSON_Processing HOP Attribute TLV. At most two ResourceBlockInfo
TLVs MAY be present in the WSON_Processing HOP Attribute TLV . If sub-TLVs MAY be present in the WSON_Processing HOP Attribute TLV. If
more than two objects are encountered, two MUST be processed and the more than two sub-TLVs are encountered, the first two MUST be
rest SHOULD be ignored. processed and the rest SHOULD be ignored.
The <RBInformation> contains several information as defined by The <ResourceBlockInfo> contains several information as defined by
[WSON-Encode]. The following processing rules apply: [WSON-Encode]. The following processing rules apply to the sub-TLV:
RB Set Field MAY contain more than one RB Indetifier. Only the first RB Set Field MAY contain more than one RB Identifier. Only the first
one MUST be processed, the others SHOULD be ignored. of which MUST be processed, the others SHOULD be ignored.
The I an E flags MUST be set according to bidirectional LSP In case of signalin a unidirectional LSP, only one ResourceBlockInfo
signaling and the numbers of RBInformation subobjects available. In sub-TLV MUST be processed and I/O bits can be safely ignored.
case of unidirectional signaling, only one RBInformartion sub-object
MUST be processed and I/E bits can be safely ignored. In case of
bidirectional signaling: if only one RBInformartion is available,
bits I and E MUST be both set to 1, if two RBInformation sub-objects
are available, bits I and E MUST have different values.
The rest of information available within RBInformation sub-object is In case of signaling a bidirectional LSP: if only one
Optical Interface Class List, Input Bit Range List and Processing ResourceBlockInfo is included, bits I and O MUST be both set to 1,
Capability List. Lists MAY contain one or more elements. The usage if two ResourceBlockInfo sub-TLVs are included, bits I and O MUST
of WSON Processing object for the bidirectional case is the same as have different values, i.e., only one bit can be set in each
per unidirectional. When an intermediate node uses information from ResourceBlockInfo sub-TLV. Any violation of these detected by a
this object to instruct a node about wavelength regeneration, the transit or egress node will incur a processing error and SHOULD NOT
same information applies to both downstream and upstream directions. trigger any RSVP message but can be logged locally, and perhaps
reported through network management mechanisms.
4.4. Wavelength Assignment Method Selection TLV Encoding The rest of information available within ResourceBlockInfo sub-TLV
is Optical Interface Class List, Input Bit Rate List and Processing
Capability List. These lists MAY contain one or more elements. The
usage of WSON Processing HOP Attribute TLV for the bidirectional
case is the same as per unidirectional. When an intermediate node
uses information from this TLV to instruct a node about wavelength
regeneration, the same information applies to both downstream and
upstream directions.
Routing + Distributed wavelength assignment (R+DWA) is one of the This sub-TLV is constructed by an ingress node and the processing is
applied to all nodes (transit and egress) whose R bit is set in the
ERO HOP ATTRIBUTE subobject according to [RSVP-RO]. When the R bit
is set, a node MUST examine the ResourceBlockInfo sub-TLV present in
the subobject following the rule described in [RFC5420].
If a node processing an ERO HOP ATTRIBUTE subobject with WSON
Processing HOP Attributes TLV (which may include the
ResourceBlockInfo sub-TLVs) longer than the ERO subobject SHOULD
return a PathErr with an error code "Routing Error" and error value
"Bad EXPLICT_ROUTE object" with the EXPLICIT_ROUTE object included
as defined in [RSVP-RO] Section 3.3.
Once a node properly parsed the Sub-TLV, the node applies the
selected regeneration pool (at that hop) for the LSP. In addition,
the node SHOULD report compliance by adding a RRO_HOP_ATTRIBUTE
subobject with the WSON Processing HOP Attribute TLV (and its sub-
TLVs) which describes the attributes to be reported.
4.4. Wavelength Selection Sub-TLV
Routing + Distributed Wavelength Assignment (R+DWA) is one of the
options defined by the [RFC6163]. The output from the routing options defined by the [RFC6163]. The output from the routing
function will be a path but the wavelength will be selected on a function will be a path but the wavelength will be selected on a
hop-by-hop basis. hop-by-hop basis.
Under this hypothesis the node initiating the signaling process Under this hypothesis, the node initiating the signaling process
needs to declare its own wavelength availability (through a needs to declare its own wavelength availability (through a
label_set object). Each intermediate node may delete some labels due label_set object). Each intermediate node may delete some labels due
to connectivity constraints or its own assignment policy. At the to connectivity constraints or its own assignment policy. At the
end, the destination node has to make the final decision on the end, the destination node has to make the final decision on the
wavelength assignment among the ones received through the signaling wavelength assignment among the ones received through the signaling
process. process.
As discussed in [HZang00] a number of different wavelength As discussed in [HZang00], a number of different wavelength
assignment algorithms maybe employed. In addition as discussed in assignment algorithms may be employed. In addition as discussed in
[RFC6163] the wavelength assignment can be either for a [RFC6163] the wavelength assignment can be either for a
unidirectional lightpath or for a bidirectional lightpath unidirectional lightpath or for a bidirectional lightpath
constrained to use the same lambda in both directions. constrained to use the same lambda in both directions.
A simple sub-TLV could be used to indication wavelength assignment In order to indicate wavelength assignment directionality and
directionality and wavelength assignment method as a TLV in the LSP wavelength assignment method, a new Wavelength Selection, or
Attributes Object, as defined in [RFC5420]. WavelengthSelection, sub-TLV is defined to be carried in the WSON
Processing HOP Attribute TLV defined in Section 4.2 of this draft.
The type value of the Sub-TLV is:
Type Sub-TLV Type Sub-TLV Name
TDB <WavelengthSelection> 2(TDA) <WavelengthSelection>
The WavlengthSelection sub-TLV value field is defined as:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|W| WA Method | Reserved | |W| WA Method | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where: Where:
. W is a bit, 0 same wavelength in both directions, 1 may use W (1 bit): 0 denotes requiring the same wavelength in both
different wavelengths directions, 1 denotes that different wavelengths on both directions
. Wavelength Assignment (WA) Method: 0 unspecified (any), 1 are allowed.
First-Fit, 2 Random, 3 Least-Loaded (multi-fiber). Others TBD.
Wavelength Assignment (WA) Method (7 bits):
0 - unspecified (any); This does not constrain the WA method used by
a specific node.
1 - First-Fit. All the wavelengths are numbered and this WA method
chooses the available wavelength with the lowest index.
2 - Random. This WA method chooses an available wavelength randomly.
3 - Least-Loaded (multi-fiber). This WA method selects the
wavelength that has the largest residual capacity on the most loaded
link along the route. This method is used in multi-fiber networks.
If used in single-fiber networks, it is equivalent to the FF WA
method.
4- 127: Unassigned.
The processing rules of this TLV are as follows:
If a receiving node does not support the attribute(s), its behaviors
are specified below:
- W bit not supported: a PathErr MUST be generated with the Error
Code "Routing Problem" (24) with error sub-code "Unsupported
WavelengthSelection Symmetry value" (value to be assigned by IANA,
suggested value: 107).
- WA method not supported: a PathErr MUST be generated with the
Error Code "Routing Problem" (24) with error sub-code "unsupported
Wavelength Assignment value" (value to be assigned by IANA,
suggested value: 108).
This sub-TLV is constructed by an ingress node and the processing is
applied to all nodes (transit and egress) whose R bit is set in the
ERO HOP ATTRIBUTE subobject according to [RSVP-RO]. When the R bit
is set, a node MUST examine the WavelengthSelection sub-TLV present
in the subobject following the rule described in [RFC5420].
If a node processing an ERO HOP ATTRIBUTE subobject with WSON
Processing HOP Attributes TLV (which may include the
WavelengthSelection sub-TLVs) longer than the ERO subobject SHOULD
return a PathErr with an error code "Routing Error" and error value
"Bad EXPLICT_ROUTE object" with the EXPLICIT_ROUTE object included
as defined in [RSVP-RO] Section 3.3.
Once a node properly parsed the Sub-TLV, the node applies wavelength
assignment method (at that hop) for the LSP. In addition, the node
SHOULD report compliance by adding a RRO_HOP_ATTRIBUTE subobject
with the WSON Processing HOP Attribute TLV (and its sub-TLVs) which
describes the attributes to be reported.
5. Security Considerations 5. Security Considerations
This document is builds on the mechanisms defined in [RFC3473], and This document is builds on the mechanisms defined in [RFC3473], and
only differs in specific information communicated. As such, this only differs in specific information communicated. As such, this
document introduces no new security considerations to the existing document introduces no new security considerations to the existing
GMPLS signaling protocols. See [RFC3473], for details of the GMPLS signaling protocols. See [RFC3473], for details of the
supported security measures. Additionally, [RFC5920] provides an supported security measures. Additionally, [RFC5920] provides an
overview of security vulnerabilities and protection mechanisms for overview of security vulnerabilities and protection mechanisms for
the GMPLS control plane. the GMPLS control plane.
6. IANA Considerations 6. IANA Considerations
Upon approval of this document, IANA will make the following Upon approval of this document, IANA is requested to make the
assignments as follows: assignment of a new value for the existing "Attributes TLV Space"
registry located at http://www.iana.org/assignments/rsvp-te-
parameters/rsvp-te-parameters.xhtml:
A new LSP_REQUIRED_ATTRIBUTE type is required Type Name Allowed on Allowed on Reference
LSP ATTRIBUTES LSP REQUIRED_
ATTRIBUTES
Value Sub-TLV Reference 4 (Suggested) WSON No No [This.I-D]
Processing
HOP Attribute
TLV
3 (Suggested) WSON Processing HOP Attribute TLV [This ID] Upon approval of this document, IANA is requested to create a new
registry named "Sub-TLV Types for WSON Processing HOP Attribute TLV"
located at http://www.iana.org/assignments/rsvp-te-parameters/rsvp-
te-parameters.xhtml.
One new type sub-TLV is allowed within the LSP_Attributes Object The following entries are to be added:
Value Sub-TLV Reference Value Length Sub-TLV Type Reference
4 (Suggested) Wavelength Selection [This ID] 1 (suggested) variable ResourceBlockInfo [This.I-D]
2 (Suggested) 4 WavelengthSelection [This.I-D]
All assignments are to be performed via Standards Action as defined
in [RFC5226 <http://tools.ietf.org/html/rfc5226>].
Upon approval of this document, IANA is requested to create a new
registry named "Values for Wavelength Assignment Method field in
WavelengthSelection Sub-TLV" located at
http://www.iana.org/assignments/rsvp-te-parameters/rsvp-te-
parameters.xhtml.
The following entries are to be added:
Value Meaning Reference
0 unspecified [This.I-D]
1 First-Fit [This.I-D]
2 Random [This.I-D]
3 Least-Loaded (multi-fiber) [This.I-D]
4-127 unassigned
All assignments are to be performed via Standards Action as defined
in [RFC5226 <http://tools.ietf.org/html/rfc5226>].
Upon approval of this document, IANA is requested to make the
assignment of a new value for the existing "Error Codes and
Globally-Defined Error Value Sub-Codes - 29 Unknown Attribute TLV"
registry located at http://www.iana.org/assignments/rsvp-
parameters/rsvp-parameters.xml:
Value Meaning Reference
41 (suggested) Unknown WSON Processing
HOP Attribute sub-TLV type [This.I-D]
Upon approval of this document, IANA is requested to make the
assignment of a new value for the existing "Sub-Codes . 24 Routing
Problem" registry located at http://www.iana.org/assignments/rsvp-
parameters/rsvp-parameters.xml:
Value Description Reference
107 Unsupported WavelengthSelection
symmetry value [This.I-D]
108 Unsupported Wavelength Assignment
value [This.I-D]
7. Acknowledgments 7. Acknowledgments
Authors would like to thanks Lou Berger and Cyril Margaria for Authors would like to thanks Lou Berger, Cyril Margaria and Xian
comments and suggestions. Zhang for comments and suggestions.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC6205] T. Otani, H. Guo, K. Miyazaki, D. Caviglia, "Generalized
"Structure of Management Information Version 2 (SMIv2)", Labels for G.694 Lambda-Switching Capable Label Switching
STD 58, RFC 2578, April 1999. Routers", RFC 6205, March 2011.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., [WSON-Encode] Bernstein G., Lee Y., Li D., and W. Imajuku, "Routing
and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP and Wavelength Assignment Information Encoding for
Tunnels", RFC 3209, December 2001. Wavelength Switched Optical Networks", draft-ietf-ccamp-
rwa-wson-encode, work in progress.
[WSON-OSPF] Lee, Y, Bernstein G., "GMPLS OSPF Enhancement for Signal
and Network Element Compatibility for Wavelength Switched
Optical Networks", draft-ietf-ccamp-wson-signal-
compatibility-ospf, work in progress.
[RFC5511] Farrel, A., "Routing Backus-Naur Form (RBNF): A Syntax
Used to Form Encoding Rules in Various Routing Protocol
Specifications", RFC 5511, April 2009.
[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.
[RFC3473] Berger, L., Ed., "Generalized Multi-Protocol Label [RFC3473] Berger, L., Ed., "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Resource ReserVation Protocol- Switching (GMPLS) Signaling Resource ReserVation Protocol-
Traffic Engineering (RSVP-TE) Extensions", RFC 3473, Traffic Engineering (RSVP-TE) Extensions", RFC 3473,
January 2003. January 2003.
[RFC3477] Kompella, K. and Y. Rekhter, "Signalling Unnumbered Links
in Resource ReSerVation Protocol - Traffic Engineering
(RSVP-TE)", RFC 3477, January 2003.
[RFC5420] Farrel, A., Ed., Papadimitriou, D., Vasseur, J.-P., and A. [RFC5420] Farrel, A., Ed., Papadimitriou, D., Vasseur, J.-P., and A.
Ayyangar, " Encoding of Attributes for MPLS LSP Ayyangar, "Encoding of Attributes for MPLS LSP
Establishment Using Resource Reservation Protocol Traffic Establishment Using Resource Reservation Protocol Traffic
Engineering (RSVP-TE)", RFC 5420, February 2006. Engineering (RSVP-TE)", RFC 5420, February 2009.
[RFC5920] Luyuan Fang(Ed.), "Security Framework for MPLS and GMPLS
Networks", RFC5920, July 2010. [WSON-Encode] Bernstein
G., Lee Y., Li D., and W. Imajuku, "Routing and Wavelength
Assignment Information Encoding for Wavelength Switched
Optical Networks", draft-ietf-ccamp-rwa-wson-encode, work
in progress.
[RFC6205] T. Otani, H. Guo, K. Miyazaki, D. Caviglia, "Generalized
Labels for G.694 Lambda-Switching Capable Label Switching
Routers", RFC 6205, March 2011.
[RSVP-RO] Margaria, C., et al, "LSP Attribute in ERO", draft-ietf- [RSVP-RO] Margaria, C., et al, "LSP Attribute in ERO", draft-ietf-
ccamp-lsp-attribute-ro,work in progress. ccamp-lsp-attribute-ro, work in progress.
8.2. Informative References 8.2. Informative References
[WSON-CompOSPF] Y. Lee, G. Bernstein, "OSPF Enhancement for Signal [RFC5920] Fang, L., Ed., "Security Framework for MPLS and GMPLS
and Network Element Compatibility for Wavelength Switched Networks", RFC5920, July 2010.
Optical Networks", work in progress: draft-lee-ccamp-wson-
signal-compatibility-OSPF.
[RFC6163] Y. Lee, G. Bernstein, W. Imajuku, "Framework for GMPLS [RFC6163] Y. Lee, G. Bernstein, W. Imajuku, "Framework for GMPLS
and PCE Control of Wavelength Switched Optical Networks", and PCE Control of Wavelength Switched Optical Networks",
work in progress: draft-bernstein-ccamp-wavelength- work in progress: draft-bernstein-ccamp-wavelength-
switched-03.txt, February 2008. switched-03.txt, February 2008.
[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, work in progress. ccamp-rwa-info, work in progress.
[HZang00] H. Zang, J. Jue and B. Mukherjeee, "A review of routing [HZang00] H. Zang, J. Jue and B. Mukherjeee, "A review of routing
and wavelength assignment approaches for wavelength-routed and wavelength assignment approaches for wavelength-routed
optical WDM networks", Optical Networks Magazine, January optical WDM networks", Optical Networks Magazine, January
2000. 2000.
[Xu] S. Xu, H. Harai, and D. King, "Extensions to GMPLS RSVP-TE
for Bidirectional Lightpath the Same Wavelength", work in
progress: draft-xu-rsvpte-bidir-wave-01, November 2007.
[Winzer06] Peter J. Winzer and Rene-Jean Essiambre, "Advanced
Optical Modulation Formats", Proceedings of the IEEE, vol.
94, no. 5, pp. 952-985, May 2006.
[G.959.1] ITU-T Recommendation G.959.1, Optical Transport Network
Physical Layer Interfaces, March 2006.
[G.694.1] ITU-T Recommendation G.694.1, Spectral grids for WDM
applications: DWDM frequency grid, June 2002.
[G.694.2] ITU-T Recommendation G.694.2, Spectral grids for WDM
applications: CWDM wavelength grid, December 2003.
[G.Sup43] ITU-T Series G Supplement 43, Transport of IEEE 10G base-R
in optical transport networks (OTN), November 2006.
[RFC4427] Mannie, E., Ed., and D. Papadimitriou, Ed., "Recovery
(Protection and Restoration) Terminology for Generalized
Multi-Protocol Label Switching (GMPLS)", RFC 4427, March
2006.
[RFC4872] Lang, J., Rekhter, Y., and Papadimitriou, D., "RSVP-TE
Extensions in Support of End-to-End Generalized Multi-
Protocol Label Switching (GMPLS) Recovery", RFC 4872,
Author's Addresses Author's Addresses
Greg M. Bernstein (editor) Greg M. Bernstein (editor)
Grotto Networking Grotto Networking
Fremont California, USA Fremont California, USA
Phone: (510) 573-2237 Phone: (510) 573-2237
Email: gregb@grotto-networking.com Email: gregb@grotto-networking.com
Nicola Andriolli Nicola Andriolli
 End of changes. 69 change blocks. 
177 lines changed or deleted 284 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/