draft-ietf-spring-ipv6-use-cases-11.txt   draft-ietf-spring-ipv6-use-cases-12.txt 
Spring J. Brzozowski Spring J. Brzozowski
Internet-Draft J. Leddy Internet-Draft J. Leddy
Intended status: Informational Comcast Intended status: Informational Comcast
Expires: December 15, 2017 C. Filsfils Expires: June 21, 2018 C. Filsfils
R. Maglione, Ed. R. Maglione, Ed.
M. Townsley M. Townsley
Cisco Systems Cisco Systems
June 13, 2017 December 18, 2017
IPv6 SPRING Use Cases IPv6 SPRING Use Cases
draft-ietf-spring-ipv6-use-cases-11 draft-ietf-spring-ipv6-use-cases-12
Abstract Abstract
The Source Packet Routing in Networking (SPRING) architecture The Source Packet Routing in Networking (SPRING) architecture
describes how Segment Routing can be used to steer packets through an describes how Segment Routing can be used to steer packets through an
IPv6 or MPLS network using the source routing paradigm. This IPv6 or MPLS network using the source routing paradigm. This
document illustrates some use cases for Segment Routing in an IPv6 document illustrates some use cases for Segment Routing in an IPv6
only environment. only environment.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 15, 2017. This Internet-Draft will expire on June 21, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. IPv6 SPRING use cases . . . . . . . . . . . . . . . . . . . . 2 2. IPv6 SPRING use cases . . . . . . . . . . . . . . . . . . . . 2
2.1. SPRING in the Home Network . . . . . . . . . . . . . . . 2 2.1. SPRING in the Small Office . . . . . . . . . . . . . . . 2
2.2. SPRING in the Access Network . . . . . . . . . . . . . . 4 2.2. SPRING in the Access Network . . . . . . . . . . . . . . 4
2.3. SPRING in Data Center . . . . . . . . . . . . . . . . . . 4 2.3. SPRING in Data Center . . . . . . . . . . . . . . . . . . 4
2.4. SPRING in Content Delivery Networks . . . . . . . . . . . 5 2.4. SPRING in Content Delivery Networks . . . . . . . . . . . 5
2.5. SPRING in Core networks . . . . . . . . . . . . . . . . . 5 2.5. SPRING in Core networks . . . . . . . . . . . . . . . . . 5
3. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . . 7 6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
7.1. Informative References . . . . . . . . . . . . . . . . . 8 7.1. Informative References . . . . . . . . . . . . . . . . . 8
7.2. Normative References . . . . . . . . . . . . . . . . . . 8 7.2. Normative References . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
Source Packet Routing in Networking (SPRING) architecture leverages Source Packet Routing in Networking (SPRING) architecture leverages
the source routing paradigm. An ingress node steers a packet through the source routing paradigm. An ingress node steers a packet by
a controlled set of instructions, called segments, by prepending the including a controlled set of instructions, called segments, in the
packet with SPRING header. The SPRING architecture is described in SPRING header. The SPRING architecture is described in
[I-D.ietf-spring-segment-routing]. This document illustrates some [I-D.ietf-spring-segment-routing]. This document illustrates some
use cases for SPRING/Segment Routing in an IPv6 only environment. use cases for SPRING/Segment Routing in an IPv6 only environment.
2. IPv6 SPRING use cases 2. IPv6 SPRING use cases
The use cases described in the section do not constitute an The use cases described in the section do not constitute an
exhaustive list of all the possible scenarios: this section only exhaustive list of all the possible scenarios: this section only
includes some of the most common envisioned deployment models for includes some of the most common envisioned deployment models for
IPv6 Segment Routing. IPv6 Segment Routing.
In addition to the use cases described in this document, all the In addition to the use cases described in this document, all the
SPRING use cases [RFC7855] are also applicable to the SRv6 data SPRING use cases [RFC7855] are also applicable to the SRv6 data
plane. plane.
2.1. SPRING in the Home Network 2.1. SPRING in the Small Office
An IPv6-enabled home network provides ample globally routed IP An IPv6-enabled small office (SOHO) provides ample globally routed IP
addresses for all devices in the home. An IPv6 home network with addresses for all devices in the SOHO. An IPv6 small office with
multiple egress points and associated provider-assigned prefixes multiple egress points and associated provider-assigned prefixes
will, in turn, provide multiple IPv6 addresses to hosts. A homenet will, in turn, provide multiple IPv6 addresses to hosts. A small
performing Source and Destination Routing office performing Source and Destination Routing
([I-D.ietf-rtgwg-enterprise-pa-multihoming]) will ensure that packets ([I-D.ietf-rtgwg-enterprise-pa-multihoming]) will ensure that packets
exit the home at the appropriate egress based on the associated exit the SOHO at the appropriate egress based on the associated
delegated prefix for that link. delegated prefix for that link.
A SPRING enabled home provides the ability to steer traffic into a A SPRING enabled SOHO provides the ability to steer traffic into a
specific path from end-hosts in the home, or from a customer edge specific path from end-hosts in the SOHO, or from a customer edge
router in the home. If the selection of the source routed path is router in the SOHO. If the selection of the source routed path is
enabled at the customer edge router, that router is responsible for enabled at the customer edge router, that router is responsible for
classifying traffic and steering it into the correct path. If hosts classifying traffic and steering it into the correct path. If hosts
in the home have explicit source selection rules, classification can in the SOHO have explicit source selection rules, classification can
be based on source address or associated network egress point, be based on source address or associated network egress point,
avoiding the need for DPI-based implicit classification techniques. avoiding the need for DPI-based implicit classification techniques.
If the traffic is steered into a specific path by the host itself, it If the traffic is steered into a specific path by the host itself, it
is important to know which networks can interpret the SPRING header. is important to know which networks can interpret the SPRING header.
This information can be provided as part of host configuration as a This information can be provided as part of host configuration as a
property of the configured IP address. property of the configured IP address.
The ability to steer traffic to an appropriate egress or utilize a The ability to steer traffic to an appropriate egress or utilize a
specific type of media (e.g., low-power, WIFI, wired, femto-cell, specific type of media (e.g., low-power, WIFI, wired, femto-cell,
bluetooth, MOCA, HomePlug, etc.) within the home itself are obvious bluetooth, MOCA, HomePlug, etc.) within the home itself are obvious
cases which may be of interest to an application running within a cases which may be of interest to an application running within a
home network. SOHO.
Steering to a specific egress point may be useful for a number of Steering to a specific egress point may be useful for a number of
reasons, including: reasons, including:
o Regulatory o Regulatory
o Performance of a particular service associated with a particular o Performance of a particular service associated with a particular
link link
o Cost imposed due to data-caps or per-byte charges o Cost imposed due to data-caps or per-byte charges
skipping to change at page 8, line 17 skipping to change at page 8, line 17
7.1. Informative References 7.1. Informative References
[DOCSIS] "DOCSIS Specifications Page", [DOCSIS] "DOCSIS Specifications Page",
<http://www.cablelabs.com/news/ <http://www.cablelabs.com/news/
new-generation-of-docsis-technology/>. new-generation-of-docsis-technology/>.
[I-D.ietf-rtgwg-enterprise-pa-multihoming] [I-D.ietf-rtgwg-enterprise-pa-multihoming]
Baker, F., Bowers, C., and J. Linkova, "Enterprise Baker, F., Bowers, C., and J. Linkova, "Enterprise
Multihoming using Provider-Assigned Addresses without Multihoming using Provider-Assigned Addresses without
Network Prefix Translation: Requirements and Solution", Network Prefix Translation: Requirements and Solution",
draft-ietf-rtgwg-enterprise-pa-multihoming-00 (work in draft-ietf-rtgwg-enterprise-pa-multihoming-02 (work in
progress), March 2017. progress), October 2017.
[I-D.ietf-spring-segment-routing] [I-D.ietf-spring-segment-routing]
Filsfils, C., Previdi, S., Decraene, B., Litkowski, S., Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B.,
and R. Shakir, "Segment Routing Architecture", draft-ietf- Litkowski, S., and R. Shakir, "Segment Routing
spring-segment-routing-11 (work in progress), February Architecture", draft-ietf-spring-segment-routing-13 (work
2017. in progress), October 2017.
[QAM] "QAM specification", <ITU-T Recommendation J.83 Annex B [QAM] "QAM specification", <ITU-T Recommendation J.83 Annex B
(J.83b)>. (J.83b)>.
[RFC5095] Abley, J., Savola, P., and G. Neville-Neil, "Deprecation [RFC5095] Abley, J., Savola, P., and G. Neville-Neil, "Deprecation
of Type 0 Routing Headers in IPv6", RFC 5095, of Type 0 Routing Headers in IPv6", RFC 5095,
DOI 10.17487/RFC5095, December 2007, DOI 10.17487/RFC5095, December 2007,
<http://www.rfc-editor.org/info/rfc5095>. <https://www.rfc-editor.org/info/rfc5095>.
7.2. Normative References 7.2. Normative References
[RFC7855] Previdi, S., Ed., Filsfils, C., Ed., Decraene, B., [RFC7855] Previdi, S., Ed., Filsfils, C., Ed., Decraene, B.,
Litkowski, S., Horneffer, M., and R. Shakir, "Source Litkowski, S., Horneffer, M., and R. Shakir, "Source
Packet Routing in Networking (SPRING) Problem Statement Packet Routing in Networking (SPRING) Problem Statement
and Requirements", RFC 7855, DOI 10.17487/RFC7855, May and Requirements", RFC 7855, DOI 10.17487/RFC7855, May
2016, <http://www.rfc-editor.org/info/rfc7855>. 2016, <https://www.rfc-editor.org/info/rfc7855>.
Authors' Addresses Authors' Addresses
John Brzozowski John Brzozowski
Comcast Comcast
Email: john_brzozowski@cable.comcast.com Email: john_brzozowski@cable.comcast.com
John Leddy John Leddy
Comcast Comcast
 End of changes. 19 change blocks. 
29 lines changed or deleted 29 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/