draft-ietf-ccamp-flexible-grid-ospf-ext-09.txt   rfc8363.txt 
CCAMP Working Group Xian Zhang
Internet-Draft Haomian Zheng Internet Engineering Task Force (IETF) X. Zhang
Intended status: Standards Track Huawei Request for Comments: 8363 H. Zheng
Ramon Casellas Category: Standards Track Huawei
ISSN: 2070-1721 R. Casellas
CTTC CTTC
O. Gonzalez de Dios O. Gonzalez de Dios
Telefonica Telefonica
D. Ceccarelli D. Ceccarelli
Ericsson Ericsson
Expires: August 17, 2017 February 17, 2017 May 2018
GMPLS OSPF-TE Extensions in support of Flexi-grid DWDM networks
draft-ietf-ccamp-flexible-grid-ospf-ext-09.txt GMPLS OSPF-TE Extensions in Support of Flexi-Grid
Dense Wavelength Division Multiplexing (DWDM) Networks
Abstract Abstract
The International Telecommunication Union Telecommunication The International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) has extended its Recommendations standardization sector (ITU-T) has extended its Recommendations
G.694.1 and G.872 to include a new Dense Wavelength Division G.694.1 and G.872 to include a new Dense Wavelength Division
Multiplexing (DWDM) grid by defining a set of nominal central Multiplexing (DWDM) grid by defining channel spacings, a set of
frequencies, channel spacings, and the concept of the "frequency nominal central frequencies, and the concept of the "frequency slot".
slot". Corresponding techniques for data-plane connections are known Corresponding techniques for data-plane connections are known as
as flexi-grid. "flexi-grid".
Based on the characteristics of flexi-grid defined in G.694.1, RFC
7698 and 7699, this document describes the OSPF-TE extensions in
support of GMPLS control of networks that include devices that use
the new flexible optical grid.
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with Based on the characteristics of flexi-grid defined in G.694.1 and in
the provisions of BCP 78 and BCP 79. RFCs 7698 and 7699, this document describes the Open Shortest Path
First - Traffic Engineering (OSPF-TE) extensions in support of GMPLS
control of networks that include devices that use the new flexible
optical grid.
Internet-Drafts are working documents of the Internet Engineering Status of This Memo
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six This is an Internet Standards Track document.
months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at This document is a product of the Internet Engineering Task Force
http://www.ietf.org/shadow.html. (IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
This Internet-Draft will expire on August 17, 2017. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8363.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2018 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 (https://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
respect to this document. Code Components extracted from this to this document. Code Components extracted from this document must
document must include Simplified BSD License text as described in include Simplified BSD License text as described in Section 4.e of
Section 4.e of the Trust Legal Provisions and are provided without the Trust Legal Provisions and are provided without warranty as
warranty as described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction ................................................. 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology .................................................. 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Conventions Used in this Document ....................... 4 2.1. Conventions Used in This Document . . . . . . . . . . . . 4
3. Requirements for Flexi-grid Routing .......................... 4 3. Requirements for Flexi-Grid Routing . . . . . . . . . . . . . 4
3.1. Available Frequency Ranges .............................. 4 3.1. Available Frequency Ranges . . . . . . . . . . . . . . . 4
3.2. Application Compliance Considerations ................... 5 3.2. Application Compliance Considerations . . . . . . . . . . 5
3.3. Comparison with Fixed-grid DWDM Links ................... 6 3.3. Comparison with Fixed-Grid DWDM Links . . . . . . . . . . 6
4. Extensions ................................................... 7 4. Extensions . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.1. ISCD Extensions for Flexi-grid .......................... 7 4.1. Interface Switching Capability Descriptor (ISCD)
4.1.1. Switching Capability Specific Information (SCSI).... 8 Extensions for Flexi-Grid . . . . . . . . . . . . . . . . 7
4.1.2. An SCSI Example ................................... 10 4.1.1. Switching Capability Specific Information (SCSI) . . 8
4.2. Extensions to Port Label Restriction sub-TLV ........... 12 4.1.2. An SCSI Example . . . . . . . . . . . . . . . . . . . 10
5. IANA Considerations ......................................... 13 4.2. Extensions to the Port Label Restrictions Field . . . . . 11
5.1. New Switching Type ..................................... 13 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
5.2. New Sub-TLV ............................................ 13 5.1. New ISCD Switching Type . . . . . . . . . . . . . . . . . 13
6. Implementation Status ....................................... 14 5.2. New SCSI Type . . . . . . . . . . . . . . . . . . . . . . 13
6.1. Centre Tecnologic de Telecomunicacions de Catalunya (CTTC)14 6. Security Considerations . . . . . . . . . . . . . . . . . . . 13
7. Acknowledgments ............................................. 15 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
8. Security Considerations ..................................... 15 7.1. Normative References . . . . . . . . . . . . . . . . . . 14
9. Contributors' Addresses ..................................... 16 7.2. Informative References . . . . . . . . . . . . . . . . . 15
10. References ................................................. 16 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 16
10.1. Normative References .................................. 16 Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 16
10.2. Informative References ................................ 17 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
Authors' Addresses ............................................. 17
1. Introduction 1. Introduction
[G.694.1] defines the Dense Wavelength Division Multiplexing (DWDM) [G.694.1] defines the Dense Wavelength Division Multiplexing (DWDM)
frequency grids for Wavelength Division Multiplexing (WDM) frequency grids for Wavelength Division Multiplexing (WDM)
applications. A frequency grid is a reference set of frequencies applications. A frequency grid is a reference set of frequencies
used to denote allowed nominal central frequencies that may be used used to denote allowed nominal central frequencies that may be used
for defining applications. The channel spacing is the frequency for defining applications. The channel spacing is the frequency
spacing between two allowed nominal central frequencies. All of the spacing between two allowed nominal central frequencies. All of the
wavelengths on a fiber should use different central frequencies and wavelengths on a fiber should use different central frequencies and
occupy a fixed bandwidth of frequency. occupy a fixed bandwidth of frequency.
Fixed grid channel spacing ranges from 12.5 GHz, 25 GHz, 50 GHz, 100 Fixed-grid channel spacing ranges from one of 12.5 GHz, 25 GHz, 50
GHz to integer multiples of 100 GHz. But [G.694.1] also defines GHz, or 100 GHz to integer multiples of 100 GHz. But [G.694.1] also
"flexible grids", also known as "flexi-grid". The terms "frequency defines a "flexible grid", also known as "flexi-grid". The terms
slot" (i.e., the frequency range allocated to a specific channel and "frequency slot" (i.e., the frequency range allocated to a specific
unavailable to other channels within a flexible grid) and "slot channel and unavailable to other channels within a flexible grid) and
width" (i.e., the full width of a frequency slot in a flexible grid) "slot width" (i.e., the full width of a frequency slot in a flexible
are used to define a flexible grid. grid) are used to define a flexible grid.
[RFC7698] defines a framework and the associated control plane [RFC7698] defines a framework and the associated control-plane
requirements for the GMPLS based control of flexi-grid DWDM networks. requirements for the GMPLS-based control of flexi-grid DWDM networks.
[RFC6163] provides a framework for GMPLS and Path Computation [RFC6163] provides a framework for GMPLS and Path Computation Element
Element (PCE) control of Wavelength Switched Optical Networks (PCE) control of Wavelength Switched Optical Networks (WSONs).
(WSONs), and [RFC7688] defines the requirements and OSPF-TE [RFC7688] defines the requirements and OSPF-TE extensions in support
extensions in support of GMPLS control of a WSON. of GMPLS control of a WSON.
[RFC7792] describes requirements and protocol extensions for [RFC7792] describes requirements and protocol extensions for
signaling to set up LSPs in networks that support the flexi-grid, signaling to set up Label Switched Paths (LSPs) in networks that
and this document complements [RFC7792] by describing the support the flexi-grid. This document complements [RFC7792] by
requirement and extensions for OSPF-TE routing in a flexi-grid describing the requirement and extensions for OSPF-TE routing in a
network. flexi-grid network.
This document complements the efforts to provide extensions to Open This document complements the efforts to provide extensions to the
Short Path First (OSPF) Traffic-Engineering (TE) protocol so as to OSPF-TE protocol so as to support GMPLS control of flexi-grid
support GMPLS control of flexi-grid networks. networks.
2. Terminology 2. Terminology
For terminology related to flexi-grid, please consult [RFC7698] and For terminology related to flexi-grid, please consult [RFC7698] and
[G.694.1]. [G.694.1].
2.1. Conventions Used in this Document 2.1. 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", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in RFC-2119 [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
3. Requirements for Flexi-grid Routing 3. Requirements for Flexi-Grid Routing
The architecture for establishing LSPs in a Spectrum Switched The architecture for establishing LSPs in a Spectrum Switched Optical
optical Network (SSON) is described in [RFC7698]. Network (SSON) is described in [RFC7698].
A flexi-grid LSP occupies a specific frequency slot, i.e., a A flexi-grid LSP occupies one or multiple specific frequency slots.
frequency range. The process of computing a route and the The process of computing a route and the allocation of a frequency
allocation of a frequency slot is referred to as RSA (Routing and slot is referred to as "RSA" (Routing and Spectrum Assignment).
Spectrum Assignment). [RFC7698] describes three types of [RFC7698] describes three types of architectural approaches to RSA:
architectural approaches to RSA: combined RSA, separated RSA, and combined RSA, separated RSA, and routing and distributed SA. The
distributed SA. The first two approaches among them could be called first two approaches could be called "centralized SA" because the
"centralized SA" because the spectrum (frequency slot) assignment is spectrum (frequency slot) assignment is performed by a single entity
performed by a single entity before the signaling procedure. before the signaling procedure.
In the case of centralized SA, the assigned frequency slot is In the case of centralized SA, the assigned frequency slot is
specified in the RSVP-TE Path message during the signaling process. specified in the RSVP-TE Path message during the signaling process.
In the case of distributed SA, only the requested slot width of the In the case of routing and distributed SA, only the requested slot
flexi-grid LSP is specified in the Path message, allowing the width of the flexi-grid LSP is specified in the Path message,
involved network elements to select the frequency slot to be used. allowing the involved network elements to select the frequency slot
to be used.
If the capability of switching or converting the whole optical If the capability of switching or converting the whole optical
spectrum allocated to an optical spectrum LSP is not available at spectrum allocated to an optical spectrum LSP is not available at
nodes along the path of the LSP, the LSP is subject to the Optical nodes along the path of the LSP, the LSP is subject to the Optical
"Spectrum Continuity Constraint", as described in [RFC7698]. "Spectrum Continuity Constraint", as described in [RFC7698].
The remainder of this section states the additional extensions on The remainder of this section states the additional extensions on the
the routing protocols in a flexi-grid network. routing protocols in a flexi-grid network.
3.1. Available Frequency Ranges 3.1. Available Frequency Ranges
In the case of flexi-grids, the central frequency steps from 193.1 In the case of flexi-grids, the central frequency steps from 193.1
THz with 6.25 GHz granularity. The calculation method of central THz with 6.25 GHz granularity. The calculation method of central
frequency and the frequency slot width of a frequency slot are frequency and the frequency slot width of a frequency slot are
defined in [G.694.1], i.e., by using nominal central frequency n and defined in [G.694.1], i.e., by using nominal central frequency n and
the slot width m. the slot width m.
On a DWDM link, the allocated or in-use frequency slots do not On a DWDM link, the allocated or in-use frequency slots do not
overlap with each other. However, the border frequencies of two overlap with each other. However, the border frequencies of two
frequency slots may be the same frequency, i.e., the upper bound of frequency slots may be the same frequency, i.e., the upper bound of a
a frequency slot and the lower bound of the directly adjacent frequency slot and the lower bound of the directly adjacent frequency
frequency slot are the same. slot are the same.
Frequency Slot 1 Frequency Slot 2 Frequency Slot 1 Frequency Slot 2
+-----------+-----------------------+ +-----------+-----------------------+
| | | | | |
-9 -8 -7 -6 -5 -4 -3 -2 -1 0 1 2 3 4 5 6 7 8 9 10 11 -9 -8 -7 -6 -5 -4 -3 -2 -1 0 1 2 3 4 5 6 7 8 9 10 11
...+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--... ...+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--...
------------ ------------------------ ------------ ------------------------
^ ^ ^ ^
Central F = 193.1THz Central F = 193.1375 THz Central F = 193.1 THz Central F = 193.1375 THz
Slot width = 25 GHz Slot width = 50 GHz Slot width = 25 GHz Slot width = 50 GHz
Figure 1 - Two Frequency Slots on a Link Figure 1: Two Frequency Slots on a Link
Figure 1 shows two adjacent frequency slots on a link. The highest Figure 1 shows two adjacent frequency slots on a link. The highest
frequency of frequency slot 1 denoted by n=2 is the lowest frequency frequency of frequency slot 1 denoted by n=2 is the lowest frequency
of slot 2. In this example, it means that the frequency range from of slot 2. In this example, it means that the frequency range from
n=-2 to n=10 is unavailable to other flexi-grid LSPs. Available n=-2 to n=10 is unavailable to other flexi-grid LSPs. Available
central frequencies are advertised for m=1, which means that for an central frequencies are advertised for m=1, which means that for an
available central frequency n, the frequency slot from central available central frequency n, the frequency slot from central
frequency n-1 to central frequency n+1 is available. frequency n-1 to central frequency n+1 is available.
Hence, in order to clearly show which LSPs can be supported and what Hence, in order to clearly show which frequency slots are available
frequency slots are unavailable, the available frequency ranges are and can be used for LSP establishment and which frequency slots are
advertised by the routing protocol for the flexi-grid DWDM links. A unavailable, the availability of frequency slots is advertised by the
set of non-overlapping available frequency ranges are disseminated routing protocol for the flexi-grid DWDM links. A set of non-
in order to allow efficient resource management of flexi-grid DWDM overlapping available frequency ranges is disseminated in order to
links and RSA procedures which are described in Section 4.8 of allow efficient resource management of flexi-grid DWDM links and RSA
[RFC7698]. procedures, which are described in Section 4.8 of [RFC7698].
3.2. Application Compliance Considerations 3.2. Application Compliance Considerations
As described in [G.694.1], devices or applications that make use of As described in [G.694.1], devices or applications that make use of
the flexi-grid may not be capable of supporting every possible slot the flexi-grid may not be capable of supporting every possible slot
width or position (i.e., central frequency). In other words, width or position (i.e., central frequency). In other words,
applications or implementations may be defined where only a subset applications or implementations may be defined where only a subset of
of the possible slot widths and positions are required to be the possible slot widths and positions are required to be supported.
supported.
For example, an application could be defined where the nominal For example, an application could be defined where the nominal
central frequency granularity is 12.5 GHz (by only requiring values central frequency granularity is 12.5 GHz (by only requiring values
of n that are even) and that only requires slot widths as a multiple of n that are even) and the same application only requires slot
of 25 GHz (by only requiring values of m that are even). widths as a multiple of 25 GHz (by only requiring values of m that
are even).
Hence, in order to support all possible applications and Hence, in order to support all possible applications and
implementations the following information SHOULD be advertised for a implementations, the following information SHOULD be advertised for a
flexi-grid DWDM link: flexi-grid DWDM link:
o Channel Spacing (C.S.): as defined in [RFC7699] for flexi-grid, o Channel Spacing (C.S.): as defined in [RFC7699] for flexi-grid, is
is set to 5 to denote 6.25GHz. set to 5 to denote 6.25 GHz.
o Central frequency granularity: a multiplier of C.S.. o Central frequency granularity: a multiplier of C.S.
o Slot width granularity: a multiplier of 2*C.S.. o Slot width granularity: a multiplier of 2*C.S.
o Slot width range: two multipliers of the slot width granularity, o Slot width range: two multipliers of the slot width granularity,
each indicate the minimal and maximal slot width supported by a each indicating the minimal and maximal slot width supported by a
port respectively. port, respectively.
The combination of slot width range and slot width granularity can The combination of slot width range and slot width granularity can be
be used to determine the slot widths set supported by a port. used to determine the slot widths set supported by a port.
3.3. Comparison with Fixed-grid DWDM Links 3.3. Comparison with Fixed-Grid DWDM Links
In the case of fixed-grid DWDM links, each wavelength has a pre- In the case of fixed-grid DWDM links, each wavelength has a
defined central frequency and each wavelength maps to a pre-defined predefined central frequency. Each wavelength maps to a predefined
central frequency and the usable frequency range is implicit by the central frequency, and the usable frequency range is implicit by the
channel spacing. All the wavelengths on a DWDM link can be channel spacing. All the wavelengths on a DWDM link can be
identified with an identifier that mainly conveys its central identified with an identifier that mainly conveys its central
frequency as the label defined in [RFC6205], and the status of the frequency as the label defined in [RFC6205]; the status of the
wavelengths (available or not) can be advertised through a routing wavelengths (available or not) can be advertised through a routing
protocol. protocol.
Figure 2 shows a link that supports a fixed-grid with 50 GHz channel Figure 2 shows a link that supports a fixed-grid with 50 GHz channel
spacing. The central frequencies of the wavelengths are pre-defined spacing. The central frequencies of the wavelengths are predefined
by values of "n" and each wavelength occupies a fixed 50 GHz by values of "n", and each wavelength occupies a fixed 50 GHz
frequency range as described in [G.694.1]. frequency range as described in [G.694.1].
W(-2) | W(-1) | W(0) | W(1) | W(2) | W(-2) | W(-1) | W(0) | W(1) | W(2) |
...---------+-----------+-----------+-----------+-----------+----... ...---------+-----------+-----------+-----------+-----------+----...
| 50 GHz | 50 GHz | 50 GHz | 50 GHz | | 50 GHz | 50 GHz | 50 GHz | 50 GHz |
n=-2 n=-1 n=0 n=1 n=2 n=-2 n=-1 n=0 n=1 n=2
...---+-----------+-----------+-----------+-----------+----------... ...---+-----------+-----------+-----------+-----------+----------...
^ ^
Central F = 193.1THz Central F = 193.1 THz
Figure 2 - A Link Supports Fixed Wavelengths with 50 GHz Channel Figure 2: A Link Supports Fixed Wavelengths
Spacing with 50 GHz Channel Spacing
Unlike the fixed-grid DWDM links, on a flexi-grid DWDM link the slot Unlike the fixed-grid DWDM links, on a flexi-grid DWDM link, the slot
width of the frequency slot is flexible as described in section 3.1. width of the frequency slot is flexible, as described in Section 3.1.
That is, the value of m in the following formula [G.694.1] is That is, the value of m in the following formula from [G.694.1] is
uncertain before a frequency slot is actually allocated for a flexi- uncertain before a frequency slot is actually allocated for a flexi-
grid LSP. grid LSP.
Slot Width (GHz) = 12.5GHz * m Slot Width (in GHz) = 12.5GHz * m
For this reason, the available frequency slot/ranges are advertised
for a flexi-grid DWDM link instead of the specific "wavelengths"
points that are sufficient for a fixed-grid link. Moreover, this
advertisement is represented by the combination of Central Frequency
Granularity and Slot Width Granularity.
4. Extensions For this reason, the available frequency slots (or ranges) are
advertised for a flexi-grid DWDM link instead of the specific
"wavelength" points that are sufficient for a fixed-grid link.
Moreover, this advertisement is represented by the combination of
central frequency granularity and slot width granularity.
As described in [RFC7698], the network connectivity topology 4. Extensions
constructed by the links/nodes and node capabilities are the same as
for WSON, and can be advertised by the GMPLS routing protocols using
opaque LSAs [RFC3630] in the case of OSPF-TE [RFC4203] (refer to
section 6.2 of [RFC6163]). In the flexi-grid case, the available
frequency ranges instead of the specific "wavelengths" are
advertised for the link. This section defines the GMPLS OSPF-TE
extensions in support of advertising the available frequency ranges
for flexi-grid DWDM links.
4.1. ISCD Extensions for Flexi-grid The network-connectivity topology constructed by the links and/or
nodes and node capabilities are the same as for WSON, as described in
[RFC7698], and they can be advertised by the GMPLS routing protocols
using Opaque Link State Advertisements (LSAs) [RFC3630] in the case
of OSPF-TE [RFC4203] (refer to Section 6.2 of [RFC6163]). In the
flexi-grid case, the available frequency ranges, instead of the
specific "wavelengths", are advertised for the link. This section
defines the GMPLS OSPF-TE extensions in support of advertising the
available frequency ranges for flexi-grid DWDM links.
Value Type 4.1. Interface Switching Capability Descriptor (ISCD) Extensions for
Flexi-Grid
----- ---- This section defines a new value for the Switching Capability field
of the ISCD with a value of 152 and type name Flexi-Grid-LSC.
152 (TBA by IANA) Flexi-Grid-LSC Value Name
----- --------------
152 Flexi-Grid-LSC
Switching Capability and Encoding values MUST be used as follows: Switching Capability and Encoding values MUST be used as follows:
Switching Capability = Flexi-Grid-LSC Switching Capability = Flexi-Grid-LSC
Encoding Type = lambda [as defined in RFC3471] Encoding Type = lambda (as defined in [RFC3471])
When Switching Capability and Encoding fields are set to values as When the Switching Capability and Encoding fields are set to values
stated above, the Interface Switching Capability Descriptor is as stated above, the ISCD is interpreted as in [RFC4203] with the
interpreted as in [RFC4203] with the optional inclusion of one or optional inclusion of one or more Switching Capability Specific
more Switching Capability Specific Information sub-TLVs. Information (SCSI) sub-TLVs.
As the "Max LSP Bandwidth at priority x" (x from 0 to 7) fields in As the "Max LSP Bandwidth at priority x" (x from 0 to 7) fields in
the generic part of the Interface Switching Capability Descriptor the generic part of the ISCD [RFC4203] are not meaningful for flexi-
[RFC4203] are not meaningful for flexi-grid DWDM links, the values grid DWDM links, the values of these fields MUST be set to zero and
of these fields MUST be set to zero and MUST be ignored. The MUST be ignored. The SCSI as defined below provides the
Switching Capability Specific Information (SCSI) as defined below corresponding information for flexi-grid DWDM links.
provides the corresponding information for flexi-grid DWDM links.
4.1.1. Switching Capability Specific Information (SCSI) 4.1.1. Switching Capability Specific Information (SCSI)
The technology specific part of the Flexi-grid ISCD includes the [RFC8258] defines a Generalized SCSI for the ISCD. This document
available frequency spectrum resource as well as the max slot widths defines the Frequency Availability Bitmap as a new type of the
per priority information. The format of this flex-grid SCSI, the Generalized SCSI TLV. The technology-specific part of the flexi-grid
frequency available bitmap TLV, is depicted in the following figure: ISCD includes the available frequency-spectrum resource as well as
the information regarding max slot widths per priority. The format
of this flexi-grid SCSI, the Frequency Availability Bitmap sub-TLV,
is depicted in the following figure:
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 = 1 | Length | | Type = 11 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Priority | Reserved | | Priority | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Max Slot Width at Priority k | Unreserved padding ~ ~ Max Slot Width at Priority k | Unreserved Padding ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C.S. | Starting n | No. of Effective. Bits| | C.S. | Starting n | No. of Effective Bits |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bit Map ... ~ | Bitmap ... ~
~ ... | padding bits ~ ~ ... | padding bits ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type (16 bits): The type of this sub-TLV and is set to 1. Type (16 bits): The type of this sub-TLV (11).
Length (16 bits): The length of the value field of this sub-TLV, in Length (16 bits): The length of the value field of this sub-TLV in
octets. octets.
Priority (8 bits): A bitmap used to indicate which priorities Priority (8 bits): A bitmap used to indicate which priorities are
are being advertised. The bitmap is in ascending order, with the being advertised. The bitmap is in ascending order, with the
leftmost bit representing priority level 0 (i.e., the highest) and leftmost bit representing priority level 0 (i.e., the highest) and
the rightmost bit representing priority level 7 (i.e., the the rightmost bit representing priority level 7 (i.e., the lowest).
lowest). A bit is set (1) corresponding to each priority A bit is set (1) corresponding to each priority represented in the
represented in the sub-TLV, and clear (0) for each priority not sub-TLV and clear (0) for each priority not represented in the sub-
represented in the sub-TLV. At least one priority level MUST be TLV. At least one priority level MUST be advertised. If only one
advertised. If only one priority level is advertised, it MUST be at priority level is advertised, it MUST be at priority level 0.
priority level 0.
The Reserved field MUST be set to zero on transmission and MUST be Reserved: The Reserved field MUST be set to zero on transmission and
ignored on receipt. MUST be ignored on receipt.
Max Slot Width at priority k(16 bits): This field indicates maximal Max Slot Width at Priority k (16 bits): This field indicates maximal
frequency slot width supported at a particular priority level, up to frequency slot width supported at a particular priority level, up to
8. This field is set to max frequency slot width supported in the 8. This field is set to max frequency slot width supported in the
unit of 2*C.S., for a particular priority level. One field MUST be unit of 2*C.S., for a particular priority level. One field MUST be
present for each bit set in the Priority field, and is ordered to present for each bit set in the Priority field, and each present
match the Priority field. Fields MUST be present for priority field is ordered to match the Priority field. Fields MUST be present
levels that are indicated in the Priority field. for priority levels that are indicated in the Priority field.
Unreserved Padding (16 bits): The Padding field is used to Unreserved Padding (16 bits): The Padding field is used to ensure the
ensure the 32 bit alignment of Max Slot Width fields. When the 32-bit alignment of Max Slot Width at Priority k. When k is an odd
number of priorities is odd, the Unreserved Padding field MUST be number, the Unreserved Padding field MUST be included. When k is an
included. When the number of priorities is even, the Unreserved even number, the Unreserved Padding field MUST be omitted. This
Padding MUST be omitted. This field MUST be set to 0 and MUST be field MUST be set to 0 and MUST be ignored on receipt.
ignored on receipt.
C.S. (4 bits): As defined in [RFC7699] and it is currently set to 5. C.S. (4 bits): As defined in [RFC7699]; it is currently set to 5.
Starting n (16 bits): as defined in [RFC7699] and this value denotes Starting n (16 bits): As defined in [RFC7699]. This value denotes
the starting nominal central frequency point of the frequency the starting point of the nominal central frequency of the frequency
availability bitmap sub-TLV. availability bitmap sub-TLV.
Number of Effective Bits (12 bits): Indicates the number of No. of Effective Bits (12 bits): Indicates the number of effective
effective bits in the Bit Map field. bits in the Bitmap field.
Bit Map (variable): Indicates whether a basic frequency slot, Bitmap (variable): Indicates whether or not a basic frequency slot,
characterized by a nominal central frequency and a fixed m value of characterized by a nominal central frequency and a fixed m value of
1, is available or not for flexi-grid LSP setup. The first nominal 1, is available for flexi-grid LSP setup. The first nominal central
central frequency is the value of starting n and with the subsequent frequency is the value of starting n; subsequent nominal central
ones implied by the position in the bitmap. Note that when setting frequencies are implied by the position in the bitmap. Note that
to 1, it means that the corresponding central frequency is available setting to 1 indicates that the corresponding central frequency is
for a flexi-grid LSP with m=1; and when setting to 0, it means the available for a flexi-grid LSP with m=1 and setting to 0 indicates
corresponding central frequency is unavailable. Note that a the corresponding central frequency is unavailable. Note that a
centralized SA process will need to extend this to high values of m centralized SA process will need to extend this to high values of m
by checking a sufficient large number of consecutive basic frequency by checking a sufficiently large number of consecutive basic
slots that are available. frequency slots that are available.
Padding Bits (variable): Padded after the Bit Map to make it a padding bits (variable): Padded after the Bitmap to make it a
multiple of four bytes if necessary. Padding bits MUST be set to 0 multiple of four bytes, if necessary. Padding bits MUST be set to 0
and MUST be ignored on receipt. and MUST be ignored on receipt.
An example is provided in section 4.1.2. An example is provided in Section 4.1.2.
4.1.2. An SCSI Example 4.1.2. An SCSI Example
Figure 3 shows an example of the available frequency spectrum Figure 3 shows an example of the available frequency spectrum
resource of a flexi-grid DWDM link. resource of a flexi-grid DWDM link.
-9 -8 -7 -6 -5 -4 -3 -2 -1 0 1 2 3 4 5 6 7 8 9 10 11 -9 -8 -7 -6 -5 -4 -3 -2 -1 0 1 2 3 4 5 6 7 8 9 10 11
...+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--... ...+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--...
|--Available Frequency Range--| |--Available Frequency Range--|
Figure 3 - Flexi-grid DWDM Link Example Figure 3: Flexi-Grid DWDM Link Example
The symbol "+" represents the allowed nominal central frequency. The The symbol "+" represents the allowed nominal central frequency. The
symbol "--" represents a central frequency granularity of 6.25 GHz, symbol "--" represents a central frequency granularity of 6.25 GHz,
as currently be standardized in [G.694.1]. The number on the top of which is currently standardized in [G.694.1]. The number on the top
the line represents the "n" in the frequency calculation formula of the line represents the "n" in the frequency calculation formula
(193.1 + n * 0.00625). The nominal central frequency is 193.1 THz (193.1 + n * 0.00625). The nominal central frequency is 193.1 THz
when n equals zero. when n equals zero.
In this example, it is assumed that the lowest nominal central In this example, it is assumed that the lowest nominal central
frequency supported is n= -9 and the highest is n=11. Note they frequency supported is n=-9 and the highest is n=11. Note they
cannot be used as a nominal central frequency for setting up a LSP, cannot be used as a nominal central frequency for setting up an LSP,
but merely as the way to express the supported frequency range. but merely as the way to express the supported frequency range.
Using the encoding defined in Section 4.1.1, the relevant fields to Using the encoding defined in Section 4.1.1, the relevant fields to
express the frequency resource availability can be filled as below: express the frequency resource availability can be filled as 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 | Length | | Type = 11 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Priority | Reserved | | Priority | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Max Slot Width at Priority k | Unreserved padding ~ ~ Max Slot Width at Priority k | Unreserved Padding ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 5 | Starting n (-9) | No. of Effec. Bits(21)| | 5 | Starting n (-9) | No. of Effec. Bits(21)|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0|0|0|0|1|1|1|1|1|1|1|1|1|0|0|0|0| padding bits (0s) | |0|0|0|0|0|0|0|0|1|1|1|1|1|1|1|1|1|0|0|0|0| padding bits (0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
In the above example, the starting n is selected to be the lowest In the above example, the starting n is selected to be the lowest
nominal central frequency, i.e. -9. It is observed from the bit map nominal central frequency, i.e., -9. It is observed from the bitmap
that n = -1 to 7 can be used to set up LSPs. Note other starting n that n=-1 to 7 can be used to set up LSPs. Note other starting n
values can be chosen to represent the bit map, for example, the values can be chosen to represent the bitmap; for example, the first
first available nominal central frequency (a.k.a., the first available nominal central frequency (a.k.a., the first available
available basic frequency slot) can be chosen and the SCSI will be basic frequency slot) can be chosen, and the SCSI will be expressed
expressed as the following: as the following:
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 = 1 | Length | | Type = 11 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Priority | Reserved | | Priority | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Max Slot Width at Priority k | Unreserved padding ~ ~ Max Slot Width at Priority k | Unreserved Padding ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 5 | Starting n (-1) | No. of Effec. Bits(9)| | 5 | Starting n (-1) | No. of Effec. Bits(9)|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1|1|1|1|1|1|1|1|1| padding bits (0s) | |1|1|1|1|1|1|1|1|1| padding bits (0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This denotes that other than the advertised available nominal This encoding denotes that, other than the advertised available
central frequencies, the other nominal central frequencies within nominal central frequencies, the other nominal central frequencies
the whole frequency range supported by the link are not available within the whole frequency range supported by the link are not
for flexi-grid LSP set up. available for flexi-grid LSP setup.
If a LSP with slot width m equals to 1 is set up using this link, If an LSP with slot width m equal to 1 is set up using this link, say
say using n= -1, then the SCSI information is updated to be the using n=-1, then the SCSI information is updated to be the following:
following:
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 = 1 | Length | | Type = 11 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Priority | Reserved | | Priority | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Max Slot Width at Priority k | Unreserved padding ~ ~ Max Slot Width at Priority k | Unreserved Padding ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 5 | Starting n (-1) | No. of Effec. Bits(9)| | 5 | Starting n (-1) | No. of Effec. Bits(9)|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|1|1|1|1|1|1|1| padding bits (0s) | |0|0|1|1|1|1|1|1|1| padding bits (0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
4.2. Extensions to Port Label Restriction sub-TLV 4.2. Extensions to the Port Label Restrictions Field
As described in Section 3.2, a port that supports flexi-grid may As described in Section 3.2, a port that supports flexi-grid may
support only a restricted subset of the full flexible grid. The support only a restricted subset of the full flexible grid. The Port
Port Label Restriction field is defined in [RFC7579]. It can be Label Restrictions field is defined in [RFC7579]. It can be used to
used to describe the label restrictions on a port and is carried in describe the label restrictions on a port and is carried in the top-
the top-level Link TLV as specified in [RFC7580]. A new restriction level Link TLV as specified in [RFC7580]. A new restriction type,
type, the flexi-grid Restriction Type, is defined here to specify the flexi-grid Restriction Type, is defined here to specify the
the restrictions on a port to support flexi-grid. restrictions on a port to support flexi-grid.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MatrixID | RstType = 5 | Switching Cap | Encoding | | MatrixID | RstType = 5 | Switching Cap | Encoding |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C.S. | C.F.G | S.W.G | Reserved | | C.S. | C.F.G | S.W.G | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Min Slot Width | Reserved | | Min Slot Width | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 13, line 5 skipping to change at page 12, line 27
RstType (Restriction Type, 8 bits): Takes the value of 5 to indicate RstType (Restriction Type, 8 bits): Takes the value of 5 to indicate
the restrictions on a port to support flexi-grid. the restrictions on a port to support flexi-grid.
Switching Cap (Switching Capability, 8 bits): As defined in Switching Cap (Switching Capability, 8 bits): As defined in
[RFC7579], MUST be consistent with the one specified in ISCD as [RFC7579], MUST be consistent with the one specified in ISCD as
described in Section 4.1. described in Section 4.1.
Encoding (8 bits): As defined in [RFC7579], MUST be consistent with Encoding (8 bits): As defined in [RFC7579], MUST be consistent with
the one specified in ISCD as described in Section 4.1. the one specified in ISCD as described in Section 4.1.
C.S. (4 bits): As defined in [RFC7699] and for flexi-grid is 5 to C.S. (4 bits): As defined in [RFC7699]. For flexi-grid, it is 5 to
denote 6.25GHz. denote 6.25 GHz.
C.F.G (Central Frequency Granularity, 8 bits): A positive integer. C.F.G (Central Frequency Granularity, 8 bits): A positive integer.
Its value indicates the multiple of C.S., in terms of central Its value indicates the multiple of C.S., in terms of central
frequency granularity. frequency granularity.
S.W.G (Slot Width Granularity, 8 bits): A positive integer. Its S.W.G (Slot Width Granularity, 8 bits): A positive integer. Its
value indicates the multiple of 2*C.S., in terms of slot width value indicates the multiple of 2*C.S., in terms of slot width
granularity. granularity.
Min Slot Width (16 bits): A positive integer. Its value indicates Min Slot Width (16 bits): A positive integer. Its value indicates
the multiple of 2*C.S. (GHz), in terms of the supported minimal slot the multiple of 2*C.S. (in GHz), in terms of the supported minimal
width. slot width.
The Reserved field MUST be set to zero on transmission and SHOULD be Reserved: The Reserved field MUST be set to zero on transmission and
ignored on receipt. SHOULD be ignored on receipt.
5. IANA Considerations 5. IANA Considerations
5.1. New Switching Type 5.1. New ISCD Switching Type
Upon approval of this document, IANA will make the assignment in the IANA has made the following assignment in the "Switching Types" sub-
"Switching Types" section of the "GMPLS Signaling Parameters" registry of the "Generalized Multi-Protocol Label Switching (GMPLS)
registry located at http://www.iana.org/assignments/gmpls-sig- Signaling Parameters" registry located at
parameters: <https://www.iana.org/assignments/gmpls-sig-parameters>:
Value Name Reference Value Name Reference
------- ---------------- ----------
152 Flexi-Grid-LSC RFC 8363
--------- -------------------------- ---------- 5.2. New SCSI Type
152 (*) Flexi-Grid-LSC [This.I-D] This document defines a new generalized SCSI sub-TLV that is carried
in the Interface Switching Capability Descriptors [RFC4203] when the
Switching Type is set to Flexi-Grid-LSC.
(*) Suggested value IANA has made the following assignment in the "Generalized SCSI
(Switching Capability Specific Information) TLV Types" sub-registry
[RFC8258] of the "Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Parameters" registry located at
<https://www.iana.org/assignments/gmpls-sig-parameters>:
5.2. New Sub-TLV Value SCSI-TLV Switching Type Reference
----- ----------------------------- -------------- ---------
11 Frequency Availability Bitmap 152 RFC 8363
This document defines one new sub-TLV that are carried in the 6. Security Considerations
Interface Switching Capability Descriptors [RFC4203] with Signal
Type Flexi-Grid-LSC.
Upon approval of this document, IANA will create and maintain a new This document extends [RFC4203] and [RFC7580] to carry flexi-grid-
sub-registry, the "Types for sub-TLVs of Flexi-Grid-LSC SCSI (Switch specific information in OSPF Opaque LSAs. This document does not
Capability-Specific Information)" registry under the "Open Shortest introduce any further security issues other than those discussed in
Path First (OSPF) Traffic Engineering TLVs" registry, see [RFC3630] and [RFC4203]. To be more specific, the security
http://www.iana.org/assignments/ospf-traffic-eng-tlvs/ospf-traffic- mechanisms described in [RFC2328], which apply to Opaque LSAs carried
eng-tlvs.xml, with the sub-TLV types as follows: in OSPF, still apply. An analysis of the OSPF security is provided
in [RFC6863] and applies to the extensions to OSPF in this document
as well.
This document defines new sub-TLV types as follows: 7. References
Value Sub-TLV Reference 7.1. Normative References
--------- -------------------------- ----------
0 Reserved [This.I-D]
1 Frequency availability bitmap [This.I-D]
6. Implementation Status [G.694.1] International Telecommunication Union, "Spectral grids for
WDM applications: DWDM frequency grid", ITU-T
Recommendation G.694.1, February 2012,
<https://www.itu.int/rec/T-REC-G.694.1/en>.
[RFC Editor Note: Please remove this entire section prior to [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
publication as an RFC.] Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
This section records the status of known implementations of the [RFC3471] Berger, L., Ed., "Generalized Multi-Protocol Label
protocol defined by this specification at the time of posting of Switching (GMPLS) Signaling Functional Description",
this Internet-Draft, and is based on a proposal described in RFC RFC 3471, DOI 10.17487/RFC3471, January 2003,
7942. The description of implementations in this section is <https://www.rfc-editor.org/info/rfc3471>.
intended to assist the IETF in its decision processes in progressing
drafts to RFCs. Please note that the listing of any individual
implementation here does not imply endorsement by the IETF.
Furthermore, no effort has been spent to verify the information
presented here that was supplied by IETF contributors. This is not
intended as, and must not be construed to be, a catalog of available
implementations or their features. Readers are advised to note that
other implementations may exist.
According to RFC 7942, "this will allow reviewers and working groups [RFC4203] Kompella, K., Ed. and Y. Rekhter, Ed., "OSPF Extensions in
to assign due consideration to documents that have the benefit of Support of Generalized Multi-Protocol Label Switching
running code, which may serve as evidence of valuable (GMPLS)", RFC 4203, DOI 10.17487/RFC4203, October 2005,
experimentation and feedback that have made the implemented <https://www.rfc-editor.org/info/rfc4203>.
protocols more mature. It is up to the individual working groups to
use this information as they see fit.
6.1. Centre Tecnologic de Telecomunicacions de Catalunya (CTTC) [RFC6205] Otani, T., Ed. and D. Li, Ed., "Generalized Labels for
Lambda-Switch-Capable (LSC) Label Switching Routers",
RFC 6205, DOI 10.17487/RFC6205, March 2011,
<https://www.rfc-editor.org/info/rfc6205>.
Organization Responsible for the Implementation: CTTC - Centre [RFC7579] Bernstein, G., Ed., Lee, Y., Ed., Li, D., Imajuku, W., and
Tecnologic de Telecomunicacions de Catalunya (CTTC), Optical J. Han, "General Network Element Constraint Encoding for
Networks and Systems Department, http://wikiona.cttc.es. GMPLS-Controlled Networks", RFC 7579,
DOI 10.17487/RFC7579, June 2015,
<https://www.rfc-editor.org/info/rfc7579>.
Implementation Name and Details: ADRENALINE testbed, [RFC7580] Zhang, F., Lee, Y., Han, J., Bernstein, G., and Y. Xu,
http://networks.cttc.es/experimental-testbeds/ "OSPF-TE Extensions for General Network Element
Constraints", RFC 7580, DOI 10.17487/RFC7580, June 2015,
<https://www.rfc-editor.org/info/rfc7580>.
Brief Description: Experimental testbed implementation of [RFC7699] Farrel, A., King, D., Li, Y., and F. Zhang, "Generalized
GMPLS/PCE control plane. Labels for the Flexi-Grid in Lambda Switch Capable (LSC)
Label Switching Routers", RFC 7699, DOI 10.17487/RFC7699,
November 2015, <https://www.rfc-editor.org/info/rfc7699>.
Level of Maturity: Implemented as extensions to a mature [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
GMLPS/PCE control plane. It is limited to research / prototyping 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
stages but it has been used successfully for more than the last five May 2017, <https://www.rfc-editor.org/info/rfc8174>.
years.
Coverage: Support for the 64 bit label [RFC7699] for flexi-grid [RFC8258] Ceccarelli, D. and L. Berger, "Generalized SCSI: A Generic
as described in this document, with available label set encoded as Structure for Interface Switching Capability Descriptor
bitmap. (ISCD) Switching Capability Specific Information (SCSI)",
RFC 8258, DOI 10.17487/RFC8258, October 2017,
<https://www.rfc-editor.org/info/rfc8258>.
It is expected that this implementation will evolve to follow the 7.2. Informative References
evolution of this document.
Licensing: Proprietary [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328,
DOI 10.17487/RFC2328, April 1998,
<https://www.rfc-editor.org/info/rfc2328>.
Implementation Experience: Implementation of this document [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering
reports no issues. General implementation experience has been (TE) Extensions to OSPF Version 2", RFC 3630,
reported in a number of journal papers. Contact Ramon Casellas for DOI 10.17487/RFC3630, September 2003,
more information or see http://networks.cttc.es/publications/? <https://www.rfc-editor.org/info/rfc3630>.
search=GMPLS&research_area=optical-networks-systems
Contact Information: Ramon Casellas: ramon.casellas@cttc.es [RFC6163] Lee, Y., Ed., Bernstein, G., Ed., and W. Imajuku,
"Framework for GMPLS and Path Computation Element (PCE)
Control of Wavelength Switched Optical Networks (WSONs)",
RFC 6163, DOI 10.17487/RFC6163, April 2011,
<https://www.rfc-editor.org/info/rfc6163>.
Interoperability: No report. [RFC6863] Hartman, S. and D. Zhang, "Analysis of OSPF Security
According to the Keying and Authentication for Routing
Protocols (KARP) Design Guide", RFC 6863,
DOI 10.17487/RFC6863, March 2013,
<https://www.rfc-editor.org/info/rfc6863>.
7. Acknowledgments [RFC7688] Lee, Y., Ed. and G. Bernstein, Ed., "GMPLS OSPF
Enhancement for Signal and Network Element Compatibility
for Wavelength Switched Optical Networks", RFC 7688,
DOI 10.17487/RFC7688, November 2015,
<https://www.rfc-editor.org/info/rfc7688>.
[RFC7698] Gonzalez de Dios, O., Ed., Casellas, R., Ed., Zhang, F.,
Fu, X., Ceccarelli, D., and I. Hussain, "Framework and
Requirements for GMPLS-Based Control of Flexi-Grid Dense
Wavelength Division Multiplexing (DWDM) Networks",
RFC 7698, DOI 10.17487/RFC7698, November 2015,
<https://www.rfc-editor.org/info/rfc7698>.
[RFC7792] Zhang, F., Zhang, X., Farrel, A., Gonzalez de Dios, O.,
and D. Ceccarelli, "RSVP-TE Signaling Extensions in
Support of Flexi-Grid Dense Wavelength Division
Multiplexing (DWDM) Networks", RFC 7792,
DOI 10.17487/RFC7792, March 2016,
<https://www.rfc-editor.org/info/rfc7792>.
Acknowledgments
This work was supported in part by the FP-7 IDEALIST project under This work was supported in part by the FP-7 IDEALIST project under
grant agreement number 317999. grant agreement number 317999.
This work was supported in part by NSFC Project 61201260. This work was supported in part by NSFC Project 61201260.
8. Security Considerations Contributors
This document extends [RFC4203] and [RFC7580] to carry flex-grid
specific information in OSPF Opaque LSAs. This document does not
introduce any further security issues other than those discussed in
[RFC3630], [RFC4203]. To be more specific, the security mechanisms
described in [RFC2328] which apply to Opaque LSAs carried in OSPF
still apply. An analysis of the OSPF security is provided in
[RFC6863] and applies to the extensions to OSPF in this document as
well.
9. Contributors' Addresses
Adrian Farrel Adrian Farrel
Juniper Networks Juniper Networks
Email: afarrel@juniper.net Email: afarrel@juniper.net
Fatai Zhang Fatai Zhang
Huawei Technologies Huawei Technologies
Email: zhangfatai@huawei.com Email: zhangfatai@huawei.com
Lei Wang, Lei Wang
Beijing University of Posts and Telecommunications Beijing University of Posts and Telecommunications
Email: wang.lei@bupt.edu.cn Email: wang.lei@bupt.edu.cn
Guoying Zhang, Guoying Zhang
China Academy of Information and Communication Technology China Academy of Information and Communication Technology
Email: zhangguoying@ritt.cn
10. References
10.1. Normative References
[RFC2119] S. Bradner, "Key words for use in RFCs to indicate
requirements levels", RFC 2119, March 1997.
[G.694.1] ITU-T Recommendation G.694.1 (revision 2), "Spectral grids Email: zhangguoying@ritt.cn
for WDM applications: DWDM frequency grid", February 2012.
[RFC4203] K. Kompella, Y. Rekhter, " OSPF Extensions in Support of
Generalized Multi-Protocol Label Switching (GMPLS)",
October 2005.
[RFC7579] Bernstein, G., Lee, Y., Li, D., and W. Imajuku, "General
Network Element Constraint Encoding for GMPLS Controlled
Networks", RFC 7579, June 2015.
[RFC7580] F. Zhang, Y. Lee, J. Han, G. Bernstein and Y. Xu, "OSPF-TE
Extensions for General Network Element Constraints ", RFC
7580, June 2015.
[RFC6205] T. Otani and D. Li, "Generalized Labels for Lambda-Switch-
Capable (LSC) Label Switching Routers", RFC 6205, March
2011.
[RFC7699] King, D., Farrel, A. and Y. Li, "Generalized Labels for
the Flexi-Grid in Lambda Switch Capable (LSC) Label
Switching Routers", RFC7699, September 2015.
10.2. Informative References
[RFC6163] Y. Lee, G. Bernstein and W. Imajuku, "Framework for GMPLS
and Path Computation Element (PCE) Control of Wavelength
Switched Optical Networks (WSONs)", RFC 6163, April 2011.
[RFC7792] F.Zhang et al, "RSVP-TE Signaling Extensions in support of
Flexible-grid", RFC 7792, November 2015.
[RFC7698] Gonzalez de Dios, O., Casellas R., Zhang, F., Fu, X.,
Ceccarelli, D., and I. Hussain, "Framework and
Requirements for GMPLS based control of Flexi-grid DWDM
networks', RFC 7698, August 2015.
[RFC7688] Y. Lee and G. Bernstein, "GMPLS OSPF Enhancement for
Signal and Network Element Compatibility for Wavelength
Switched Optical Networks ", RFC7688, August 2015.
[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998.
[RFC3630] D. Katz, K. Kompella, D. Yeung, " Traffic Engineering
(TE) Extensions to OSPF Version 2", September 2003.
[RFC6863] Hartman, S. and D. Zhang, "Analysis of OSPF Security
According to the Keying and Authentication for Routing
Protocols (KARP) Design Guide", RFC 6863, March 2013.
Authors' Addresses Authors' Addresses
Xian Zhang Xian Zhang
Huawei Technologies Huawei Technologies
Email: zhang.xian@huawei.com Email: zhang.xian@huawei.com
Haomian Zheng Haomian Zheng
Huawei Technologies Huawei Technologies
Email: zhenghaomian@huawei.com Email: zhenghaomian@huawei.com
Ramon Casellas, Ph.D. Ramon Casellas, Ph.D.
CTTC CTTC
Spain Spain
Phone: +34 936452916 Phone: +34 936452916
Email: ramon.casellas@cttc.es Email: ramon.casellas@cttc.es
Oscar Gonzalez de Dios Oscar Gonzalez de Dios
Telefonica Investigacion y Desarrollo Telefonica Investigacion y Desarrollo
Emilio Vargas 6 Emilio Vargas 6
Madrid, 28045 Madrid, 28045
Spain Spain
Phone: +34 913374013 Phone: +34 913374013
Email: ogondio@tid.es Email: oscar.gonzalezdedios@telefonica.com
Daniele Ceccarelli Daniele Ceccarelli
Ericsson Ericsson
Via A. Negrone 1/A Via A. Negrone 1/A
Genova - Sestri Ponente Genova - Sestri Ponente
Italy Italy
Email: daniele.ceccarelli@ericsson.com Email: daniele.ceccarelli@ericsson.com
 End of changes. 149 change blocks. 
417 lines changed or deleted 395 lines changed or added

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