Advertising Node Admin Tags in BGP Link-State Advertisements
draft-ietf-idr-bgp-ls-node-admin-tag-extension-02

Document Type Active Internet-Draft (idr WG)
Last updated 2017-07-25
Replaces draft-psarkar-idr-bgp-ls-node-admin-tag-extension
Stream IETF
Intended RFC status (None)
Formats plain text pdf xml html bibtex
Reviews
Stream WG state In WG Last Call
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Inter-Domain Routing                                      P. Sarkar, Ed.
Internet-Draft                                              Arrcus, Inc.
Intended status: Standards Track                              H. Gredler
Expires: January 26, 2018                                  RtBrick, Inc.
                                                            S. Litkowski
                                                                  Orange
                                                           July 25, 2017

      Advertising Node Admin Tags in BGP Link-State Advertisements
           draft-ietf-idr-bgp-ls-node-admin-tag-extension-02

Abstract

   This document describes the protocol extensions to collect node
   administrative tags adevertised in IGP Link State advertisements and
   disseminate the same in BGP Link-State advertisement protocol, to
   facilitate inter-AS TE applications that may need the same node
   administrative tags to associate a subset of network devices spanning
   across more than one AS with a specific functionality.

Requirements Language

   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].

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 http://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
   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 January 26, 2018.

Sarkar, et al.          Expires January 26, 2018                [Page 1]
Internet-Draft          Node Admin Tags in BGP-LS              July 2017

Copyright Notice

   Copyright (c) 2017 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Per-Node Administrative Tag . . . . . . . . . . . . . . . . .   3
   3.  BGP-LS Extensions for Per-Node Administrative Tags  . . . . .   4
     3.1.  Node Admin Tag TLV  . . . . . . . . . . . . . . . . . . .   5
   4.  Elements of Procedure . . . . . . . . . . . . . . . . . . . .   7
   5.  Applications  . . . . . . . . . . . . . . . . . . . . . . . .   8
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   7.  Manageability Considerations  . . . . . . . . . . . . . . . .   9
     7.1.  Operational Considerations  . . . . . . . . . . . . . . .   9
       7.1.1.  Operations  . . . . . . . . . . . . . . . . . . . . .   9
   8.  TLV/Sub-TLV Code Points Summary . . . . . . . . . . . . . . .   9
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     11.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     11.2.  Informative References . . . . . . . . . . . . . . . . .  10
     11.3.  URIs . . . . . . . . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   Advertising Node Administrative Tags in Link State protocols like IS-
   IS [RFC7917] and OSPF [RFC7777] defines an optional operational
   capability, that allows tagging and grouping of the nodes in a IGP
   domain.  This, among other applications, allows simple management and
   easy control over route and path selection, based on local configured
   policies.  However, node administrative tags advertised in IGP
   advertisements let network operators associate nodes within a single
Show full document text