OSPF-TE Link Availability Extension for Links with Variable Discrete Bandwidth
draft-ietf-ccamp-ospf-availability-extension-08
Network Working Group H. Long, M.Ye
Internet Draft Huawei Technologies Co., Ltd
Intended status: Standards Track G. Mirsky
Individual
A.D'Alessandro
Telecom Italia S.p.A
H. Shah
Ciena
Expires: April 2017 October 24, 2016
OSPF-TE Link Availability Extension for Links with Variable Discrete
Bandwidth
draft-ietf-ccamp-ospf-availability-extension-08.txt
Abstract
A network may contain links with variable discrete bandwidth, e.g.,
copper, radio, etc. The bandwidth of such links may change
discretely in reaction to changing external environment.
Availability is typically used for describing such links during
network planning. This document introduces an optional Interface
Switching Capability Descriptor (ISCD) Availability sub-TLV to
extend the Generalized Multi-Protocol Label Switching (GMPLS) Open
Shortest Path First (OSPF) routing protocol. This extension can be
used for route computation in a network that contains links with
variable discrete bandwidth. Note, this document only covers the
mechanisms by which the availability information is distributed. The
mechanisms by which availability information of a link is determined
and the use of the distributed information for route computation are
outside the scope of this document. It is intended that technology-
specific documents will reference this document to describe specific
uses.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Long, et al. Expires April 24, 2017 [Page 1]
Internet-Draft Availability extension to OSPF-TE October 2016
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
This Internet-Draft will expire on April 24, 2016.
Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License.
Table of Contents
1. Introduction ................................................ 3
2. Overview .................................................... 4
3. Extension to OSPF Routing Protocol........................... 4
3.1. ISCD Availability sub-TLV............................... 4
3.2. Signaling Process....................................... 5
4. Security Considerations...................................... 6
5. IANA Considerations ......................................... 6
6. References .................................................. 7
6.1. Normative References.................................... 7
6.2. Informative References.................................. 7
7. Acknowledgments ............................................. 8
Conventions used in this document
Long, et al. Expires April 24, 2017 [Page 2]
Internet-Draft Availability extension to OSPF-TE October 2016
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119 [RFC2119].
Show full document text