IS-IS TE Attributes per application
draft-ietf-isis-te-app-17

The information below is for an old version of the document
Document Type Active Internet-Draft (lsr WG)
Last updated 2020-06-17 (latest revision 2020-06-15)
Replaces draft-ginsberg-isis-te-app
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Acee Lindem
Shepherd write-up Show (last changed 2020-01-10)
IESG IESG state IESG Evaluation::AD Followup
Consensus Boilerplate Yes
Telechat date
Has enough positions to pass.
Responsible AD Alvaro Retana
Send notices to Acee Lindem <acee@cisco.com>, aretana.ietf@gmail.com
IANA IANA review state Version Changed - Review Needed
Networking Working Group                                     L. Ginsberg
Internet-Draft                                                 P. Psenak
Intended status: Standards Track                           Cisco Systems
Expires: December 19, 2020                                    S. Previdi
                                                                  Huawei
                                                           W. Henderickx
                                                                   Nokia
                                                                J. Drake
                                                        Juniper Networks
                                                           June 17, 2020

                  IS-IS TE Attributes per application
                       draft-ietf-isis-te-app-17

Abstract

   Existing traffic engineering related link attribute advertisements
   have been defined and are used in RSVP-TE deployments.  Since the
   original RSVP-TE use case was defined, additional applications (e.g.,
   Segment Routing Policy, Loop Free Alternate) that also make use of
   the link attribute advertisements have been defined . 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
   document introduces new link attribute advertisements that address
   both of these shortcomings.

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

Ginsberg, et al.        Expires December 19, 2020               [Page 1]
Internet-Draft           draft-ietf-isis-te-app                June 2020

   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 December 19, 2020.

Copyright Notice

   Copyright (c) 2020 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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Requirements Discussion . . . . . . . . . . . . . . . . . . .   4
   3.  Legacy Advertisements . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Legacy sub-TLVs . . . . . . . . . . . . . . . . . . . . .   5
     3.2.  Legacy SRLG Advertisements  . . . . . . . . . . . . . . .   6
   4.  Advertising Application Specific Link Attributes  . . . . . .   6
     4.1.  Application Identifier Bit Mask . . . . . . . . . . . . .   6
     4.2.  Application Specific Link Attributes sub-TLV  . . . . . .   9
       4.2.1.  Special Considerations for Maximum Link Bandwidth . .  10
       4.2.2.  Special Considerations for Reservable/Unreserved
               Bandwidth . . . . . . . . . . . . . . . . . . . . . .  10
       4.2.3.  Considerations for Extended TE Metrics  . . . . . . .  11
     4.3.  Application Specific SRLG TLV . . . . . . . . . . . . . .  11
   5.  Attribute Advertisements and Enablement . . . . . . . . . . .  12
   6.  Deployment Considerations . . . . . . . . . . . . . . . . . .  13
     6.1.  Use of Legacy Advertisements  . . . . . . . . . . . . . .  13
     6.2.  Use of Zero Length Application Identifier Bit Masks . . .  14
     6.3.  Interoperability, Backwards Compatibility and Migration
           Concerns  . . . . . . . . . . . . . . . . . . . . . . . .  14
       6.3.1.  Multiple Applications: Common Attributes with  RSVP-
               TE  . . . . . . . . . . . . . . . . . . . . . . . . .  15
Show full document text