IPv6 SPRING Use Cases
draft-ietf-spring-ipv6-use-cases-12

Document Type Active Internet-Draft (spring WG)
Last updated 2017-12-18
Replaces draft-martin-spring-segment-routing-ipv6-use-cases
Stream IETF
Intended RFC status Informational
Formats plain text xml pdf html bibtex
Reviews OPSDIR will not review this version
Stream WG state Submitted to IESG for Publication (wg milestone: Apr 2016 - Requirements for mod... )
Document shepherd Bruno Decraene
Shepherd write-up Show (last changed 2017-04-24)
IESG IESG state RFC Ed Queue
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 IC
RFC Editor RFC Editor state MISSREF
Spring                                                     J. Brzozowski
Internet-Draft                                                  J. Leddy
Intended status: Informational                                   Comcast
Expires: June 21, 2018                                       C. Filsfils
                                                        R. Maglione, Ed.
                                                             M. Townsley
                                                           Cisco Systems
                                                       December 18, 2017

                         IPv6 SPRING Use Cases
                  draft-ietf-spring-ipv6-use-cases-12

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 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 June 21, 2018.

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
   (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

Brzozowski, et al.        Expires June 21, 2018                 [Page 1]
Internet-Draft       IPv6 Segment Routing Use Cases        December 2017

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

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
   [I-D.ietf-spring-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 the 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
   IPv6 Segment Routing.

   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 (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

Brzozowski, et al.        Expires June 21, 2018                 [Page 2]
Internet-Draft       IPv6 Segment Routing Use Cases        December 2017

   will, in turn, provide multiple IPv6 addresses to hosts.  A small
   office performing Source and Destination Routing
Show full document text