draft-ietf-ccamp-ospf-availability-extension-10.txt   draft-ietf-ccamp-ospf-availability-extension-11.txt 
Network Working Group H. Long, M.Ye Network Working Group H. Long, M.Ye
Internet Draft Huawei Technologies Co., Ltd Internet Draft Huawei Technologies Co., Ltd
Intended status: Standards Track G. Mirsky Intended status: Standards Track G. Mirsky
ZTE ZTE
A.D'Alessandro A.D'Alessandro
Telecom Italia S.p.A Telecom Italia S.p.A
H. Shah H. Shah
Ciena Ciena
Expires: February 2018 August 8, 2017 Expires: April 2018 October 24, 2017
OSPF-TE Link Availability Extension for Links with Variable Discrete OSPF-Traffic Engineering Link Availability Extension for Links with
Bandwidth Variable Discrete Bandwidth
draft-ietf-ccamp-ospf-availability-extension-10.txt draft-ietf-ccamp-ospf-availability-extension-11.txt
Abstract Abstract
A network may contain links with variable discrete bandwidth, e.g., A network may contain links with variable discrete bandwidth, e.g.,
copper, radio, etc. The bandwidth of such links may change copper, radio, etc. The bandwidth of such links may change
discretely in reaction to changing external environment. discretely in reaction to changing external environment.
Availability is typically used for describing such links during Availability is typically used for describing such links during
network planning. This document defines a new type of the network planning. This document defines a new type of the
Generalized Switching Capability-specific information (SCSI) TLV to Generalized Switching Capability-specific information (SCSI) TLV to
extend the Generalized Multi-Protocol Label Switching (GMPLS) Open extend the Generalized Multi-Protocol Label Switching (GMPLS) Open
skipping to change at page 2, line 16 skipping to change at page 2, line 16
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 February 8, 2018. This Internet-Draft will expire on April 24, 2018.
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. Overview .................................................... 4 2. Acronyms .................................................... 3
3. TE Metric Extension to OSPF-TE............................... 4 3. Overview .................................................... 4
3.1. Availability SCSI-TLV................................... 4 4. TE Metric Extension to OSPF-TE............................... 4
3.2. Processing Procedures................................... 5 4.1. Availability SCSI-TLV................................... 4
4. Security Considerations...................................... 6 4.2. Processing Procedures................................... 5
5. IANA Considerations ......................................... 6 5. Security Considerations...................................... 6
6. References .................................................. 7 6. IANA Considerations ......................................... 6
6.1. Normative References.................................... 7 7. References .................................................. 7
6.2. Informative References.................................. 7 7.1. Normative References.................................... 7
7. Acknowledgments ............................................. 8 7.2. Informative References.................................. 7
8. Acknowledgments ............................................. 8
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", "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
The following acronyms are used in this draft: capitals, as shown here.
GMPLS Generalized Multi-Protocol Label Switching
LSA Link State Advertisement
ISCD Interface Switching Capability Descriptor
LSP Label Switched Path
OSPF Open Shortest Path First
PSN Packet Switched Network
SCSI Switching Capability-specific information
SNR Signal-to-noise Ratio
SONET-SDH Synchronous Optical Network - Synchronous Digital
Hierarchy
SPF Shortest Path First
TE Traffic Engineering
TLV Type Length Value
1. Introduction 1. Introduction
Some data plane technologies, e.g., microwave, and copper, allow Some data plane technologies, e.g., microwave, and copper, allow
seamless change of maximum physical bandwidth through a set of known seamless change of maximum physical bandwidth through a set of known
discrete values. The parameter, availability, as described in discrete values. The parameter, availability, as described in
[G.827], [F.1703] and [P.530] is often used to describe the link [G.827], [F.1703] and [P.530] is often used to describe the link
capacity. The availability is a time scale, representing a proportion capacity. The availability is a time scale, representing a proportion
of the operating time that the requested bandwidth is ensured. To of the operating time that the requested bandwidth is ensured. To
set up an LSP across these links, availability information is set up an LSP across these links, availability information is
skipping to change at page 4, line 18 skipping to change at page 3, line 38
four or three nines availability. For the route computation, both four or three nines availability. For the route computation, both
the availability information and the bandwidth resource information the availability information and the bandwidth resource information
are needed. Since different service types may need different are needed. Since different service types may need different
availability guarantees, multiple <availability, bandwidth> pairs availability guarantees, multiple <availability, bandwidth> pairs
may be required to be associated with a link. may be required to be associated with a link.
In this document, a new type of the Generalized SCSI TLV, In this document, a new type of the Generalized SCSI TLV,
Availability TLV is defined. It is intended that technology-specific Availability TLV is defined. It is intended that technology-specific
documents will reference this document to describe specific uses. documents will reference this document to describe specific uses.
The signaling extension to support links with discrete bandwidth is The signaling extension to support links with discrete bandwidth is
defined in [ETPAI]. defined in [I-D. ietf-ccamp-rsvp-te-bandwidth-availability].
2. Overview 2. Acronyms
The following acronyms are used in this draft:
GMPLS Generalized Multi-Protocol Label Switching
LSA Link State Advertisement
ISCD Interface Switching Capability Descriptor
LSP Label Switched Path
OSPF Open Shortest Path First
PSN Packet Switched Network
SCSI Switching Capability-specific information
SNR Signal-to-noise Ratio
SONET-SDH Synchronous Optical Network - Synchronous Digital
Hierarchy
SPF Shortest Path First
TE Traffic Engineering
TLV Type Length Value
3. Overview
A node which has link(s) with variable bandwidth attached should A node which has link(s) with variable bandwidth attached should
include < availability, bandwidth> information list in its OSPF include < availability, bandwidth> information list in its OSPF
Traffic Engineering (TE) LSA messages. The list provides the mapping Traffic Engineering (TE) LSA messages. The list provides the mapping
between the link nominal bandwidth and its availability level. This between the link nominal bandwidth and its availability level. This
information is used for path calculation by the node(s). The setup information is used for path calculation by the node(s). The setup
of a Label Switched Path requires this information to be flooded in of a Label Switched Path requires this information to be flooded in
the network and used by the nodes or the PCE for the path the network and used by the nodes or the PCE for the path
computation. In this document, a new type of the Generalized SCSI computation. In this document, a new type of the Generalized SCSI
TLV, Availability TLV is defined. The computed path can then be TLV, Availability TLV is defined. The computed path can then be
provisioned via the signaling protocol [ETPAI]. provisioned via the signaling protocol [I-D. ietf-ccamp-rsvp-te-
bandwidth-availability].
Note, the mechanisms described in this document only distribute Note, the mechanisms described in this document only distribute
availability information. The methods for measuring the information availability information. The methods for measuring the information
or using the information for route computation are outside the scope or using the information for route computation are outside the scope
of this document. of this document.
3. TE Metric Extension to OSPF-TE 4. TE Metric Extension to OSPF-TE
3.1. Availability SCSI-TLV 4.1. Availability SCSI-TLV
The Generalized SCSI is defined in [GSCSI]. The Availability TLV The Generalized SCSI is defined in [I-D. ietf-teas-gmpls-scsi]. The
defined in this document is a new type of Generalized SCSI-TLV. The Availability TLV defined in this document is a new type of
Availability SCSI-TLV can be included for one or more times. The Generalized SCSI-TLV. The Availability SCSI-TLV can be included for
Availability SCSI-TLV has the following format: one or more times. The Availability SCSI-TLV has the following
format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Availability level | | Availability level |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LSP Bandwidth at Availability level n | | LSP Bandwidth at Availability level n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 0x01, 16 bits. Type: 0x0001, 16 bits.
Length: A 16 bits field that expresses the length of the TLV in Length: 2 octets, 16 bits.
bytes.
Availability level: 32 bits Availability level: 32 bits
This field is a 32-bit IEEE floating point number which describes This field is a binary32-format floating point number as defined by
the decimal value of availability guarantee of the switching [IEEE754-2008]. The bytes are transmitted in network order; that is,
capability in the Interface Switching Capability Descriptor (ISCD) the byte containing the sign bit is transmitted first. This field
[RFC4202] object. The value MUST be less than 1. The Availability describes the decimal value of availability guarantee of the
level is usually expressed in the value of switching capability in the Interface Switching Capability
Descriptor (ISCD) [RFC4202] object. The value MUST be less than 1.
The Availability level is usually expressed in the value of
0.99/0.999/0.9999/0.99999. 0.99/0.999/0.9999/0.99999.
LSP Bandwidth at Availability level n: 32 bits LSP Bandwidth at Availability level n: 32 bits
This field is a 32-bit IEEE floating point number which describes This field is a 32-bit IEEE floating point number which describes
the LSP Bandwidth for the Availability level represented in the the LSP Bandwidth for the Availability level represented in the
Availability field. The units are bytes per second. Availability field. The units are bytes per second.
3.2. Processing Procedures 4.2. Processing Procedures
A node advertising an interface with a Switching Capability which The ISCD allows routing protocols such as OSPF to carry technology
supports variable bandwidth attached SHOULD contain one or more specific information in the Switching Capability-specific
Availability SCSI-TLVs in its OSPF TE LSA messages. Each information (SCSI) field, see [RFC4203]. A node advertising an
Availability SCSI-TLV provides the information about how much interface with a Switching Capability which supports variable
bandwidth a link can support for a specified availability. This bandwidth attached SHOULD contain one or more Availability SCSI-TLVs
information MAY be used for path calculation by the node(s). in its OSPF TE LSA messages. Each Availability SCSI-TLV provides the
information about how much bandwidth a link can support for a
specified availability. This information may be used for path
calculation by the node(s).
The Availability SCSI-TLV MUST NOT be sent in ISCDs with Switching The Availability SCSI-TLV MUST NOT be sent in ISCDs with Switching
Capability field values that have not been defined to support the Capability field values that have not been defined to support the
Availability SCSI-TLV. Non-supporting nodes would see such as a Availability SCSI-TLV. Non-supporting nodes would see such as a
malformed ISCD/LSA. malformed ISCD/LSA.
Absence of the Availability SCSI-TLV in an ISCD containing Switching Absence of the Availability SCSI-TLV in an ISCD containing Switching
Capability field values that have been defined to support the Capability field values that have been defined to support the
Availability SCSI-TLV, SHALL be interpreted as representing fixed- Availability SCSI-TLV, SHALL be interpreted as representing fixed-
bandwidth link with the highest availability value. bandwidth link with the highest availability value.
Only one Availability SCSI-TLV for the specific availability level Only one Availability SCSI-TLV for the specific availability level
SHOULD be sent. If multiple are present, only the first Availability SHOULD be sent. If multiple are present, the Availability SCSI-TLV
SCSI-TLV for an availability level carried in the same ISCD SHALL be with the lowest bandwidth value SHALL be processed. If an
processed. Availability SCSI-TLV with an invalid value (e.g., large than 1) is
received, the Availability SCSI-TLV will be ignored.
4. Security Considerations 5. Security Considerations
This document does not introduce security issues beyond those This document does not introduce security issues beyond those
discussed in [RFC4203]. As with [RFC4203], it specifies the content discussed in [RFC4203]. As with [RFC4203], it specifies the content
of an Opaque LSAs in OSPFv2. As Opaque LSAs are not used for of an Opaque LSAs in OSPFv2. As Opaque LSAs are not used for
Shortest Path First (SPF) computation or normal routing, the Shortest Path First (SPF) computation or normal routing, the
extensions specified here have no direct effect on IP routing. extensions specified here have no direct effect on IP routing.
Tampering with GMPLS TE LSAs may have an impact on the ability to Tampering with GMPLS TE LSAs may have an impact on the ability to
set up connections in the underlying data plane network. As the set up connections in the underlying data plane network. As the
additional availability information may represent information that additional availability information may represent information that
an operator may wish to keep private, consideration should be given an operator may wish to keep private, consideration should be given
skipping to change at page 6, line 35 skipping to change at page 6, line 44
OSPFv2. An analysis of the security of OSPF is provided in OSPFv2. An analysis of the security of OSPF is provided in
[RFC6863] and applies to the extensions to OSPF as described in this [RFC6863] and applies to the extensions to OSPF as described in this
document. Any new mechanisms developed to protect the transmission document. Any new mechanisms developed to protect the transmission
of information carried in Opaque LSAs will also automatically of information carried in Opaque LSAs will also automatically
protect the extensions defined in this document. protect the extensions defined in this document.
Please refer to [RFC5920] for details on security threats; defensive Please refer to [RFC5920] for details on security threats; defensive
techniques; monitoring, detection, and reporting of security techniques; monitoring, detection, and reporting of security
attacks; and requirements. attacks; and requirements.
5. IANA Considerations 6. IANA Considerations
This document introduces a new type for availability of the This document introduces a new type for availability of the
Generalized SCSI-TLV of the TE Link TLV in the TE Opaque LSA for Generalized SCSI-TLV of the TE Link TLV in the TE Opaque LSA for
OSPF v2. Technology-specific documents will reference this document OSPF v2. Technology-specific documents will reference this document
to describe specific use of this Availability SCSI-TLV. to describe specific use of this Availability SCSI-TLV.
IANA has created a registry called the "Generalized SCSI (Switching IANA has created a registry called the "Generalized SCSI (Switching
Capability Specific Information) TLVs Types" registry. The registry Capability Specific Information) TLVs Types" registry. The registry
is needed to be updated to include the Availability SCSI-TLV. This is needed to be updated to include the Availability SCSI-TLV. This
document proposes a suggested value for the Availability SCSI-TLV; document proposes a suggested value for the Availability SCSI-TLV;
it is requested that the suggested value be granted by IANA. it is requested that the suggested value be granted by IANA.
Note (Please REMOVE this note before publication): the registry will
be created by draft-ietf-teas-gmpls-scsi. The requested value should
be added to it when it is created.
Type Description Reference Type Description Reference
--- ------------------ ----------- --- ------------------ -----------
0x01 Availability [This ID] 0x01 Availability [This ID]
The registration procedure for this registry is Standards Action as 7. References
defined in [RFC8126].
6. References
6.1. Normative References 7.1. Normative References
[GSCSI] Ceccarelli, D. and Berger, L., "Generalized Routing [I-D. ietf-teas-gmpls-scsi] Ceccarelli, D. and Berger, L.,
Interface Switching Capability Descriptor Switching "Generalized Routing Interface Switching Capability
Capability Specific Information", Work in Progress, Descriptor Switching Capability Specific Information",
January, 2017. Work in Progress, August, 2017.
[RFC4202] Kompella, K. and Rekhter, Y. (Editors), "Routing [RFC4202] Kompella, K. and Rekhter, Y. (Editors), "Routing
Extensions in Support of Generalized Multi-Protocol Label Extensions in Support of Generalized Multi-Protocol Label
Switching (GMPLS)", RFC 4202, October 2005. Switching (GMPLS)", RFC 4202, October 2005.
[RFC4203] Kompella, K., Ed., and Y. Rekhter, Ed., "OSPF Extensions [RFC4203] Kompella, K., Ed., and Y. Rekhter, Ed., "OSPF Extensions
in Support of Generalized Multi-Protocol Label Switching in Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 4203, October 2005. (GMPLS)", RFC 4203, October 2005.
6.2. Informative References [IEEE754-2008] IEEE standards, "IEEE Standard for Floating-Point
Arithmetic", IEEE Standard 754, August 2008
7.2. Informative 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", RFC 2119, March 1997. Requirement Levels", RFC 2119, March 1997.
[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998.
[RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering
(TE) Extensions to OSPF Version 2", RFC 3630, September (TE) Extensions to OSPF Version 2", RFC 3630, September
2003. 2003.
[RFC8126] Cotton,M. and Leiba,B., and Narten T., "Guidelines for
Writing an IANA Considerations Section in RFCs",
RFC 8126, June 2017.
[RFC5920] Fang, L., "Security Framework for MPLS and GMPLS [RFC5920] Fang, L., "Security Framework for MPLS and GMPLS
Networks", RFC 5920, July 2010. Networks", RFC 5920, July 2010.
[RFC6863] Hartman, S. and D. Zhang, "Analysis of OSPF Security [RFC6863] Hartman, S. and D. Zhang, "Analysis of OSPF Security
According to the Keying and Authentication for Routing According to the Keying and Authentication for Routing
Protocols (KARP) Design Guide", RFC 6863, March 2013. Protocols (KARP) Design Guide", RFC 6863, March 2013.
[G.827] ITU-T Recommendation, "Availability performance parameters [G.827] ITU-T Recommendation, "Availability performance parameters
and objectives for end-to-end international constant bit- and objectives for end-to-end international constant bit-
rate digital paths", September, 2003. rate digital paths", September, 2003.
[F.1703] ITU-R Recommendation, "Availability objectives for real [F.1703] ITU-R Recommendation, "Availability objectives for real
digital fixed wireless links used in 27 500 km digital fixed wireless links used in 27 500 km
hypothetical reference paths and connections", January, hypothetical reference paths and connections", January,
2005. 2005.
[P.530] ITU-R Recommendation," Propagation data and prediction [P.530] ITU-R Recommendation," Propagation data and prediction
methods required for the design of terrestrial line-of- methods required for the design of terrestrial line-of-
sight systems", February, 2012 sight systems", February, 2012
[ETPAI] H., Long, M., Ye, Mirsky, G., Alessandro, A., Shah, H., [I-D. ietf-ccamp-rsvp-te-bandwidth-availability] H., Long, M., Ye,
"Ethernet Traffic Parameters with Availability Mirsky, G., Alessandro, A., Shah, H., "Ethernet Traffic
Information", Work in Progress, August, 2016 Parameters with Availability Information", Work in
Progress, August, 2017
7. Acknowledgments [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", RFC 8174, May 2017.
8. Acknowledgments
The authors would like to thank Acee Lindem, Daniele Ceccarelli, Lou The authors would like to thank Acee Lindem, Daniele Ceccarelli, Lou
Berger for their comments on the document. Berger for their comments on the document.
Authors' Addresses Authors' Addresses
Hao Long Hao Long
Huawei Technologies Co., Ltd. Huawei Technologies Co., Ltd.
No.1899, Xiyuan Avenue, Hi-tech Western District No.1899, Xiyuan Avenue, Hi-tech Western District
Chengdu 611731, P.R.China Chengdu 611731, P.R.China
 End of changes. 28 change blocks. 
91 lines changed or deleted 107 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/