draft-ietf-ccamp-ospf-availability-extension-05.txt   draft-ietf-ccamp-ospf-availability-extension-06.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
Ericsson Ericsson
A.D'Alessandro A.D'Alessandro
Telecom Italia S.p.A Telecom Italia S.p.A
H. Shah H. Shah
Ciena Ciena
Expires: December 2016 June 3, 2016 Expires: February 2017 August 19, 2016
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-05.txt draft-ietf-ccamp-ospf-availability-extension-06.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 ISCD network planning. This document introduces an optional ISCD
Availability sub-TLV to extend the Open Shortest Path First (OSPF) Availability sub-TLV to extend the Open Shortest Path First (OSPF)
Generalized Multi-Protocol Label Switching (GMPLS) as defined in Generalized Multi-Protocol Label Switching (GMPLS). This extension
[RFC4203]. This extension can be used for route computation in a can be used for route computation in a network that contains links
network that contains links with variable discrete bandwidth. with variable discrete bandwidth.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 42 skipping to change at page 2, line 4
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
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 December 6, 2016. This Internet-Draft will expire on February 19, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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
skipping to change at page 3, line 44 skipping to change at page 3, line 49
voice service usually needs "five nines" availability, while non- voice service usually needs "five nines" availability, while non-
real time services may adequately perform at four or three nines real time services may adequately perform at four or three nines
availability. Since different service types may need different availability. Since different service types may need different
availabilities guarantees, multiple <availability, bandwidth> pairs availabilities guarantees, multiple <availability, bandwidth> pairs
may be required when signaling. The signaling extension for links may be required when signaling. The signaling extension for links
with discrete bandwidth is defined in [ETPAI]. with discrete bandwidth is defined in [ETPAI].
For the route computation, the availability information should be For the route computation, the availability information should be
provided along with bandwidth resource information. In this document, provided along with bandwidth resource information. In this document,
an extension on Interface Switching Capacity Descriptor (ISCD) an extension on Interface Switching Capacity Descriptor (ISCD)
[RFC4202] for availability information is defined. The extension [RFC4202] for availability information is defined.
reuses the reserved field in the ISCD and also introduces an
optional Availability sub-TLV.
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 <bandwidth, availability> information list in its OSPF TE include a <bandwidth, availability> information list in its OSPF TE
LSA messages. The list provides the mapping between the link nominal LSA messages. The list provides the mapping between the link nominal
bandwidth and its availability level. This information is used for bandwidth and its availability level. This information is used for
path calculation by the node(s).The setup of a Label Switched Path path calculation by the node(s).The setup of a Label Switched Path
requires this piece of information to be flooded in the network and requires this piece of information to be flooded in the network and
used by the nodes or the PCE for the path computation. The computed used by the nodes or the PCE for the path computation. The computed
skipping to change at page 4, line 48 skipping to change at page 4, line 48
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: TBA by IANA, suggested value is 0x01, 16 bits; Type: TBA by IANA, suggested value is 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 This field is a 32-bit IEEE floating point number which
describes the decimal value of availability guarantee of the describes the decimal value of availability guarantee of the
switching capacity in the ISCD object which has the AI value switching capability in the ISCD object. The value MUST be
equal to Index of this sub-TLV. The value MUST be less than less than 1. The Availability level is usually expressed in
1. The Availability level is usually expressed in the value the value of 0.99/0.999/0.9999/0.99999.
of 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 This field is a 32-bit IEEE floating point number which
describes the LSP Bandwidth at a certain Availability level describes the LSP Bandwidth at a certain Availability level
which was described in the Availability field. The units are which was described in the Availability field. The units are
bytes per second. bytes per second.
3.2. Processing Procedures 3.2. Processing Procedures
A node which has link(s) with variable bandwidth attached SHOULD A node which has link(s) with variable bandwidth attached SHOULD
contain one or more ISCD Availability sub-TLVs in its OSPF TE LSA contain one or more ISCD Availability sub-TLVs in its OSPF TE LSA
messages. Each ISCD Availability sub-TLV provides the information messages. Each ISCD Availability sub-TLV provides the information
about how much bandwidth a link can support for a specified about how much bandwidth a link can support for a specified
availability. This information SHOULD be used for path calculation availability. This information SHOULD be used for path calculation
by the node(s). by the node(s).
A node that doesn't support ISCD Availability sub-TLV SHOULD ignore A node that doesn't support ISCD Availability sub-TLV SHOULD ignore
ISCD Availability sub-TLV. ISCD Availability sub-TLV. If a node who supports ISCD Availability
sub-TLVs doesn't receive the TLV, it indicates that the link is with
fixed bandwidth, and the availability can be interpreted as the
highest availability value, e.g., five nines. It's legal to send
multiple ISCD Availability sub-TLVs for the same availability level.
4. Security Considerations 4. Security Considerations
This document extends [RFC4203]. As with [RFC4203], it specifies This document extends [RFC4203]. As with [RFC4203], it specifies
the contents of Opaque LSAs in OSPFv2. As Opaque LSAs are not used the contents of Opaque LSAs in OSPFv2. As Opaque LSAs are not used
for Shortest Path First (SPF) computation or normal routing, the for 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 effect on the underlying Tampering with GMPLS TE LSAs may have an effect on the underlying
transport (optical and/or Synchronous Optical Network - Synchronous transport (optical and/or Synchronous Optical Network - Synchronous
Digital Hierarchy (SONET-SDH)) network. [RFC3630] notes that the Digital Hierarchy (SONET-SDH)) network. [RFC3630] notes that the
skipping to change at page 6, line 25 skipping to change at page 6, line 25
TLV; it is recommended that the suggested value be granted by IANA. TLV; it is recommended that the suggested value be granted by IANA.
Type Description Reference Type Description Reference
--- ------------------ ----------- --- ------------------ -----------
0 Reserved [This ID] 0 Reserved [This ID]
0x01 Availability [This ID] 0x01 Availability [This ID]
The registration procedure for this registry is Standards Action as
defined in [RFC5226].
6. References 6. References
6.1. Normative References 6.1. Normative References
[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.
[ETPAI] H., Long, M., Ye, Mirsky, G., Alessandro, A., Shah, H.,
"Ethernet Traffic Parameters with Availability
Information", Work in Progress, June, 2015
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
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 Networks",
RFC 5920, July 2010. 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.,
"Ethernet Traffic Parameters with Availability
Information", Work in Progress, June, 2015
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
Chengdu 611731, P.R.China Chengdu 611731, P.R.China
 End of changes. 13 change blocks. 
19 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/