IS-IS Extensions To Support The IPv6 Compressed Routing Header (CRH)
draft-bonica-lsr-crh-isis-extensions-00
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-05-14
|
|
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)
|
LSR Working Group P. Kaneriya
Internet-Draft R. Shetty
Intended status: Standards Track S. Hegde
Expires: November 15, 2019 R. Bonica
Juniper Networks
May 14, 2019
IS-IS Extensions To Support The IPv6 Compressed Routing Header (CRH)
draft-bonica-lsr-crh-isis-extensions-00
Abstract
Source nodes can use the IPv6 Compressed Routing Header (CRH) to
steer packets through a specified path. This document defines IS-IS
extensions that support the CRH.
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/.
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 November 15, 2019.
Copyright Notice
Copyright (c) 2019 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.
Kaneriya, et al. Expires November 15, 2019 [Page 1]
Internet-Draft ISIS-CRH May 2019
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 2
3. Advertising The CRH Capability . . . . . . . . . . . . . . . 2
4. Advertising Supported Algorithms . . . . . . . . . . . . . . 3
5. Advertising Loosely Routed Segment Identifiers . . . . . . . 3
6. Advertising Strictly Routed Segment Identifiers . . . . . . . 4
7. Advertising Strictly Routed Segment Identifiers Into LANs . . 6
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
8.1. The CRH Sub-TLV . . . . . . . . . . . . . . . . . . . . . 8
8.2. Loosely Routed SID Sub-TLV . . . . . . . . . . . . . . . 8
8.3. Strictly Routed SID Sub-TLV . . . . . . . . . . . . . . . 9
9. Security Considerations . . . . . . . . . . . . . . . . . . . 10
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
11.1. Normative References . . . . . . . . . . . . . . . . . . 10
11.2. Informative References . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction
Source nodes can use the IPv6 Compressed Routing Header (CRH)
[I-D.bonica-6man-comp-rtg-hdr] to steer packets through a specified
path. This document defines IS-IS extensions that support the CRH.
2. 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.
3. Advertising The CRH Capability
The Router CAPABILITY TLV [RFC7981] MAY contain exactly one CRH sub-
TLV. The CRH sub-TLV indicates that the advertising node can process
the CRH.
The CRH sub-TLV MAY contain sub-sub-TLVs. No sub-sub-TLVs are
currently defined.
Kaneriya, et al. Expires November 15, 2019 [Page 2]
Internet-Draft ISIS-CRH May 2019
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Max CRH Len | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: CRH Sub-TLV
Figure 1 depicts the CRH sub-TLV. The CRH sub-TLV contains the
Show full document text