The IPv6 Compact Routing Header (CRH)
draft-bonica-6man-comp-rtg-hdr-22
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2020-05-14
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
htmlized (tools)
htmlized
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)
|
6man R. Bonica
Internet-Draft Juniper Networks
Intended status: Standards Track Y. Kamite
Expires: November 15, 2020 NTT Communications Corporation
T. Niwa
KDDI
A. Alston
Liquid Telecom
L. Jalil
Verizon
May 14, 2020
The IPv6 Compact Routing Header (CRH)
draft-bonica-6man-comp-rtg-hdr-22
Abstract
This document defines two new Routing header types. Collectively,
they are called the Compact Routing Headers (CRH). Individually,
they are called CRH-16 and CRH-32.
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, 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
Bonica, et al. Expires November 15, 2020 [Page 1]
Internet-Draft IPv6 Compressed Routing Header May 2020
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 Language . . . . . . . . . . . . . . . . . . . . 3
3. The Compressed Routing Headers (CRH) . . . . . . . . . . . . 3
4. The CRH Forwarding Information Base (CRH-FIB) . . . . . . . 5
5. Processing Rules . . . . . . . . . . . . . . . . . . . . . . 5
5.1. Computing Minimum CRH Length . . . . . . . . . . . . . . 6
6. Mutability . . . . . . . . . . . . . . . . . . . . . . . . . 7
7. Applications And SIDs . . . . . . . . . . . . . . . . . . . . 7
8. Management Considerations . . . . . . . . . . . . . . . . . . 8
9. Security Considerations . . . . . . . . . . . . . . . . . . . 8
10. Implementation and Deployment Status . . . . . . . . . . . . 8
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 9
14. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
14.1. Normative References . . . . . . . . . . . . . . . . . . 10
14.2. Informative References . . . . . . . . . . . . . . . . . 10
Appendix A. CRH Processing Examples . . . . . . . . . . . . . . 11
A.1. The SID List Contains One Entry For Each Segment In The
Path . . . . . . . . . . . . . . . . . . . . . . . . . . 12
A.2. The SID List Omits The First Entry In The Path . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
1. Introduction
IPv6 [RFC8200] source nodes use Routing headers to specify the path
that a packet takes to its destination. The IETF has defined several
Routing header types [IANA-RH]. This document defines two new
Routing header types. Collectively, they are called the Compact
Routing Headers (CRH). Individually, they are called CRH-16 and CRH-
32.
The CRH allows IPv6 source nodes to specify the path that a packet
takes to its destination. The CRH:
o Can be encoded in relatively few bytes.
o Is designed to operate within a network domain. (See Section 9).
Bonica, et al. Expires November 15, 2020 [Page 2]
Internet-Draft IPv6 Compressed Routing Header May 2020
Show full document text