IS-IS TE Attributes per application
draft-ginsberg-isis-te-app-00

Document Type Active Internet-Draft (individual)
Last updated 2017-02-27
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Networking Working Group                                     L. Ginsberg
Internet-Draft                                                 P. Psenak
Intended status: Standards Track                              S. Previdi
Expires: August 31, 2017                                   Cisco Systems
                                                           W. Henderickx
                                                                   Nokia
                                                       February 27, 2017

                  IS-IS TE Attributes per application
                   draft-ginsberg-isis-te-app-00.txt

Abstract

   Existing traffic engineering related link attribute advertisements
   have been defined and are used in RSVP-TE deployments.  In cases
   where multiple applications wish to make use of these link attributes
   the current advertisements do not support application specific values
   for a given attribute nor do they support indication of which
   applications are using the advertised value for a given link.

   This draft introduces new link attribute advertisements which address
   both of these shortcomings.  It also discusses backwards
   compatibility issues and how to minimize duplicate advertisements in
   the presence of routers which do not support the extensions defined
   in this document.

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

Ginsberg, et al.         Expires August 31, 2017                [Page 1]
Internet-Draft         draft-ginsberg-isis-te-app          February 2017

   This Internet-Draft will expire on August 31, 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.  Requirements Discussion . . . . . . . . . . . . . . . . . . .   3
   3.  Legacy Advertisements . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Legacy sub-TLVs . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Legacy SRLG Advertisements  . . . . . . . . . . . . . . .   5
   4.  Advertising Application Specific Link Attributes  . . . . . .   5
     4.1.  Application Bit Mask  . . . . . . . . . . . . . . . . . .   6
     4.2.  Application Specific Link Attributes sub-TLV  . . . . . .   6
     4.3.  Application Specific SRLG TLV . . . . . . . . . . . . . .   7
   5.  Interoperability, Backwards Compatibility and Migration
       Concerns  . . . . . . . . . . . . . . . . . . . . . . . . . .   8
     5.1.  RSVP-TE only deployments  . . . . . . . . . . . . . . . .   9
     5.2.  Multiple Applications: Common Attributes with  RSVP-TE  .   9
     5.3.  Multiple Applications: All Attributes Not Shared w RSVP-
           TE  . . . . . . . . . . . . . . . . . . . . . . . . . . .   9
     5.4.  Deprecating legacy advertisements . . . . . . . . . . . .   9
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  11
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  12
Show full document text