Segment Routing Mapped To IPv6 (SRm6)
draft-bonica-spring-sr-mapped-six-00
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-11-19
|
|
Replaces |
|
draft-bonica-spring-srv6-plus
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
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)
|
SPRING Working Group R. Bonica
Internet-Draft S. Hegde
Intended status: Standards Track Juniper Networks
Expires: May 22, 2020 Y. Kamite
NTT Communications Corporation
A. Alston
D. Henriques
Liquid Telecom
L. Jalil
Verizon
J. Halpern
Ericsson
J. Linkova
Google
G. Chen
Baidu
November 19, 2019
Segment Routing Mapped To IPv6 (SRm6)
draft-bonica-spring-sr-mapped-six-00
Abstract
This document describes Segment Routing mapped to IPv6 (SRm6). SRm6
is a Segment Routing (SR) solution that leverages IPv6. It supports
a wide variety of use-cases while remaining in strict compliance with
IPv6 specifications. SRm6 is optimized for ASIC-based forwarding
devices that operate at high data rates.
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 May 22, 2020.
Bonica, et al. Expires May 22, 2020 [Page 1]
Internet-Draft SRm6 November 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.
Table of Contents
1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4
3. Paths, Segments And Instructions . . . . . . . . . . . . . . 5
4. Segment Types . . . . . . . . . . . . . . . . . . . . . . . . 6
4.1. Adjacency Segments . . . . . . . . . . . . . . . . . . . 6
4.2. Node Segments . . . . . . . . . . . . . . . . . . . . . . 7
4.3. Binding Segments . . . . . . . . . . . . . . . . . . . . 7
5. Segment Identifiers (SID) . . . . . . . . . . . . . . . . . . 8
5.1. Range . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.2. Assigning SIDs to Adjacency Segments . . . . . . . . . . 10
5.3. Assigning SIDs to Node Segments . . . . . . . . . . . . . 11
5.4. Assigning SIDs to Binding Segments . . . . . . . . . . . 11
6. Service Instructions . . . . . . . . . . . . . . . . . . . . 11
6.1. Per-Segment . . . . . . . . . . . . . . . . . . . . . . . 11
6.2. Per-Path . . . . . . . . . . . . . . . . . . . . . . . . 12
7. The IPv6 Data Plane . . . . . . . . . . . . . . . . . . . . . 12
7.1. The Routing Header . . . . . . . . . . . . . . . . . . . 13
7.2. The Destination Options Header . . . . . . . . . . . . . 14
8. Control Plane . . . . . . . . . . . . . . . . . . . . . . . . 15
9. Differences Between SRv6 and SRm6 . . . . . . . . . . . . . . 15
9.1. Routing Header Size . . . . . . . . . . . . . . . . . . . 15
9.2. Decoupling of Topological and Service Instructions . . . 17
9.3. Authentication . . . . . . . . . . . . . . . . . . . . . 17
9.4. Traffic Engineering Capability . . . . . . . . . . . . . 18
Show full document text