IS-IS TE Attributes per application
draft-ietf-isis-te-app-05
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (lsr WG)
|
|
Last updated |
|
2018-10-17
|
|
Replaces |
|
draft-ginsberg-isis-te-app
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
pdf
htmlized (tools)
htmlized
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Networking Working Group L. Ginsberg
Internet-Draft P. Psenak
Intended status: Standards Track Cisco Systems
Expires: April 20, 2019 S. Previdi
Huawei
W. Henderickx
Nokia
J. Drake
Juniper Networks
October 17, 2018
IS-IS TE Attributes per application
draft-ietf-isis-te-app-05.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", "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 April 20, 2019 [Page 1]
Internet-Draft draft-ietf-isis-te-app October 2018
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 April 20, 2019.
Copyright Notice
Copyright (c) 2018 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 . . . . . . . . . . . . . . . . . . . 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 Identifier Bit Mask . . . . . . . . . . . . . 6
4.2. Application Specific Link Attributes sub-TLV . . . . . . 8
4.2.1. Special Considerations for Maximum Link Bandwidth . . 9
4.2.2. Special Considerations for Unreserved Bandwidth . . . 9
4.3. Application Specific SRLG TLV . . . . . . . . . . . . . . 9
5. Deployment Considerations . . . . . . . . . . . . . . . . . . 10
6. Attribute Advertisements and Enablement . . . . . . . . . . . 11
7. Interoperability, Backwards Compatibility and Migration
Concerns . . . . . . . . . . . . . . . . . . . . . . . . . . 12
7.1. RSVP-TE only deployments . . . . . . . . . . . . . . . . 12
7.2. Multiple Applications: Common Attributes with RSVP-TE . 12
7.3. Multiple Applications: All Attributes Not Shared w RSVP-
TE . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
7.4. Deprecating legacy advertisements . . . . . . . . . . . . 13
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
Show full document text