draft-ietf-ccamp-ospf-availability-extension-11.txt   draft-ietf-ccamp-ospf-availability-extension-12.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: April 2018 October 24, 2017 Expires: May 2018 November 10, 2017
OSPF-Traffic Engineering Link Availability Extension for Links with OSPF-Traffic Engineering Link Availability Extension for Links with
Variable Discrete Bandwidth Variable Discrete Bandwidth
draft-ietf-ccamp-ospf-availability-extension-11.txt draft-ietf-ccamp-ospf-availability-extension-12.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 April 24, 2018. This Internet-Draft will expire on April 10, 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
skipping to change at page 2, line 42 skipping to change at page 2, line 42
Table of Contents Table of Contents
1. Introduction ................................................ 3 1. Introduction ................................................ 3
2. Acronyms .................................................... 3 2. Acronyms .................................................... 3
3. Overview .................................................... 4 3. Overview .................................................... 4
4. TE Metric Extension to OSPF-TE............................... 4 4. TE Metric Extension to OSPF-TE............................... 4
4.1. Availability SCSI-TLV................................... 4 4.1. Availability SCSI-TLV................................... 4
4.2. Processing Procedures................................... 5 4.2. Processing Procedures................................... 5
5. Security Considerations...................................... 6 5. Security Considerations...................................... 6
6. IANA Considerations ......................................... 6 6. IANA Considerations ......................................... 7
7. References .................................................. 7 7. References .................................................. 7
7.1. Normative References.................................... 7 7.1. Normative References.................................... 7
7.2. Informative References.................................. 7 7.2. Informative References.................................. 8
8. Acknowledgments ............................................. 8 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", "NOT RECOMMENDED","MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED","MAY", and
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
1. Introduction 1. Introduction
skipping to change at page 5, line 33 skipping to change at page 5, line 33
[IEEE754-2008]. The bytes are transmitted in network order; that is, [IEEE754-2008]. The bytes are transmitted in network order; that is,
the byte containing the sign bit is transmitted first. This field the byte containing the sign bit is transmitted first. This field
describes the decimal value of availability guarantee of the describes the decimal value of availability guarantee of the
switching capability in the Interface Switching Capability switching capability in the Interface Switching Capability
Descriptor (ISCD) [RFC4202] object. The value MUST be less than 1. Descriptor (ISCD) [RFC4202] object. The value MUST be less than 1.
The Availability level is usually expressed in the value of 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 as defined by
the LSP Bandwidth for the Availability level represented in the [IEEE754-2008]. The bytes are transmitted in network order; that is,
Availability field. The units are bytes per second. the byte containing the sign bit is transmitted first. This field
describes the LSP Bandwidth for the Availability level represented
in the Availability field. The units are bytes per second.
4.2. Processing Procedures 4.2. Processing Procedures
The ISCD allows routing protocols such as OSPF to carry technology The ISCD allows routing protocols such as OSPF to carry technology
specific information in the Switching Capability-specific specific information in the Switching Capability-specific
information (SCSI) field, see [RFC4203]. A node advertising an information (SCSI) field, see [RFC4203]. A node advertising an
interface with a Switching Capability which supports variable interface with a Switching Capability which supports variable
bandwidth attached SHOULD contain one or more Availability SCSI-TLVs bandwidth attached SHOULD contain one or more Availability SCSI-TLVs
in its OSPF TE LSA messages. Each Availability SCSI-TLV provides the in its OSPF TE LSA messages. Each Availability SCSI-TLV provides the
information about how much bandwidth a link can support for a information about how much bandwidth a link can support for a
 End of changes. 6 change blocks. 
8 lines changed or deleted 10 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/