Use Cases for IPv6 Source Packet Routing in Networking (SPRING)
RFC 8354

Document Type RFC - Informational (March 2018; No errata)
Last updated 2018-03-28
Replaces draft-martin-spring-segment-routing-ipv6-use-cases
Stream IETF
Formats plain text pdf html bibtex
Reviews OPSDIR will not review this version
Stream WG state Submitted to IESG for Publication
Document shepherd Bruno Decraene
Shepherd write-up Show (last changed 2017-04-24)
IESG IESG state RFC 8354 (Informational)
Consensus Boilerplate Yes
Telechat date
Responsible AD Alvaro Retana
Send notices to "Bruno Decraene" <bruno.decraene@orange.com>, aretana.ietf@gmail.com
IANA IANA review state Version Changed - Review Needed
IANA action state No IANA Actions
Internet Engineering Task Force (IETF)                     J. Brzozowski
Request for Comments: 8354                                      J. Leddy
Category: Informational                                          Comcast
ISSN: 2070-1721                                              C. Filsfils
                                                        R. Maglione, Ed.
                                                             M. Townsley
                                                           Cisco Systems
                                                              March 2018

    Use Cases for IPv6 Source Packet Routing in Networking (SPRING)

Abstract

   The Source Packet Routing in Networking (SPRING) architecture
   describes how Segment Routing can be used to steer packets through an
   IPv6 or MPLS network using the source routing paradigm.  This
   document illustrates some use cases for Segment Routing in an
   IPv6-only environment.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are candidates for any level of Internet
   Standard; see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8354.

Brzozowski, et al.            Informational                     [Page 1]
RFC 8354                Use Cases for IPv6 SPRING             March 2018

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.  IPv6 SPRING Use Cases . . . . . . . . . . . . . . . . . . . .   3
     2.1.  SPRING in the Small Office  . . . . . . . . . . . . . . .   3
     2.2.  SPRING in the Access Network  . . . . . . . . . . . . . .   4
     2.3.  SPRING in Data Center . . . . . . . . . . . . . . . . . .   5
     2.4.  SPRING in Content Delivery Networks . . . . . . . . . . .   5
     2.5.  SPRING in Core Networks . . . . . . . . . . . . . . . . .   6
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     5.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     5.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   8
   Contributors  . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

Brzozowski, et al.            Informational                     [Page 2]
RFC 8354                Use Cases for IPv6 SPRING             March 2018

1.  Introduction

   Source Packet Routing in Networking (SPRING) architecture leverages
   the source routing paradigm.  An ingress node steers a packet by
   including a controlled set of instructions, called segments, in the
   SPRING header.  The SPRING architecture is described in
   [SEGMENT-ROUTING].  This document illustrates some use cases for
   SPRING / Segment Routing in an IPv6-only environment.

2.  IPv6 SPRING Use Cases

   The use cases described in this section do not constitute an
   exhaustive list of all the possible scenarios: this section only
   includes some of the most common envisioned deployment models for
   Segment Routing over IPv6 (SRv6).

   In addition to the use cases described in this document, all the
   SPRING use cases [RFC7855] are also applicable to the SRv6 data
   plane.

2.1.  SPRING in the Small Office

   An IPv6-enabled Small Office, Home Office (SOHO) provides ample
   globally routed IP addresses for all devices in the SOHO.  An IPv6
   small office with multiple egress points and associated provider-
   assigned prefixes will, in turn, provide multiple IPv6 addresses to
   hosts.  A small office performing source and destination routing
Show full document text