Advertising Tunnelling Capability in IS-IS
draft-ietf-isis-encapsulation-cap-01
ISIS Working Group X. Xu, Ed.
Internet-Draft Huawei
Intended status: Standards Track B. Decraene, Ed.
Expires: October 23, 2017 Orange
R. Raszuk
Bloomberg LP
U. Chunduri
Huawei
L. Contreras
Telefonica I+D
L. Jalil
Verizon
April 21, 2017
Advertising Tunnelling Capability in IS-IS
draft-ietf-isis-encapsulation-cap-01
Abstract
Some networks use tunnels for a variety of reasons. A large variety
of tunnel types are defined and the ingress needs to select a type of
tunnel which is supported by the egress. This document defines how
to advertise egress tunnel capabilities in IS-IS Router Capability
TLV.
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 October 23, 2017.
Xu, et al. Expires October 23, 2017 [Page 1]
Internet-Draft April 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. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Advertising Encapsulation Capability . . . . . . . . . . . . 3
4. Tunnel Encapsulation Type . . . . . . . . . . . . . . . . . . 3
5. Tunnel Encapsulation Attribute . . . . . . . . . . . . . . . 5
5.1. Tunnel Parameters sub-TLV . . . . . . . . . . . . . . . . 5
5.2. Encapsulated Protocol sub-TLV . . . . . . . . . . . . . . 6
5.3. End Point sub-TLV . . . . . . . . . . . . . . . . . . . . 6
5.4. Color sub-TLV . . . . . . . . . . . . . . . . . . . . . . 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
6.1. IS-IS Router Capability . . . . . . . . . . . . . . . . . 6
6.2. IGP Tunnel Encapsulation Types Registry . . . . . . . . . 6
6.3. IGP Tunnel Encapsulation Attribute Types Registry . . . . 7
7. Security Considerations . . . . . . . . . . . . . . . . . . . 8
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
9.1. Normative References . . . . . . . . . . . . . . . . . . 8
9.2. Informative References . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction
Some networks use tunnels for a variety of reasons, such as:
o Partial deployment of MPLS-SPRING as described in
Show full document text