< draft-camarilloelmalky-springdmm-srv6-mob-usecases-01.txt   draft-camarilloelmalky-springdmm-srv6-mob-usecases-02.txt >
SPRING and DMM P. Camarillo, Ed. SPRING and DMM P. Camarillo, Ed.
Internet-Draft C. Filsfils Internet-Draft C. Filsfils
Intended status: Standards Track Cisco Systems, Inc. Intended status: Standards Track Cisco Systems, Inc.
Expires: July 19, 2019 H. Elmalky, Ed. Expires: February 16, 2020 H. Elmalky, Ed.
Individual Individual
S. Matsushima S. Matsushima
SoftBank SoftBank
D. Voyer D. Voyer
Bell Canada Bell Canada
A. Cui A. Cui
AT&T AT&T
B. Peirens B. Peirens
Proximus Proximus
January 15, 2019 August 15, 2019
SRv6 Mobility Use-Cases SRv6 Mobility Use-Cases
draft-camarilloelmalky-springdmm-srv6-mob-usecases-01 draft-camarilloelmalky-springdmm-srv6-mob-usecases-02
Abstract Abstract
This document describes the SRv6 use-cases in the mobile network in This document describes the SRv6 use-cases in the mobile network in
association with different mobile generations (3G, 4G, and 5G). It association with different mobile generations (3G, 4G, and 5G). It
also highlights potential interworking with SR-MPLS in relevant use- also highlights potential interworking with SR-MPLS in relevant use-
cases. cases.
Requirements Language Requirements Language
skipping to change at page 1, line 49 skipping to change at page 1, line 49
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 https://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 July 19, 2019. This Internet-Draft will expire on February 16, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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
(https://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
skipping to change at page 3, line 24 skipping to change at page 3, line 24
connectivity (S5-S8/N9 interface). While the tunnels themselves do connectivity (S5-S8/N9 interface). While the tunnels themselves do
not impose significant state beyond that needed, they do have a not impose significant state beyond that needed, they do have a
significant control plane setup component and are a potential target significant control plane setup component and are a potential target
for network delayering. for network delayering.
Segment Routing [I-D.ietf-spring-segment-routing] is a network Segment Routing [I-D.ietf-spring-segment-routing] is a network
architecture that simplifies networks by removing state from the architecture that simplifies networks by removing state from the
network infrastructure, creating a scalable SDN architecture for network infrastructure, creating a scalable SDN architecture for
overlays (VPNs), underlay (SLA, Traffic Engineering, FRR) and service overlays (VPNs), underlay (SLA, Traffic Engineering, FRR) and service
programming (GiLAN). The IPv6 instantiation -also known as SRv6 programming (GiLAN). The IPv6 instantiation -also known as SRv6
[I-D.filsfils-spring-srv6-network-programming]- takes this even [I-D.ietf-spring-srv6-network-programming]- takes this even further
further with the introduction of the Network Programming concept, with the introduction of the Network Programming concept, allowing to
allowing to bind segments to any kind of VNF anywhere in the network bind segments to any kind of VNF anywhere in the network -from
-from private DCs to public cloud services. private DCs to public cloud services.
Segment routing embodies a number of potentially useful properties Segment routing embodies a number of potentially useful properties
for consideration in a 4G/5G mobile networking context: for consideration in a 4G/5G mobile networking context:
1.- Direct manipulation of path routing by the head-end 1.- Direct manipulation of path routing by the head-end
SRv6 provides the ability to direct traffic through an arbitrary path SRv6 provides the ability to direct traffic through an arbitrary path
without the imposition of path state in the network or requiring a without the imposition of path state in the network or requiring a
separate signaling system. It does this without signaling by separate signaling system. It does this without signaling by
encoding the path state in the packet header. This means the path encoding the path state in the packet header. This means the path
skipping to change at page 4, line 37 skipping to change at page 4, line 37
This memo serves to critically explore the applicability of SRv6 to This memo serves to critically explore the applicability of SRv6 to
4G/5G mobile networks. It does that via an exploration of how SRv6 4G/5G mobile networks. It does that via an exploration of how SRv6
can simplify current mobile network architecture to improve the can simplify current mobile network architecture to improve the
status quo of eMBB operation, and then delves into the new use cases status quo of eMBB operation, and then delves into the new use cases
that 5G is targeted towards. that 5G is targeted towards.
2. Terminology 2. Terminology
This document focuses on the use-cases, and it's associated This document focuses on the use-cases, and it's associated
terminologies. The full list of terminologies exists in terminologies. The full list of terminologies exists in
[I-D.filsfils-spring-srv6-network-programming]. [I-D.ietf-spring-srv6-network-programming].
In this document we focus on the 5G systems architecture, as In this document we focus on the 5G systems architecture, as
specified in [TS.23501]. This document also refers to 3G and 4G specified in [TS.23501]. This document also refers to 3G and 4G
networks as specified in [TS.23002]. networks as specified in [TS.23002].
The uplink/upstream traffic is the traffic originated at the UE, The uplink/upstream traffic is the traffic originated at the UE,
while the downlink/downstream traffic is traffic destined towards the while the downlink/downstream traffic is traffic destined towards the
UE. UE.
3. Use-cases 3. Use-cases
skipping to change at page 13, line 5 skipping to change at page 13, line 5
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[TS.23501] [TS.23501]
3GPP, "System Architecture for the 5G System", 3GPP TS 3GPP, "System Architecture for the 5G System", 3GPP TS
23.501 15.2.0, June 2018. 23.501 15.2.0, June 2018.
6.2. Informative References 6.2. Informative References
[I-D.filsfils-spring-srv6-network-programming]
Filsfils, C., Camarillo, P., Leddy, J.,
daniel.voyer@bell.ca, d., Matsushima, S., and Z. Li, "SRv6
Network Programming", draft-filsfils-spring-srv6-network-
programming-06 (work in progress), October 2018.
[I-D.ietf-spring-segment-routing] [I-D.ietf-spring-segment-routing]
Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B., Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B.,
Litkowski, S., and R. Shakir, "Segment Routing Litkowski, S., and R. Shakir, "Segment Routing
Architecture", draft-ietf-spring-segment-routing-15 (work Architecture", draft-ietf-spring-segment-routing-15 (work
in progress), January 2018. in progress), January 2018.
[I-D.ietf-spring-srv6-network-programming]
Filsfils, C., Camarillo, P., Leddy, J.,
daniel.voyer@bell.ca, d., Matsushima, S., and Z. Li, "SRv6
Network Programming", draft-ietf-spring-srv6-network-
programming-01 (work in progress), July 2019.
[I-D.xuclad-spring-sr-service-programming] [I-D.xuclad-spring-sr-service-programming]
Clad, F., Xu, X., Filsfils, C., daniel.bernier@bell.ca, Clad, F., Xu, X., Filsfils, C., daniel.bernier@bell.ca,
d., Li, C., Decraene, B., Ma, S., Yadlapalli, C., d., Li, C., Decraene, B., Ma, S., Yadlapalli, C.,
Henderickx, W., and S. Salsano, "Service Programming with Henderickx, W., and S. Salsano, "Service Programming with
Segment Routing", draft-xuclad-spring-sr-service- Segment Routing", draft-xuclad-spring-sr-service-
programming-01 (work in progress), October 2018. programming-02 (work in progress), April 2019.
[TS.23002] [TS.23002]
3GPP, "Network Architecture", 3GPP TS 23.23002 15.0.0, 3GPP, "Network Architecture", 3GPP TS 23.23002 15.0.0,
March 2018. March 2018.
Authors' Addresses Authors' Addresses
Pablo Camarillo Garvia (editor) Pablo Camarillo Garvia (editor)
Cisco Systems, Inc. Cisco Systems, Inc.
Spain Spain
 End of changes. 9 change blocks. 
16 lines changed or deleted 16 lines changed or added

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