Application Specific Attributes Advertisement with BGP Link-State
draft-ietf-idr-bgp-ls-app-specific-attr-01
Inter-Domain Routing K. Talaulikar
Internet-Draft P. Psenak
Intended status: Standards Track Cisco Systems
Expires: May 19, 2020 J. Tantsura
Apstra
November 16, 2019
Application Specific Attributes Advertisement with BGP Link-State
draft-ietf-idr-bgp-ls-app-specific-attr-01
Abstract
Various link attributes have been defined in link-state routing
protocols like OSPF and IS-IS in the context of the MPLS Traffic
Engineering (TE) and GMPLS. BGP Link-State (BGP-LS) extensions have
been defined to distribute these attributes along with other topology
information from these link-state routing protocols. Many of these
link attributes can be used for applications other than MPLS TE or
GMPLS.
Extensions to link-state routing protocols have been defined for such
link attributes which enable distribution of their application
specific values. This document defines extensions to BGP-LS address-
family to enable advertisement of these application specific
attributes as a part of the topology information from the network.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
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). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
Talaulikar, et al. Expires May 19, 2020 [Page 1]
Internet-Draft BGP-LS Extns for App Specific Attributes November 2019
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 19, 2020.
Copyright Notice
Copyright (c) 2019 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
(https://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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Application Specific Link Attributes TLV . . . . . . . . . . 3
3. Application Specific Link Attributes . . . . . . . . . . . . 5
4. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . 7
5. Deployment Considerations . . . . . . . . . . . . . . . . . . 9
6. Backward Compatibility . . . . . . . . . . . . . . . . . . . 9
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
8. Manageability Considerations . . . . . . . . . . . . . . . . 10
8.1. Operational Considerations . . . . . . . . . . . . . . . 10
8.2. Management Considerations . . . . . . . . . . . . . . . . 10
9. Security Considerations . . . . . . . . . . . . . . . . . . . 10
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
11.1. Normative References . . . . . . . . . . . . . . . . . . 11
11.2. Informative References . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction
Various link attributes have been defined in link-state routing
protocols (viz. IS-IS [RFC1195], OSPFv2 [RFC2328] and OSPFv3
[RFC5340] ) in the context of the MPLS traffic engineering and GMPLS.
All these attributes are distributed by these protocols using TLVs
that were originally defined for traditional MPLS Traffic Engineering
(i.e. using RSVP-TE [RFC3209]) or GMPLS [RFC4202] applications.
Talaulikar, et al. Expires May 19, 2020 [Page 2]
Internet-Draft BGP-LS Extns for App Specific Attributes November 2019
Show full document text