draft-ietf-ccamp-rwa-wson-encode-23.txt   draft-ietf-ccamp-rwa-wson-encode-24.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: May 2014 D. Li Expires: August 2014 D. Li
Huawei Huawei
W. Imajuku W. Imajuku
NTT NTT
November 13, 2013 February 13, 2014
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-23.txt draft-ietf-ccamp-rwa-wson-encode-24.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with This Internet-Draft is submitted to IETF in full conformance with
the provisions of BCP 78 and BCP 79. the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on May 13, 2013. This Internet-Draft will expire on August 13, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
skipping to change at page 2, line 44 skipping to change at page 2, line 44
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. Terminology....................................................4 1.1. Terminology..................................................4
2. Resources, Resource Blocks, and the Resource Pool..............4 2. Resources, Resource Blocks, and the Resource Pool..............4
2.1. Resource Block Set Field..................................5 2.1. Resource Block Set Field..................................5
3. Resource Accessibility/Availability............................6 3. Resource Accessibility/Availability............................6
3.1. Resource Accessibility Field..............................6 3.1. Resource Accessibility Field..............................6
3.2. Resource Wavelength Constraints Field.....................8 3.2. Resource Wavelength Constraints Field.....................8
3.3. Resource Block Pool State (RBPoolState) Field............10 3.3. Resource Block Pool State (RBPoolState) Field............10
3.4. Resource Block Shared Access Wavelength Availability 3.4. Resource Block Shared Access Wavelength Availability
(RBSharedAccessWaveAvailability) Field........................11 (RBSharedAccessWaveAvailability) Field........................11
4. Resource Signal Constraints and Processing Capabilities.......13 4. Resource Block Information (ResourceBlockInfo) Field..........13
4.1. Resource Block Information (ResourceBlockInfo) Field.....13 4.1. Optical Interface Class List Subfield....................15
4.2. Shared Input or Output Indication........................14 4.1.1. ITU-G.698.1 Application Code Mapping.............16
4.3. Optical Interface Class List(s) Field....................14 4.1.2. ITU-G.698.2 Application Code Mapping.............18
4.3.1. Optical Interface Class Format......................15 4.1.3. ITU-G.959.1 Application Code Mapping.............19
4.3.2. ITU-G.698.1 Application Code Mapping................16 4.1.4. ITU-G.695 Application Code Mapping...............22
4.3.3. ITU-G.698.2 Application Code Mapping................18 4.2. Acceptable Client Signal List Subfield...................24
4.3.4. ITU-G.959.1 Application Code Mapping................19 4.3. Input Bit Rate List Subfield.............................24
4.3.5. ITU-G.695 Application Code Mapping..................21 4.4. Processing Capability List Subfield......................25
4.4. Acceptable Client Signal List Field......................23
4.5. Input Bit Rate List Field................................24
4.6. Processing Capability List Field.........................24
4.6.1. Processing Capabilities Field.......................24
5. Security Considerations.......................................26 5. Security Considerations.......................................26
6. IANA Considerations...........................................26 6. IANA Considerations...........................................27
7. Acknowledgments...............................................26 6.1. Types for subfields of WSON Resource Block Information...27
APPENDIX A: Encoding Examples....................................27 7. Acknowledgments...............................................27
A.1. Wavelength Converter Accessibility Field.................27 APPENDIX A: Encoding Examples....................................28
A.2. Wavelength Conversion Range Field........................28 A.1. Wavelength Converter Accessibility Field.................28
A.3. An OEO Switch with DWDM Optics...........................29 A.2. Wavelength Conversion Range Field........................29
8. References....................................................32 A.3. An OEO Switch with DWDM Optics...........................30
8.1. Normative References.....................................32 8. References....................................................33
8.2. Informative References...................................32 8.1. Normative References.....................................33
9. Contributors..................................................34 8.2. Informative References...................................33
Authors' Addresses...............................................35 9. Contributors..................................................35
Intellectual Property Statement..................................36 Authors' Addresses...............................................36
Disclaimer of Validity...........................................37 Intellectual Property Statement..................................37
Disclaimer of Validity...........................................38
1. Introduction 1. Introduction
A Wavelength Switched Optical Network (WSON) is a Wavelength A Wavelength Switched Optical Network (WSON) is a Wavelength
Division Multiplexing (WDM) optical network in which switching is Division Multiplexing (WDM) optical network in which switching is
performed selectively based on the center wavelength of an optical performed selectively based on the center wavelength of an optical
signal. signal.
[RFC6163] describes a framework for Generalized Multiprotocol Label [RFC6163] describes a framework for Generalized Multiprotocol Label
Switching (GMPLS) and Path Computation Element (PCE) control of a Switching (GMPLS) and Path Computation Element (PCE) control of a
skipping to change at page 4, line 15 skipping to change at page 4, line 12
This document provides efficient encodings of information needed by This document provides efficient encodings of information needed by
the routing and wavelength assignment (RWA) process in a WSON. Such the routing and wavelength assignment (RWA) process in a WSON. Such
encodings can be used to extend GMPLS signaling and routing encodings can be used to extend GMPLS signaling and routing
protocols. In addition these encodings could be used by other protocols. In addition these encodings could be used by other
mechanisms to convey this same information to a path computation mechanisms to convey this same information to a path computation
element (PCE). Note that since these encodings are relatively element (PCE). Note that since these encodings are relatively
efficient they can provide more accurate analysis of the control efficient they can provide more accurate analysis of the control
plane communications/processing load for WSONs looking to utilize a plane communications/processing load for WSONs looking to utilize a
GMPLS control plane. GMPLS control plane.
1. Terminology 1.1. Terminology
Refer to [RFC6163] for CWDM, DWDM, RWA, WDM. Refer to [RFC6163] for CWDM, DWDM, RWA, WDM.
Refer to Section 5 of [Gen-Encode] for the terminology of Resources, Refer to Section 5 of [Gen-Encode] for the terminology of Resources,
Resources Blocks, and Resource Pool. Resources Blocks, and Resource Pool.
2. Resources, Resource Blocks, and the Resource Pool 2. Resources, Resource Blocks, and the Resource Pool
This section provides encodings for the information elements defined This section provides encodings for the information elements defined
in [RWA-INFO] that have applicability to WSON. The encodings are in [RWA-Info] that have applicability to WSON. The encodings are
designed to be suitable for use in the GMPLS routing protocols OSPF designed to be suitable for use in the GMPLS routing protocols OSPF
[RFC4203] and IS-IS [RFC5307] and in the PCE protocol (PCEP) [RFC4203] and IS-IS [RFC5307] and in the PCE protocol (PCEP)
[RFC5440]. Note that the information distributed in [RFC4203] and [RFC5440]. Note that the information distributed in [RFC4203] and
[RFC5307] is arranged via the nesting of sub-TLVs within TLVs and [RFC5307] is arranged via the nesting of sub-TLVs within TLVs and
this document defines elements to be used within such constructs. this document defines elements to be used within such constructs.
Specific constructs of sub-TLVs and the nesting of sub-TLVs of the Specific constructs of sub-TLVs and the nesting of sub-TLVs of the
information element defined by this document will be defined in the information element defined by this document will be defined in the
respective protocol enhancement documents. respective protocol enhancement documents.
This document defines the following information elements pertaining This document defines the following information elements pertaining
skipping to change at page 5, line 30 skipping to change at page 5, line 28
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Action |C| Reserved | Length | | Action |C| Reserved | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB Identifier 1 | | RB Identifier 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: : : : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB Identifier n | | RB Identifier n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Action: 8 bits Action: 8 bits
0 - Inclusive List 0 - Inclusive List
Indicates that the TLV contains one or more RB elements that are Indicates that the TLV contains one or more RB elements that are
included in the list. included in the list.
1 - Inclusive Range(s) 1 - Inclusive Range(s)
skipping to change at page 7, line 8 skipping to change at page 7, line 8
pool in relation to the switching device. In particular it indicates pool in relation to the switching device. In particular it indicates
the ability of an input port to reach sets of resources and of sets the ability of an input port to reach sets of resources and of sets
of resources to reach a particular output port. This is the of resources to reach a particular output port. This is the
PoolInputMatrix and PoolOutputMatrix of [RWA-Info]. PoolInputMatrix and PoolOutputMatrix of [RWA-Info].
The Resource Accessibility is defined by: The Resource Accessibility is defined by:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved |C| Reserved | |Reserved(8bits)|C| Reserved (23 bits) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Link Set Field A #1 | | Input Link Set Field A #1 |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB Set Field A #1 | | RB Set Field A #1 |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Additional Link set and RB set pairs as needed to | | Additional Link set and RB set pairs as needed to |
: specify PoolInputMatrix : : specify PoolInputMatrix :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Link Set Field B #1 | | Output Link Set Field B #1 |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB Set B Field #1 (for output connectivity) | | RB Set B Field #1 (for output connectivity) |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Additional Link Set and RB set pairs as needed to | | Additional Link Set and RB set pairs as needed to |
: specify PoolOutputMatrix : : specify PoolOutputMatrix :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 13, line 5 skipping to change at page 13, line 5
Indicates the wavelengths currently available (not being used) on Indicates the wavelengths currently available (not being used) on
the input fiber to this resource block. This field is encoded via the input fiber to this resource block. This field is encoded via
the Label Set field of [Gen-Encode]. the Label Set field of [Gen-Encode].
Output Available Wavelength Set Field: Output Available Wavelength Set Field:
Indicates the wavelengths currently available (not being used) on Indicates the wavelengths currently available (not being used) on
the output fiber from this resource block. This field is encoded via the output fiber from this resource block. This field is encoded via
the Label Set field of [Gen-Encode]. the Label Set field of [Gen-Encode].
4. Resource Signal Constraints and Processing Capabilities 4. Resource Block Information (ResourceBlockInfo) Field
Within a WSON network element (NE) there may be resources with As defined in [RWA-INFO], the Resource Block Information
signal compatibility constraints. These resources be regenerators, <ResourceBlockInfo> field is used to represent resource signal
wavelength converters, etc... Such resources may also constitute the constraints and processing capabilities of a node.
network element as a whole as in the case of an electro optical
switch. This section primarily focuses on the signal compatibility
and processing properties of such a resource block.
The fundamental properties of a resource block, such as a The fundamental properties of a resource block are:
regenerator or wavelength converter, are:
(a) Optical Interface Class List(s) (a) Optical Interface Class List(s)
(b) Acceptable Client Signal (shared input, modulation, FEC, bit (b) Acceptable Client Signal (shared input, modulation, FEC, bit
rate, G-PID) rate, G-PID)
(c) Input Bit Rate (c) Input Bit Rate
(d) Processing Capabilities (number of resources in a block, (d) Processing Capabilities (number of resources in a block,
regeneration, performance monitoring, vendor specific) regeneration, performance monitoring, vendor specific)
4.1. Resource Block Information (ResourceBlockInfo) Field ResourceBlockInfo fields are used to convey relatively static
information about individual resource blocks including the resource
Resource Block information fields are used to convey relatively block properties and the number of resources in a block.
static information about individual resource blocks including the
resource block compatibility properties, processing properties, and
the number of resources in a block.
There can be more than one Resource Block field as resources are When more than one ResourceBlockInfo field is used, there are no
packaged together in blocks of similar devices and its ordering requirements amongst these fields.
characteristics.
This field has the following format: This ResourceBlockInfo field has the following format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB Set Field | | RB Set Field |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I|O| Reserved | |I|O| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Optical Interface Class List(s) (opt) | | Optional subfield 1 |
: : : ... :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Acceptable Client Signal Type (opt) |
: :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Bit Rate List (opt) | : : :
: : : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Processing Capabilities List (opt) | | Optional subfield N |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
RB Set Field is described in Section 2.1. RB Set Field is described in Section 2.1.
4.2. Shared Input or Output Indication
The shared input or output indication is indicated by the first bit The shared input or output indication is indicated by the first bit
(I) and the second bit (O): (I) and the second bit (O):
where I and O are set to 1 if the resource blocks identified in the where I and O are set to 1 if the resource blocks identified in the
RB set field utilized a shared fiber for input/output access and set RB set field utilized a shared fiber for input/output access and set
to 0 otherwise. to 0 otherwise.
4.3. Optical Interface Class List(s) Field Zero or more Optional subfields MAY be present. Optional subfields
have following format:
The list of Optical Interface Class Field has the following format: 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value... |
. .
. .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Length field defines the length of the value portion in bytes
(thus a subfield with no value portion would have a length of zero).
The subfield is padded to four-byte alignment; padding is not
included in the Length field (so a three byte value would have a
length of three, but the total size of the subfield would be eight
byte). Unrecognized types are not processed. If multiple subfields
of the same type are present, only the first of the type SHOULD be
processed.
The following subfield Types are defined:
Value Length Sub-TLV Type
1 variable Optical Interface Class List
2 variable Acceptable Client Signal List
3 variable Input Bit Rate List
4 variable Processing Capability List
See the IANA Considerations section for allocation of new Types.
4.1. Optical Interface Class List Subfield
The list of Optical Interface Class subfield 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved |I|E| | Reserved |I|O|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Optical Interface Classes | | Optical Interface Classes |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The following I and E combination are defined: The following I and E combination are defined:
I E I O
0 0 Invalid 0 0 Invalid
1 0 Optical Interface Class List acceptable in input 1 0 Optical Interface Class List acceptable in input
0 1 Optical Interface Class List available in output 0 1 Optical Interface Class List available in output
1 1 Optical Interface Class List available on both input and 1 1 Optical Interface Class List available on both input and
output. output.
The Resource Block MAY contain one or more lists according to The Resource Block MAY contain one or more lists according to
input/output flags. input/output flags.
4.3.1. Optical Interface Class Format The Optical Interface Classes Format is defined as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|S| Reserved | OI Code Points | |S| Reserved | OI Code Points |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Optical Interface Class | | Optical Interface Class |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Optical Interface Class (Cont.) | | Optical Interface Class (Cont.) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 16, line 31 skipping to change at page 16, line 33
0: reserved 0: reserved
1: [ITU-G.698.1] application code. 1: [ITU-G.698.1] application code.
2: [ITU-G.698.2] application code. 2: [ITU-G.698.2] application code.
3: [ITU-G.959.1] application code. 3: [ITU-G.959.1] application code.
4: [ITU-G.695] application code. 4: [ITU-G.695] application code.
In case of ITU Application Code, the mapping between the string In case of ITU Application Code, the mapping between the string
defining the application code and the 64 bits number implementing defining the application code and the 64 bits number implementing
the optical interface class is given in the following sections. the optical interface class is given in the following sections.
4.3.2. ITU-G.698.1 Application Code Mapping 4.1.1. ITU-G.698.1 Application Code Mapping
Recommendation ITU-G.698.1 defines the Application Codes: DScW- Recommendation ITU-G.698.1 defines the Application Codes: DScW-
ytz(v) and B-DScW-ytz(v). Where: ytz(v) and B-DScW-ytz(v). Where:
B: means Bidirectionals. B: means Bidirectionals.
D: means a DWDM application. D: means a DWDM application.
S: take values N (narrow spectral excursion), W (wide spectral S: take values N (narrow spectral excursion), W (wide spectral
excursion). excursion).
skipping to change at page 17, line 39 skipping to change at page 18, line 4
reported above): reported above):
B: = 1 bidirectional, 0 otherwise B: = 1 bidirectional, 0 otherwise
D (prefix): = 0 reserved, = 1 (D) D (prefix): = 0 reserved, = 1 (D)
S: = 0 (N), = 1 (W) S: = 0 (N), = 1 (W)
c: Channel Spacing, 4 bits mapped according to same definition c: Channel Spacing, 4 bits mapped according to same definition
in [RFC6205] (note that DWDM spacing apply here) in [RFC6205] (note that DWDM spacing apply here)
W: = 0 reserved, = 2 (S), = 3 (L) W: = 0 reserved, = 2 (S), = 3 (L)
y: = 0 reserved, = 1 (1), = 2 (2) y: = 0 reserved, = 1 (1), = 2 (2)
t: = 0 reserved, = 4 (D) t: = 0 reserved, = 4 (D)
z: = 0 reserved, = 2 (2), = 3 (3), = 5 (5) z: = 0 reserved, = 2 (2), = 3 (3), = 5 (5)
v: = 0 reserved, = 1 (S), = 2 (C), = 3 (L) v: = 0 reserved, = 1 (S), = 2 (C), = 3 (L)
F (suffix): = 0 reserved, = 1 Fec Encoding F (suffix): = 0 reserved, = 1 Fec Encoding
Values not mentioned here are not allowed in this application Values not mentioned here are not allowed in this application
code, the last 32 bits are reserved and shall be set to zero. code, the last 32 bits are reserved and shall be set to zero.
4.3.3. ITU-G.698.2 Application Code Mapping 4.1.2. ITU-G.698.2 Application Code Mapping
Recommendation ITU-G.698.2 defines the Application Codes: DScW- Recommendation ITU-G.698.2 defines the Application Codes: DScW-
ytz(v) and B-DScW-ytz(v). ytz(v) and B-DScW-ytz(v).
B: means Bidirectional. B: means Bidirectional.
D: means a DWDM application. D: means a DWDM application.
S: take values N (narrow spectral excursion), W (wide spectral S: take values N (narrow spectral excursion), W (wide spectral
excursion). excursion).
skipping to change at page 19, line 32 skipping to change at page 19, line 44
z: = 0 reserved, = 2 (2), = 3 (3), = 5 (5) z: = 0 reserved, = 2 (2), = 3 (3), = 5 (5)
v: = 0 reserved, = 1 (S), = 2 (C), = 3 (L) v: = 0 reserved, = 1 (S), = 2 (C), = 3 (L)
F (suffix): = 0 reserved, = 1 Fec Encoding F (suffix): = 0 reserved, = 1 Fec Encoding
Values not mentioned here are not allowed in this application Values not mentioned here are not allowed in this application
code, the last 32 bits are reserved and shall be set to zero. code, the last 32 bits are reserved and shall be set to zero.
4.3.4. ITU-G.959.1 Application Code Mapping 4.1.3. ITU-G.959.1 Application Code Mapping
Recommendation ITU-G.959.1 defines the Application Codes: PnWx-ytz Recommendation ITU-G.959.1 defines the Application Codes: PnWx-ytz
and BnWx-ytz. Where: and BnWx-ytz. Where:
P,B: when present indicate Plural or Bidirectional P,B: when present indicate Plural or Bidirectional
n: maximum number of channels supported by the application code n: maximum number of channels supported by the application code
(i.e. an integer number) (i.e. an integer number)
W: take values I (intra-office), S (short-haul), L (long-haul), V W: take values I (intra-office), S (short-haul), L (long-haul), V
skipping to change at page 21, line 30 skipping to change at page 22, line 5
suffix is an 6 bit, bit map: suffix is an 6 bit, bit map:
0 1 2 3 4 5 0 1 2 3 4 5
+-+-+-+-+-+-+ +-+-+-+-+-+-+
|F|D|E|r|a|b| |F|D|E|r|a|b|
+-+-+-+-+-+-+ +-+-+-+-+-+-+
where a 1 in the appropriate slot indicates that the corresponding where a 1 in the appropriate slot indicates that the corresponding
suffix has been added. suffix has been added.
4.3.5. ITU-G.695 Application Code Mapping 4.1.4. ITU-G.695 Application Code Mapping
Recommendation [ITU-G.695] defines the Application Codes: CnWx-ytz Recommendation [ITU-G.695] defines the Application Codes: CnWx-ytz
and B-CnWx-ytz and S-CnWx-ytz. and B-CnWx-ytz and S-CnWx-ytz.
Where the optional prefixed are: Where the optional prefixed are:
B: Bidirectional B: Bidirectional
S: a system using a black link approach S: a system using a black link approach
skipping to change at page 23, line 26 skipping to change at page 24, line 5
suffix is an 6 bit, bit map: suffix is an 6 bit, bit map:
0 1 2 3 4 5 0 1 2 3 4 5
+-+-+-+-+-+-+ +-+-+-+-+-+-+
|F|0|0|0|0|0| |F|0|0|0|0|0|
+-+-+-+-+-+-+ +-+-+-+-+-+-+
where a 1 in the appropriate slot indicates that the corresponding where a 1 in the appropriate slot indicates that the corresponding
suffix has been added. suffix has been added.
4.4. Acceptable Client Signal List Field 4.2. Acceptable Client Signal List Subfield
This field contains a list of acceptable input client signal types. This subfield contains a list of acceptable input client signal
types.
The acceptable client signal list is a list of Generalized Protocol The acceptable client signal list is a list of Generalized Protocol
Identifiers (G-PIDs). G-PIDs are assigned by IANA and many are Identifiers (G-PIDs).
defined in [RFC3471] and [RFC4328].
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of G-PIDs | G-PID #1 | | Reserved | Number of G-PIDs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| G-PID #1 | G-PID #2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: | : : | :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| G-PID #N | | | G-PID #N | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where the number of G-PIDs is an integer greater than or equal to Type (16 bits): identifies the Acceptable Client Signal List field.
one.
4.5. Input Bit Rate List Field Length (16 bits): The Length field defines the length of the value
portion in octets.
This field contains a list of bit rate of each input client signal The number of G-PIDs is an integer greater than or equal to one.
types specified in the Input Client Signal List.
G-PIDs are assigned by IANA and many are defined in [RFC3471] and
[RFC4328].
4.3. Input Bit Rate List Subfield
This subfield contains a list of bit rate of each input client
signal types specified in the Input Client Signal List.
The number of Input Bit Rate MUST match the number of G-PID. The number of Input Bit Rate MUST match the number of G-PID.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Bit Rate of G-PID #1 | | Input Bit Rate of G-PID #1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Bit Rate of G-PID #N | | Input Bit Rate of G-PID #N |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
4.6. Processing Capability List Field Input Bit Rates are in IEEE floating point format [IEEE].
This field contains a list of resource processing capabilities. 4.4. Processing Capability List Subfield
This subfield contains a list of resource processing capabilities.
The processing capability list field is a list of capabilities that The processing capability list field is a list of capabilities that
can be achieved through the referred resources: can be achieved through the referred resources:
1. Regeneration capability 1. Regeneration capability
2. Fault and performance monitoring 2. Fault and performance monitoring
3. Vendor Specific capability 3. Vendor Specific capability
Note that the code points for Fault and performance monitoring and Note that the code points for Fault and performance monitoring and
vendor specific capability are subject to further study. vendor specific capability are subject to further study.
4.6.1. Processing Capabilities Field The processing capability list field is then given by:
The processing capability field is then given by:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Processing Cap ID | Length | | Reserved | Processing Cap ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Possible additional capability parameters depending upon | | Possible additional capability parameters depending upon |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: the processing ID : : the processing ID :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
When the processing Cap ID is "regeneration capability", the When the processing Cap ID is "regeneration capability", the
following additional capability parameters are provided in the following additional capability parameters are provided in the
following field: following field:
skipping to change at page 25, line 46 skipping to change at page 26, line 36
C=0: Reserved C=0: Reserved
C=1: Fixed Regeneration Point C=1: Fixed Regeneration Point
C=2: Selective Regeneration Point C=2: Selective Regeneration 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
input and output restrictions and availability need to be specified. input and output restrictions and availability need to be specified.
This encoding is to be determined in the later revision. The code point for this is subject to further study.
5. Security Considerations 5. Security Considerations
This document defines protocol-independent encodings for WSON This document defines protocol-independent encodings for WSON
information and does not introduce any security issues. information and does not introduce any security issues.
However, other documents that make use of these encodings within However, other documents that make use of these encodings within
protocol extensions need to consider the issues and risks associated protocol extensions need to consider the issues and risks associated
with, inspection, interception, modification, or spoofing of any of with, inspection, interception, modification, or spoofing of any of
this information. It is expected that any such documents will this information. It is expected that any such documents will
describe the necessary security measures to provide adequate describe the necessary security measures to provide adequate
protection. A general discussion on security in GMPLS networks can protection. A general discussion on security in GMPLS networks can
be found in [RFC5920]. be found in [RFC5920].
6. IANA Considerations 6. IANA Considerations
This document provides general protocol independent information IANA allocation requests for protocol dependent encodings will be
encodings. There is no IANA allocation request for the information
elements defined in this document. IANA allocation requests will be
addressed in protocol specific documents based on the encodings addressed in protocol specific documents based on the encodings
defined here. defined here.
This document introduces a new registry for GMPLS routing parameters
for WSON encoding. This new IANA registry will be created to make
the assignment of a new type and new values for the new "GMPLS
Routing Parameters for WSON."
6.1. Types for subfields of WSON Resource Block Information
Under this new GMPLS Routing Parameters for WSON, a new IANA
registry will be created for nested subfields of the Resource Block
Information field to create a new section named "Types for subfields
of WSON Resource Block Information" and allocate new values as
follows:
Value Length Sub-TLV Type Reference
0 Reserved
1 variable Optical Interface Class List [This.I-D]
2 variable Acceptable Client
Signal List [This.I-D]
3 variable Input Bit Rate List [This.I-D]
4 variable Processing Capability List [This.I-D]
5-65535 Unassigned
Types are to be assigned via Standards Action as defined in
[RFC5226].
7. Acknowledgments 7. Acknowledgments
This document was prepared using 2-Word-v2.0.template.dot. This document was prepared using 2-Word-v2.0.template.dot.
APPENDIX A: Encoding Examples APPENDIX A: Encoding Examples
A.1. Wavelength Converter Accessibility Field A.1. Wavelength Converter Accessibility Field
Example: Example:
skipping to change at page 31, line 34 skipping to change at page 32, line 34
: Fixed (non optional) 3R regeneration : : Fixed (non optional) 3R regeneration :
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Since there is fixed connectivity to resource blocks (the electronic Since there is fixed connectivity to resource blocks (the electronic
switch) the <RBAccessibility> is: switch) the <RBAccessibility> is:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Connectivity=0|Reserved | | Connectivity=0|Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Link Set Field A #1 | | Input Link Set Field A #1 |
: (All input links connect to resource) : : (All input links connect to resource) :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB Set Field A #1 | | RB Set Field A #1 |
: (trivial set only one resource block) : : (trivial set only one resource block) :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Link Set Field B #1 | | Output Link Set Field B #1 |
: (All output links connect to resource) : : (All output links connect to resource) :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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,
"Structure of Management Information Version 2 (SMIv2)",
STD 58, RFC 2578, April 1999.
[RFC4328] Papadimitriou, D., Ed., "Generalized Multi-Protocol Label [RFC4328] Papadimitriou, D., Ed., "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Extensions for G.709 Optical Switching (GMPLS) Signaling Extensions for G.709 Optical
Transport Networks Control", RFC 4328, January 2006. Transport Networks Control", RFC 4328, January 2006.
[RWA-Info] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "Routing and
Wavelength Assignment Information Model for Wavelength
Switched Optical Networks", work in progress: draft-ietf-
ccamp-rwa-info.
[Gen-Encode] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "General [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- Networks", work in progress: draft-ietf-ccamp-general-
constraint-encode. constraint-encode.
8.2. Informative References 8.2. Informative References
[IEEE] IEEE, "IEEE Standard for Binary Floating-Point
Arithmetic", Standard 754-1985, 1985 (ISBN 1-5593-7653-8).
[G.694.1] ITU-T Recommendation G.694.1, Spectral grids for WDM [G.694.1] ITU-T Recommendation G.694.1, Spectral grids for WDM
applications: DWDM frequency grid, June 2002. applications: DWDM frequency grid, June 2002.
[G.694.2] ITU-T Recommendation G.694.2, Spectral grids for WDM [G.694.2] ITU-T Recommendation G.694.2, Spectral grids for WDM
applications: CWDM wavelength grid, December 2003. applications: CWDM wavelength grid, December 2003.
[G.695] ITU-T Recommendation G.695, Optical interfaces for coarse [G.695] ITU-T Recommendation G.695, Optical interfaces for coarse
wavelength division multiplexing applications, October, wavelength division multiplexing applications, October,
2010. 2010.
skipping to change at page 34, line 5 skipping to change at page 34, line 28
Networks", RFC 5920, July 2010. Networks", RFC 5920, July 2010.
[RFC6205] T. Otani, H. Guo, K. Miyazaki, D. Caviglia, "Generalized [RFC6205] T. Otani, H. Guo, K. Miyazaki, D. Caviglia, "Generalized
Labels for G.694 Lambda-Switching Capable Label Switching Labels for G.694 Lambda-Switching Capable Label Switching
Routers", RFC 6205, March 2011. Routers", RFC 6205, March 2011.
[RFC6163] Y. Lee, G. Bernstein, W. Imajuku, "Framework for GMPLS [RFC6163] Y. Lee, G. Bernstein, W. Imajuku, "Framework for GMPLS
and PCE Control of Wavelength Switched Optical Networks", and PCE Control of Wavelength Switched Optical Networks",
RFC 6163, April 2011. RFC 6163, April 2011.
[RWA-Info] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "Routing and
Wavelength Assignment Information Model for Wavelength
Switched Optical Networks", work in progress: draft-ietf-
ccamp-rwa-info.
9. Contributors 9. Contributors
Diego Caviglia Diego Caviglia
Ericsson Ericsson
Via A. Negrone 1/A 16153 Via A. Negrone 1/A 16153
Genoa Italy Genoa Italy
Phone: +39 010 600 3736 Phone: +39 010 600 3736
Email: diego.caviglia@ericsson.com Email: diego.caviglia@ericsson.com
 End of changes. 57 change blocks. 
112 lines changed or deleted 163 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/