draft-ietf-ccamp-ospf-availability-extension-08.txt   draft-ietf-ccamp-ospf-availability-extension-09.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
Individual Individual
A.D'Alessandro A.D'Alessandro
Telecom Italia S.p.A Telecom Italia S.p.A
H. Shah H. Shah
Ciena Ciena
Expires: April 2017 October 24, 2016 Expires: August 2017 February 15, 2017
OSPF-TE Link Availability Extension for Links with Variable Discrete OSPF-TE Link Availability Extension for Links with Variable Discrete
Bandwidth Bandwidth
draft-ietf-ccamp-ospf-availability-extension-08.txt draft-ietf-ccamp-ospf-availability-extension-09.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 introduces an optional Interface network planning. This document defines a new type of the
Switching Capability Descriptor (ISCD) Availability sub-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
Shortest Path First (OSPF) routing protocol. This extension can be Shortest Path First (OSPF) routing protocol. The extension can be
used for route computation in a network that contains links with used for route computation in a network that contains links with
variable discrete bandwidth. Note, this document only covers the variable discrete bandwidth. Note, this document only covers the
mechanisms by which the availability information is distributed. The mechanisms by which the availability information is distributed. The
mechanisms by which availability information of a link is determined mechanisms by which availability information of a link is determined
and the use of the distributed information for route computation are and the use of the distributed information for route computation are
outside the scope of this document. It is intended that technology- outside the scope of this document. It is intended that technology-
specific documents will reference this document to describe specific specific documents will reference this document to describe specific
uses. uses.
Status of this Memo Status of this Memo
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 April 24, 2016. This Internet-Draft will expire on August 15, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 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. Overview .................................................... 4
3. Extension to OSPF Routing Protocol........................... 4 3. TE Metric Extension to OSPF-TE............................... 4
3.1. ISCD Availability sub-TLV............................... 4 3.1. Availability SCSI-TLV................................... 4
3.2. Signaling Process....................................... 5 3.2. Processing Procedures................................... 5
4. Security Considerations...................................... 6 4. Security Considerations...................................... 6
5. IANA Considerations ......................................... 6 5. IANA Considerations ......................................... 6
6. References .................................................. 7 6. References .................................................. 7
6.1. Normative References.................................... 7 6.1. Normative References.................................... 7
6.2. Informative References.................................. 7 6.2. Informative References.................................. 7
7. Acknowledgments ............................................. 8 7. 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", "MAY", and "OPTIONAL" in this
skipping to change at page 3, line 22 skipping to change at page 3, line 22
LSA Link State Advertisement LSA Link State Advertisement
ISCD Interface Switching Capability Descriptor ISCD Interface Switching Capability Descriptor
LSP Label Switched Path LSP Label Switched Path
OSPF Open Shortest Path First OSPF Open Shortest Path First
PSN Packet Switched Network PSN Packet Switched Network
SCSI Switching Capability-specific information
SNR Signal-to-noise Ratio SNR Signal-to-noise Ratio
SONET-SDH Synchronous Optical Network -- Synchronous Digital SONET-SDH Synchronous Optical Network - Synchronous Digital
Hierarchy Hierarchy
SPF Shortest Path First SPF Shortest Path First
TE Traffic Engineering TE Traffic Engineering
TLV Type Length Value TLV Type Length Value
1. Introduction 1. Introduction
skipping to change at page 4, line 4 skipping to change at page 4, line 6
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
required by the nodes to verify the bandwidth before making a required by the nodes to verify the bandwidth before making a
bandwidth reservation. Assigning different availability classes bandwidth reservation. Assigning different availability classes
over such links provides for a more efficient planning of link over such links provides for a more efficient planning of link
capacity to support different types of services. The link capacity to support different types of services. The link
availability information will be determined by the operator and availability information will be determined by the operator and
statically configured. It will usually be determined from the statically configured. It will usually be determined from the
availability requirements of the services expected to be carried on availability requirements of the services expected to be carried on
the LSP. For example, voice service usually needs ''five nines'' the LSP. For example, voice service usually needs "five nines"
availability, while non-real time services may adequately perform at availability, while non-real time services may adequately perform at
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, an extension on Interface Switching Capability In this document, a new type of the Generalized SCSI TLV,
Descriptor (ISCD) [RFC4202] for availability information is defined. Availability TLV is defined. It is intended that technology-specific
It is intended that technology-specific documents will reference documents will reference this document to describe specific uses.
this document to describe specific uses. The signaling extension to The signaling extension to support links with discrete bandwidth is
support links with discrete bandwidth is defined in [ETPAI]. defined in [ETPAI].
2. Overview 2. Overview
A node which has link(s) with variable bandwidth attached should A node which has link(s) with variable bandwidth attached should
include a< 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 of information is used for path calculation by the node(s). The setup
a Label Switched Path requires this information to be flooded in the of a Label Switched Path requires this information to be flooded in
network and used by the nodes or the PCE for the path computation. the network and used by the nodes or the PCE for the path
In this document, an extension to Interface Switching Capability computation. In this document, a new type of the Generalized SCSI
Descriptor (ISCD) [RFC4202] for availability information is defined. TLV, Availability TLV is defined. The computed path can then be
The computed path can then be provisioned via the signaling protocol provisioned via the signaling protocol [ETPAI].
[ETPAI].
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 3. TE Metric Extension to OSPF-TE
3.1. ISCD Availability sub-TLV 3.1. Availability SCSI-TLV
The ISCD sub-TLV is defined in Section 1.4 of [RFC4203]. The ISCD The Generalized SCSI is defined in [GSCSI]. The Availability TLV
Availability sub-TLV defined in this document is a sub-TLV of ISCD. defined in this document is a new type of Generalized SCSI-TLV. The
The Switching Capability specific information field of ISCD MAY Availability SCSI-TLV can be included for one or more times. The
include one or more ISCD Availability sub-TLV(s). The ISCD Availability SCSI-TLV has the following format:
Availability sub-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: TBA by IANA, suggested value is 0x01, 16 bits. Type: 0x01, 16 bits.
Length: A 16 bits field that expresses the length of the TLV in Length: A 16 bits field that expresses the length of the TLV in
bytes. 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 32-bit IEEE floating point number which describes
the decimal value of availability guarantee of the switching the decimal value of availability guarantee of the switching
capability in the ISCD object. The value MUST be less than 1. The capability in the Interface Switching Capability Descriptor (ISCD)
Availability level is usually expressed in the value of [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 3.2. Processing Procedures
A node advertising an interface with a Switching Capability which A node advertising an interface with a Switching Capability which
supports variable bandwidth attached SHOULD contain one or more ISCD supports variable bandwidth attached SHOULD contain one or more
Availability sub-TLVs in its OSPF TE LSA messages. Each ISCD Availability SCSI-TLVs in its OSPF TE LSA messages. Each
Availability sub-TLV provides the information about how much Availability SCSI-TLV provides the information about how much
bandwidth a link can support for a specified availability. This bandwidth a link can support for a specified availability. This
information MAY be used for path calculation by the node(s). information MAY be used for path calculation by the node(s).
The ISCD Availability sub-TLV MUST NOT be sent in ISCDs with The Availability SCSI-TLV MUST NOT be sent in ISCDs with Switching
Switching Capability field values that have not been defined to Capability field values that have not been defined to support the
support the ISCD Availability sub-TLV. Non-supporting nodes would Availability SCSI-TLV. Non-supporting nodes would see such as a
see such as a malformed ISCD/LSA. malformed ISCD/LSA.
Absence of the ISCD Availability sub-TLV in an ISCD containing Absence of the Availability SCSI-TLV in an ISCD containing Switching
Switching Capability field values that have been defined to support Capability field values that have been defined to support the
the ISCD Availability sub-TLV, SHALL be interpreted as representing Availability SCSI-TLV, SHALL be interpreted as representing fixed-
fixed-bandwidth link with the highest availability value. bandwidth link with the highest availability value.
Only one ISCD Availability sub-TLVs for the specific availability Only one Availability SCSI-TLV for the specific availability level
level SHOULD be sent. If multiple are present, only the first ISCD SHOULD be sent. If multiple are present, only the first Availability
Availability sub-TLV for an availability level carried in the same SCSI-TLV for an availability level carried in the same ISCD SHALL be
ISCD SHALL be processed. processed.
4. Security Considerations 4. 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
to securing this information. [RFC3630] notes that the security to securing this information. [RFC3630] notes that the security
mechanisms described in [RFC2328] apply to Opaque LSAs carried in mechanisms described in [RFC2328] apply to Opaque LSAs carried in
OSPFv2. An analysis of the security of OSPF is provided in [RFC6863] OSPFv2. An analysis of the security of OSPF is provided in
and applies to the extensions to OSPF as described in this document. [RFC6863] and applies to the extensions to OSPF as described in this
Any new mechanisms developed to protect the transmission of document. Any new mechanisms developed to protect the transmission
information carried in Opaque LSAs will also automatically protect of information carried in Opaque LSAs will also automatically
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 attacks; techniques; monitoring, detection, and reporting of security
and requirements. attacks; and requirements.
5. IANA Considerations 5. IANA Considerations
This document introduces an Availability sub-TLV of the ISCD sub-TLV This document introduces a new type for availability of the
of the TE Link TLV in the TE Opaque LSA for OSPF v2. Technology- Generalized SCSI-TLV of the TE Link TLV in the TE Opaque LSA for
specific documents will reference this document to describe specific OSPF v2. Technology-specific documents will reference this document
use of this Availability sub-TLV. IANA is requested to create a new to describe specific use of this Availability SCSI-TLV.
sub-registry, the ''Types for sub-TLV of Interface Switching
Capability Descriptor'' registry under the "Open Shortest Path First
(OSPF) Traffic Engineering TLVs" registry, see
http://www.iana.org/assignments/ospf-traffic-eng-tlvs.
This document proposes a suggested value for the Availability sub- IANA has created a registry called the "Generalized SCSI (Switching
TLV; it is requested that the suggested value be granted by IANA. Capability Specific Information) TLVs Types" registry. The registry
is needed to be updated to include the Availability SCSI-TLV. This
document proposes a suggested value for the Availability SCSI-TLV;
it is requested that the suggested value be granted by IANA.
Type Description Reference Type Description Reference
--- ------------------ ----------- --- ------------------ -----------
0 Reserved [This ID]
0x01 Availability [This ID] 0x01 Availability [This ID]
The registration procedure for this registry is Standards Action as The registration procedure for this registry is Standards Action as
defined in [RFC5226]. defined in [RFC5226].
6. References 6. References
6.1. Normative References 6.1. Normative References
[RFC4202] Kompella, K. and Rekhter, Y. (Editors), ''Routing [GSCSI] Ceccarelli, D. and Berger, L., "Generalized Routing
Interface Switching Capability Descriptor Switching
Capability Specific Information", Work in Progress,
January, 2017.
[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 6.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.
[RFC5226] Narten,T. and H. Alvestrand, ''Guidelines for Writing an [RFC5226] Narten,T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs'', RFC 5226, May 2008. IANA Considerations Section in RFCs", RFC 5226, May 2008.
[RFC5920] Fang, L., "Security Framework for MPLS and GMPLS Networks", [RFC5920] Fang, L., "Security Framework for MPLS and GMPLS
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., [ETPAI] H., Long, M., Ye, Mirsky, G., Alessandro, A., Shah, H.,
''Ethernet Traffic Parameters with Availability "Ethernet Traffic Parameters with Availability
Information'', Work in Progress, June, 2015 Information", Work in Progress, August, 2016
7. Acknowledgments 7. 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
 End of changes. 39 change blocks. 
86 lines changed or deleted 88 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/