Advertising Node Administrative Tags in IS-IS
draft-ietf-isis-node-admin-tag-10

The information below is for an old version of the document
Document Type Active Internet-Draft (isis WG)
Last updated 2016-05-05 (latest revision 2016-05-02)
Replaces draft-psarkar-isis-node-admin-tag
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Christian Hopps
Shepherd write-up Show (last changed 2016-02-24)
IESG IESG state IESG Evaluation::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Needs a YES. Needs 7 more YES or NO OBJECTION positions to pass.
Responsible AD Alia Atlas
Send notices to "Christian Hopps" <chopps@chopps.org>
IANA IANA review state IANA OK - Actions Needed
IS-IS for IP Internets                                    P. Sarkar, Ed.
Internet-Draft                                                H. Gredler
Intended status: Standards Track                  Individual Contributor
Expires: November 4, 2016                                       S. Hegde
                                                  Juniper Networks, Inc.
                                                            S. Litkowski
                                                             B. Decraene
                                                                  Orange
                                                             May 3, 2016

             Advertising Node Administrative Tags in IS-IS
                   draft-ietf-isis-node-admin-tag-10

Abstract

   This document describes an extension to the IS-IS routing protocol to
   add an optional capability that allows tagging and grouping of the
   nodes in an IS-IS domain.  This allows simple management and easy
   control over route and path selection, based on local configured
   policies.  This document describes an extension to the IS-IS protocol
   to advertise node administrative tags.  The node administrative tags
   can be used to express and apply locally defined network policies
   which is a very useful operational capability.  Node administrative
   tags may be used either by IS-IS itself or by other applications
   consuming information propagated via IS-IS.

   This document describes the protocol extensions to disseminate node
   administrative tags in IS-IS protocols.

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

Sarkar, et al.          Expires November 4, 2016                [Page 1]
Internet-Draft          Node Admin Tags in IS-IS                May 2016

   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 November 4, 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Node Administrative Tags  . . . . . . . . . . . . . . . . . .   3
   3.  Node Administrative Tag Sub-TLV . . . . . . . . . . . . . . .   3
     3.1.  TLV format  . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Elements of Procedure . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Interpretation of Node Administrative Tags  . . . . . . .   4
     4.2.  Use of Node Administrative Tags . . . . . . . . . . . . .   5
     4.3.  Processing Node Administrative Tag Changes  . . . . . . .   6
   5.  Applications  . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  Operational Considerations  . . . . . . . . . . . . . . . . .   7
   8.  Manageability Considerations  . . . . . . . . . . . . . . . .   7
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   10. Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   8
   11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   8
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     12.1.  Normative References . . . . . . . . . . . . . . . . . .   8
     12.2.  Informative References . . . . . . . . . . . . . . . . .   9
     12.3.  URIs . . . . . . . . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   It is useful to assign a node administrative tag to a router in the
   IS-IS domain and use it as an attribute associated with the node.
Show full document text