draft-ietf-ccamp-flexible-grid-ospf-ext-08.txt   draft-ietf-ccamp-flexible-grid-ospf-ext-09.txt 
CCAMP Working Group Xian Zhang CCAMP Working Group Xian Zhang
Internet-Draft Haomian Zheng Internet-Draft Haomian Zheng
Intended status: Standards Track Huawei Intended status: Standards Track Huawei
Ramon Casellas Ramon Casellas
CTTC CTTC
O. Gonzalez de Dios O. Gonzalez de Dios
Telefonica Telefonica
D. Ceccarelli D. Ceccarelli
Ericsson Ericsson
Expires: August 8, 2017 February 8, 2017 Expires: August 17, 2017 February 17, 2017
GMPLS OSPF-TE Extensions in support of Flexi-grid DWDM networks GMPLS OSPF-TE Extensions in support of Flexi-grid DWDM networks
draft-ietf-ccamp-flexible-grid-ospf-ext-08.txt draft-ietf-ccamp-flexible-grid-ospf-ext-09.txt
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 a set of nominal central
frequencies, channel spacings, and the concept of the "frequency frequencies, channel spacings, and the concept of the "frequency
slot". Corresponding techniques for data-plane connections are known slot". Corresponding techniques for data-plane connections are known
as flexi-grid. as flexi-grid.
skipping to change at page 2, line 10 skipping to change at page 2, line 10
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 8, 2017. This Internet-Draft will expire on August 17, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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
warranty as described in the Simplified BSD License. warranty as 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. ISCD Extensions for Flexi-grid .......................... 7
4.1.1. Switching Capability Specific Information (SCSI).... 8 4.1.1. Switching Capability Specific Information (SCSI).... 8
4.1.2. An SCSI Example ................................... 10 4.1.2. An SCSI Example ................................... 10
4.2. Extensions to Port Label Restriction sub-TLV ........... 12 4.2. Extensions to Port Label Restriction sub-TLV ........... 12
5. IANA Considerations ......................................... 13 5. IANA Considerations ......................................... 13
5.1. New Switching Type ..................................... 13 5.1. New Switching Type ..................................... 13
5.2. New Sub-TLV ............................................ 13 5.2. New Sub-TLV ............................................ 13
6. Implementation Status ....................................... 14 6. Implementation Status ....................................... 14
6.1. Centre Tecnologic de Telecomunicacions de Catalunya (CTTC)14 6.1. Centre Tecnologic de Telecomunicacions de Catalunya (CTTC)14
7. Acknowledgments ............................................. 15 7. Acknowledgments ............................................. 15
skipping to change at page 5, line 29 skipping to change at page 5, line 29
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 LSPs can be supported and what
frequency slots are unavailable, the available frequency ranges are frequency slots are unavailable, the available frequency ranges are
advertised by the routing protocol for the flexi-grid DWDM links. A advertised by the routing protocol for the flexi-grid DWDM links. A
set of non-overlapping available frequency ranges MUST be set of non-overlapping available frequency ranges are disseminated
disseminated in order to allow efficient resource management of in order to allow efficient resource management of flexi-grid DWDM
flexi-grid DWDM links and RSA procedures which are described in links and RSA procedures which are described in Section 4.8 of
Section 4.8 of [RFC7698]. [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 the possible slot widths and positions are required to be of 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 that only requires slot widths as a multiple
of 25 GHz (by only requiring values of m that are even). 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 set to 5 to denote 6.25GHz. is set to 5 to denote 6.25GHz.
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,
skipping to change at page 7, line 35 skipping to change at page 7, line 35
For this reason, the available frequency slot/ranges are advertised For this reason, the available frequency slot/ranges are advertised
for a flexi-grid DWDM link instead of the specific "wavelengths" for a flexi-grid DWDM link instead of the specific "wavelengths"
points that are sufficient for a fixed-grid link. Moreover, this points that are sufficient for a fixed-grid link. Moreover, this
advertisement is represented by the combination of Central Frequency advertisement is represented by the combination of Central Frequency
Granularity and Slot Width Granularity. Granularity and Slot Width Granularity.
4. Extensions 4. Extensions
As described in [RFC7698], the network connectivity topology As described in [RFC7698], the network connectivity topology
constructed by the links/nodes and node capabilities are the same as constructed by the links/nodes and node capabilities are the same as
for WSON, and can be advertised by the GMPLS routing protocols for WSON, and can be advertised by the GMPLS routing protocols using
(refer to section 6.2 of [RFC6163]). In the flexi-grid case, the opaque LSAs [RFC3630] in the case of OSPF-TE [RFC4203] (refer to
available frequency ranges instead of the specific "wavelengths" are 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 advertised for the link. This section defines the GMPLS OSPF-TE
extensions in support of advertising the available frequency ranges extensions in support of advertising the available frequency ranges
for flexi-grid DWDM links. for flexi-grid DWDM links.
4.1. ISCD Extensions for Flexi-grid 4.1. ISCD Extensions for Flexi-grid
Value Type Value Type
----- ---- ----- ----
skipping to change at page 9, line 12 skipping to change at page 9, line 12
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 being advertised. The bitmap is in ascending order, with the are 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). A bit is set (1) corresponding to each priority lowest). A bit is set (1) corresponding to each priority
represented in the sub-TLV, and clear (0) for each priority not represented in the sub-TLV, and clear (0) for each priority not
represented in the sub-TLV. At least one priority level MUST be represented in the sub-TLV. At least one priority level MUST be
advertised, if only one priority level is advertised, it MUST be advertised. If only one priority level is advertised, it MUST be at
at priority level 0. priority level 0.
The Reserved field MUST be set to zero on transmission and MUST be The Reserved field MUST be set to zero on transmission and MUST be
ignored on receipt. 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 is ordered to
match the Priority field. Fields MUST be present for priority match the Priority field. Fields MUST be present for priority
levels that are indicated in the Priority field. 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 32 bit alignment of Max Slot Width fields. When ensure the 32 bit alignment of Max Slot Width fields. When the
the number of priorities is odd, the Unreserved Padding field number of priorities is odd, the Unreserved Padding field MUST be
MUST be included. When the number of priorities is even, the included. When the number of priorities is even, the Unreserved
Unreserved Padding MUST be omitted. This field MUST be set to 0 and Padding MUST be omitted. This field MUST be set to 0 and MUST be
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] and 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] and this value denotes
the starting nominal central frequency point of the frequency the starting nominal central frequency point of the frequency
availability bitmap sub-TLV. availability bitmap sub-TLV.
Number of Effective Bits (12 bits): Indicates the number of Number of Effective Bits (12 bits): Indicates the number of
effective bits in the Bit Map field. effective bits in the Bit Map field.
skipping to change at page 12, line 23 skipping to change at page 12, line 23
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 Port Label Restriction sub-TLV
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 Label Restriction sub-TLV is defined in [RFC7579]. It can be Port Label Restriction field is defined in [RFC7579]. It can be
used to describe the label restrictions on a port and is carried in used to describe the label restrictions on a port and is carried in
the top-level Link TLV as specified in [RFC7580]. A new restriction the top-level Link TLV as specified in [RFC7580]. A new restriction
type, the flexi-grid Restriction Type, is defined here to specify type, the flexi-grid Restriction Type, is defined here to specify
the restrictions on a port to support flexi-grid. the 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 16, line 8 skipping to change at page 16, line 8
introduce any further security issues other than those discussed in introduce any further security issues other than those discussed in
[RFC3630], [RFC4203]. To be more specific, the security mechanisms [RFC3630], [RFC4203]. To be more specific, the security mechanisms
described in [RFC2328] which apply to Opaque LSAs carried in OSPF described in [RFC2328] which apply to Opaque LSAs carried in OSPF
still apply. An analysis of the OSPF security is provided in still apply. An analysis of the OSPF security is provided in
[RFC6863] and applies to the extensions to OSPF in this document as [RFC6863] and applies to the extensions to OSPF in this document as
well. well.
9. Contributors' Addresses 9. Contributors' Addresses
Adrian Farrel Adrian Farrel
Old Dog Consulting Juniper Networks
Email: adrian@olddog.co.uk Email: afarrel@juniper.net
Fatai Zhang Fatai Zhang
Huawei Technologies Huawei Technologies
Email: zhangfatai@huawei.com Email: zhangfatai@huawei.com
Lei Wang, Lei Wang,
ZTE 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 Email: zhangguoying@ritt.cn
10. References 10. References
10.1. Normative References 10.1. Normative References
 End of changes. 13 change blocks. 
25 lines changed or deleted 26 lines changed or added

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