draft-martin-spring-segment-routing-ipv6-use-cases-00.txt   draft-martin-spring-segment-routing-ipv6-use-cases-01.txt 
Spring J. Brzozowski Spring J. Brzozowski
Internet-Draft J. Leddy Internet-Draft J. Leddy
Intended status: Informational Comcast Intended status: Informational Comcast
Expires: September 7, 2014 I. Leung Expires: October 6, 2014 I. Leung
Rogers Communications Rogers Communications
S. Previdi S. Previdi
M. Townsley M. Townsley
C. Martin C. Martin
C. Filsfils C. Filsfils
R. Maglione R. Maglione, Ed.
Cisco Systems Cisco Systems
March 6, 2014 April 4, 2014
IPv6 Segment Routing Use Cases IPv6 SPRING Use Cases
draft-martin-spring-segment-routing-ipv6-use-cases-00 draft-martin-spring-segment-routing-ipv6-use-cases-01
Abstract Abstract
Segment Routing (SR) leverages the source routing paradigm. A node Source Packet Routing in Networking (SPRING) architecture leverages
steers a packet through a controlled set of instructions, called the source routing paradigm. A node steers a packet through a
segments, by prepending the packet with an SR header. A segment can controlled set of instructions, called segments, by prepending the
represent any instruction, topological or service-based. A segment packet with SPRING header. A segment can represent any instruction,
can have a local semantic to an SR node or global within an SR topological or service-based. A segment can have a local semantic to
domain. SR allows to enforce a flow through any topological path and the SPRING node or global within the SPRING domain. SPRING allows to
service chain while maintaining per-flow state only at the ingress enforce a flow through any topological path and service chain while
node to the SR domain. maintaining per-flow state only at the ingress node to the SPRING
domain.
The objective of this document is to illustrate some use cases that The objective of this document is to illustrate some use cases that
would benefit from an IPv6 Segment Routing data-plane architecture. need to be taken into account by the Source Packet Routing in
Networking (SPRING) architecture.
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 http://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 October 6, 2014.
This Internet-Draft will expire on September 7, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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 (http://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 Segment Routing use cases . . . . . . . . . . . . . . . 3 2. IPv6 SPRING use cases . . . . . . . . . . . . . . . . . . . . 3
2.1. IPv6 Segment Routing in the Home Network . . . . . . . . 4 2.1. SPRING in the Home Network . . . . . . . . . . . . . . . 4
2.2. IPv6 Segment Routing in the Access Network . . . . . . . 5 2.2. SPRING in the Access Network . . . . . . . . . . . . . . 5
2.3. IPv6 Segment Routing in the Data Center . . . . . . . . . 6 2.3. SPRING in the Data Center . . . . . . . . . . . . . . . . 6
2.4. IPv6 Segment Routing in the Content Delivery Networks . . 7 2.4. SPRING in the Content Delivery Networks . . . . . . . . . 6
2.5. IPv6 Segment Routing in the Core networks . . . . . . . . 8 2.5. SPRING in the Core networks . . . . . . . . . . . . . . . 7
3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
5. Security Considerations . . . . . . . . . . . . . . . . . . . 9 5. Security Considerations . . . . . . . . . . . . . . . . . . . 9
6. Informative References . . . . . . . . . . . . . . . . . . . 9 6. Informative References . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
Segment Routing (SR) leverages the source routing paradigm. An Source Packet Routing in Networking (SPRING) architecture leverages
ingress node steers a packet through a controlled set of the source routing paradigm. An ingress node steers a packet through
instructions, called segments, by prepending the packet with an SR a controlled set of instructions, called segments, by prepending the
header. A segment can represent any instruction, topological or packet with SPRING header. A segment can represent any instruction,
service-based. A segment can represent a local semantic on an SR topological or service-based. A segment can represent a local
node, or a global semantic within an SR domain. Segment Routing semantic on the SPRING node, or a global semantic within the SPRING
allows one to enforce a flow through any topological path and service domain. SPRING allows one to enforce a flow through any topological
chain while maintaining per-flow state only at the ingress node to path and service chain while maintaining per-flow state only at the
the Segment Routing domain. ingress node to the SPRING domain.
The Segment Routing architecture is described in The SPRING architecture is described in
[I-D.filsfils-rtgwg-segment-routing]. The Segment Routing control [I-D.filsfils-rtgwg-segment-routing]. The SPRING control plane is
plane is agnostic to the dataplane, thus it can be applied to both agnostic to the dataplane, thus it can be applied to both MPLS and
MPLS and IPv6. In case of MPLS the (list of) segment identifiers are IPv6. In case of MPLS the (list of) segment identifiers are carried
carried in the MPLS label stack, while for the IPv6 dataplane, a new in the MPLS label stack, while for the IPv6 dataplane, a new type of
type of routing extension header is required. routing extension header is required.
The details of the new routing extension header are not in scope of The details of the new routing extension header are described in
this document and will be published on a separate draft which also [I-D.previdi-6man-segment-routing-header] which also covers the
will cover the security considerations and the aspects related to the security considerations and the aspects related to the deprecation of
deprecation of the IPv6 Type 0 Routing Header described in [RFC5095]. the IPv6 Type 0 Routing Header described in [RFC5095].
2. IPv6 Segment Routing use cases 2. IPv6 SPRING use cases
In today's networks, source routing is typically accomplished by In today's networks, source routing is typically accomplished by
encapsulating IP packets in MPLS LSPs that are signaled via RSVP-TE. encapsulating IP packets in MPLS LSPs that are signaled via RSVP-TE.
Therefore, there are scenarios where it may be possible to run IPv6 Therefore, there are scenarios where it may be possible to run IPv6
on top of MPLS, and as such, the MPLS Segment Routing architecture on top of MPLS, and as such, the MPLS Segment Routing architecture
described in [I-D.filsfils-spring-segment-routing-mpls] could be described in [I-D.filsfils-spring-segment-routing-mpls] could be
leveraged to provide Segment Routing capabilities in an IPv6/MPLS leveraged to provide SPRING capabilities in an IPv6/MPLS environment.
environment.
However, there are other cases and/or specific network environments However, there are other cases and/or specific network segments (such
where MPLS may not be available or deployable for lack of support on as for example the Home Network, the Data Center, etc.) where MPLS
network elements or for an operator's design choice. In such may not be available or deployable for lack of support on network
scenarios a non-MPLS based solution would be required. elements or for an operator's design choice. In such scenarios a
non-MPLS based solution would be preferred by the network operators
of such infrastructures.
Specifically, there are a class of use cases that motivate an IPv6 Specifically, there are a class of use cases that motivate an IPv6
data plane. We identify some fundamental scenarios that, when data plane. We identify some fundamental scenarios that, when
recognized in conjunction, strongly indicate an IPv6 data plane: recognized in conjunction, strongly indicate an IPv6 data plane:
1. There is a need or desire to impose source-routing semantics 1. There is a need or desire to impose source-routing semantics
within an application or at the edge of a network (for example, a within an application or at the edge of a network (for example, a
CPE or home gateway) CPE or home gateway)
2. There is a strict lack of an MPLS dataplane 2. There is a strict lack of an MPLS dataplane
skipping to change at page 4, line 8 skipping to change at page 4, line 13
[I-D.ietf-mpls-seamless-mpls] [I-D.ietf-mpls-seamless-mpls]
In any environment with requirements such as those listed above, an In any environment with requirements such as those listed above, an
IPv6 data plane provides a powerful combination of capabilities for a IPv6 data plane provides a powerful combination of capabilities for a
network operator to realize benefits in explicit routing, protection network operator to realize benefits in explicit routing, protection
and restoration, high routing scalability, traffic engineering, and restoration, high routing scalability, traffic engineering,
service chaining, service differentiation and application flexibility service chaining, service differentiation and application flexibility
via programmability. via programmability.
This section will describe some scenarios where MPLS may not be This section will describe some scenarios where MPLS may not be
present and it will highlight how an IPv6 Segment Routing solution present and it will highlight how the SPRING architecture could be
could be used to address such use cases, particularly, when an MPLS used to address such use cases, particularly, when an MPLS data plane
data plane is neither present nor desired. is neither present nor desired.
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 the IPv6 In addition to the use cases described in this document the SPRING
Segment Routing architecture can be applied to all the use cases architecture can be applied to all the use cases described in
described in [I-D.filsfils-rtgwg-segment-routing-use-cases] for the [I-D.filsfils-rtgwg-segment-routing-use-cases] for the SPRING MPLS
Segment Routing MPLS data plane, when an IPv6 data plane is present. data plane, when an IPv6 data plane is present.
2.1. IPv6 Segment Routing in the Home Network 2.1. SPRING in the Home Network
An IPv6-enabled home network provides ample globally routed IP An IPv6-enabled home network provides ample globally routed IP
addresses for all devices in the home. An IPv6 home network with addresses for all devices in the home. An IPv6 home network 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 homenet
performing Source and Destination Routing ([I-D.troan-homenet-sadr]) performing Source and Destination Routing ([I-D.troan-homenet-sadr])
will ensure that packets exit the home at the appropriate egress will ensure that packets exit the home at the appropriate egress
based on the associated delegated prefix for that link. based on the associated delegated prefix for that link.
An IPv6 Segment Routing enabled home provides the possibility for A SPRING enabled home provides the possibility for imposition of a
imposition of a Segment List by end-hosts in the home, or a customer Segment List by end-hosts in the home, or a customer edge router in
edge router in the home. The semantic of the data included in the the home. If the Segment List is enabled at the customer edge
Segment List is translated into an IPv6 address. If the Segment List router, that router is responsible for classifying traffic and
is enabled at the customer edge router, that router is responsible inserting the appropriate Segment List. If hosts in the home have
for classifying traffic and inserting the appropriate Segment List. explicit source selection rules (see
If hosts in the home have explicit source selection rules (see
[I-D.lepape-6man-prefix-metadata]), classification can be based on [I-D.lepape-6man-prefix-metadata]), classification can be based on
source address or associated network egress point, avoiding the need source address or associated network egress point, avoiding the need
for DPI-based implicit classification techniques. If the Segment for DPI-based implicit classification techniques. If the Segment
List is inserted by the host itself, it is important to know which List is inserted by the host itself, it is important to know which
networks can interpret the SR extension header. This information can networks can interpret the SPRING header. This information can be
be provided as part of host configuration as a property of the provided as part of host configuration as a property of the
configured IP address (see [I-D.bhandari-dhc-class-based-prefix]). configured IP address (see [I-D.bhandari-dhc-class-based-prefix]).
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. home network.
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:
skipping to change at page 5, line 33 skipping to change at page 5, line 36
application-support in a data center can utilize the Segment List as application-support in a data center can utilize the Segment List as
a channel to include information that affects its treatment within a channel to include information that affects its treatment within
the data center itself, allowing for application-level steering and the data center itself, allowing for application-level steering and
load-balancing without relying upon implicit application load-balancing without relying upon implicit application
classification techniques at the data-center edge. Further, as more classification techniques at the data-center edge. Further, as more
and more application traffic is encrypted, the ability to extract and more application traffic is encrypted, the ability to extract
(and include in the Segment List) just enough information to enable (and include in the Segment List) just enough information to enable
the network and data center to load-balance and steer traffic the network and data center to load-balance and steer traffic
appropriately becomes more and more important. appropriately becomes more and more important.
2.2. IPv6 Segment Routing in the Access Network 2.2. SPRING in the Access Network
Access networks deliver a variety of types of traffic from the Access networks deliver a variety of types of traffic from the
service provider's network to the home environment and from the home service provider's network to the home environment and from the home
towards the service provider's network. towards the service provider's network.
For bandwidth management or related purposes, the service provider For bandwidth management or related purposes, the service provider
may want to associate certain types of traffic to specific physical may want to associate certain types of traffic to specific physical
or logical downstream capacity pipes. or logical downstream capacity pipes.
This mapping is not the same thing as classification and scheduling. This mapping is not the same thing as classification and scheduling.
skipping to change at page 6, line 10 skipping to change at page 6, line 12
separation allows an operator to differentiate between different separation allows an operator to differentiate between different
types of content and perform a variety of differing functions on types of content and perform a variety of differing functions on
these pipes, such as egress vectoring, byte capping, regulatory these pipes, such as egress vectoring, byte capping, regulatory
compliance functions, and billing. compliance functions, and billing.
In a cable operator's environment, these downstream pipes could be a In a cable operator's environment, these downstream pipes could be a
specific QAM, a DOCSIS service flow or a service group. specific QAM, a DOCSIS service flow or a service group.
Similarly, the operator may want to map traffic from the home sent Similarly, the operator may want to map traffic from the home sent
towards the service provider's network to specific upstream capacity towards the service provider's network to specific upstream capacity
pipes. Information carried in a packet's SR header could provide the pipes. Information carried in a packet's SPRING header could provide
target pipe for this specific packet. The access device would not the target pipe for this specific packet. The access device would
need to know specific details about the packet to perform this not need to know specific details about the packet to perform this
mapping; instead the access device would only need to know how to map mapping; instead the access device would only need to know how to map
the SR SID value to the target pipe. the SR SID value to the target pipe.
2.3. IPv6 Segment Routing in the Data Center 2.3. SPRING in the Data Center
A key use case for SR is to cause a packet to follow a specific path A key use case for SPRING is to cause a packet to follow a specific
through the network. One can think of the service performed at each path through the network. One can think of the service function
SR node to be forwarding. Forwarding is one such service provided by performed at each SPRING node to be forwarding. More complex service
an SR node. More complex services could be applied to the packet by functions could be applied to the packet by a SPRING node including
an SR node including accounting, IDS, load balancing, and fire accounting, IDS, load balancing, and fire walling.
walling. "Service chaining" is the name given to the mechanism where
these more complicated services are executed in a specific order for
a target set of packets. A service provider may choose to have these
services performed external to the routing infrastructure,
specifically on either dedicated physical servers or within VMs
running on a virtualization platform.
To support service chaining, an SR header could then be used to The term "Service Function Chain", as defined in
detail the set of forwarding or services to be applied to the packet [I-D.ietf-sfc-problem-statement], it is used to describe an ordered
by creating an SR header with the desired sequence of service IDs to set of service functions that must be applied to packets.
be applied to the packet.
Note that a service, operating on a physical server or within a VM, A service provider may choose to have these service functions
might not be directly connected to an SR aware router. In fact performed external to the routing infrastructure, specifically on
multiple non-SR aware routers might exist between the service and the either dedicated physical servers or within VMs running on a
nearest SR router. Encoding the SIDs as ipv6 addresses allows virtualization platform.
benefiting from SID SR header compaction.
When a DC offers infrastructure as a service to multiple tenants, [I-D.kumar-sfc-dc-use-cases] describes use cases that demonstrate the
maintaining tenant traffic separation is a key requirement. This can applicability of Service Function Chaining (SFC) within a data center
be supported without requiring the DC to run a flat layer 2 network environment and provides SFC requirements for data center centric use
segmented with VLANs or to build an overlay like solution (e.g. cases.
VXLAN). Instead, multi-tenant separation can be performed using an
SR header where the outer IPv6 DA is the remote hypervisor IP and the
SR header contains an identifier of the virtual interface on that
hypervisor that logically connects to the target remote VM.
2.4. IPv6 Segment Routing in the Content Delivery Networks 2.4. SPRING in the Content Delivery Networks
The rise of online video applications and new, video-capable IP The rise of online video applications and new, video-capable IP
devices has led to an explosion of video traffic traversing network devices has led to an explosion of video traffic traversing network
operator infrastructures. In the drive to reduce the capital and operator infrastructures. In the drive to reduce the capital and
operational impact of the massive influx of online video traffic, as operational impact of the massive influx of online video traffic, as
well as to extend traditional TV services to new devices and screens, well as to extend traditional TV services to new devices and screens,
network operators are increasingly turning to Content Delivery network operators are increasingly turning to Content Delivery
Networks (CDNs). Networks (CDNs).
Several studies showed the benefits of connecting caches in a Several studies showed the benefits of connecting caches in a
skipping to change at page 7, line 51 skipping to change at page 7, line 38
servicing, and correspondingly which service path to follow to apply servicing, and correspondingly which service path to follow to apply
the appropriate service. the appropriate service.
In the above example the service to be performed by the service node In the above example the service to be performed by the service node
was to establish a TCP session to port 80, but in other scenarios was to establish a TCP session to port 80, but in other scenarios
different functions may be required. Another example of action to be different functions may be required. Another example of action to be
taken by the service node is the capability to perform taken by the service node is the capability to perform
transformations on payload data, like real-time video transcode transformations on payload data, like real-time video transcode
option (for rate and/or resolution). option (for rate and/or resolution).
The use of Segment Routing together with the NSH allows building The use of SPRING together with the NSH allows building flexible
flexible service chains where the topological information related to service chains where the topological information related to the path
the path to be followed is carried into the Segment List while the to be followed is carried into the Segment List while the "service
"service plane related information" (function/action to be performed) plane related information" (function/action to be performed) is
is encoded in the metadata, carried into the NSH. The details about encoded in the metadata, carried into the NSH. The details about
using Segment Routing together with NSH will be described in a using SPRING together with NSH will be described in a separate
separate document. document.
2.5. IPv6 Segment Routing in the Core networks 2.5. SPRING in the Core networks
MPLS is a well-known technology widely deployed in many IP core MPLS is a well-known technology widely deployed in many IP core
networks. However there are some operators that do not run MPLS networks. However there are some operators that do not run MPLS
everywhere in their core network today, thus moving forward they everywhere in their core network today, thus moving forward they
would prefer to have an IPv6 native infrastructure for the core would prefer to have an IPv6 native infrastructure for the core
network. network.
While the overall amount of traffic offered to the network continues While the overall amount of traffic offered to the network continues
to grow and considering that multiple types of traffic with different to grow and considering that multiple types of traffic with different
characteristics and requirements are quickly converging over single characteristics and requirements are quickly converging over single
network architecture, the network operators are starting to face new network architecture, the network operators are starting to face new
challenges. challenges.
Many operators are looking at the possibility to setup an explicit Some operators are looking at the possibility to setup an explicit
path based on the IPv6 source address for specific types of traffic path based on the IPv6 source address for specific types of traffic
in order to efficiently use their network infrastructure. In case of in order to efficiently use their network infrastructure. In case of
IPv6 some operators are currently assigning or plan to assign IPv6 IPv6 some operators are currently assigning or plan to assign IPv6
prefix(es) to their IPv6 customers based on regions/geography, thus prefix(es) to their IPv6 customers based on regions/geography, thus
the subscriber's IPv6 prefix could be used to identify the region the subscriber's IPv6 prefix could be used to identify the region
where the customer is located. In such environment the IPv6 source where the customer is located. In such environment the IPv6 source
address could be used by the Edge nodes of the network to steer address could be used by the Edge nodes of the network to steer
traffic and forward it through a specific path other than the optimal traffic and forward it through a specific path other than the optimal
path. path.
skipping to change at page 9, line 17 skipping to change at page 9, line 7
All these scenarios would require a form of traffic engineering All these scenarios would require a form of traffic engineering
capabilities in IP core networks not running MPLS and not willing to capabilities in IP core networks not running MPLS and not willing to
run it. run it.
IPv4 protocol does not provide such functionalities today and it is IPv4 protocol does not provide such functionalities today and it is
not the intent of this document to address the IPv4 scenario, both not the intent of this document to address the IPv4 scenario, both
because this may create a lot of backward compatibility issues with because this may create a lot of backward compatibility issues with
currently deployed networks and for the security issues that may currently deployed networks and for the security issues that may
raise. raise.
The described use cases could be addressed with the SR architecture The described use cases could be addressed with the SPRING
applied to the ipv6 data-plane and by having the Edge nodes of architecture by having the Edge nodes of network to impose a Segment
network to impose a Segment List on specific traffic flows, based on List on specific traffic flows, based on certain classification
certain classification criteria that would include source IPv6 criteria that would include source IPv6 address.
address.
3. Acknowledgements 3. Acknowledgements
The authors would like to thank Brian Field for his valuable comments The authors would like to thank Brian Field, Robert Raszuk, John G.
and inputs to this document. Scudder and Yakov Rekhter for their valuable comments and inputs to
this document.
4. IANA Considerations 4. IANA Considerations
This document does not require any action from IANA. This document does not require any action from IANA.
5. Security Considerations 5. Security Considerations
There are a number of security concerns with source routing at the IP There are a number of security concerns with source routing at the IP
layer [RFC5095]. The new IPv6-based routing header will be defined layer [RFC5095]. The new IPv6-based routing header will be defined
in way that blind attacks are never possible, i.e., attackers will be in way that blind attacks are never possible, i.e., attackers will be
skipping to change at page 10, line 34 skipping to change at page 10, line 26
"Segment Routing with MPLS data plane", draft-filsfils- "Segment Routing with MPLS data plane", draft-filsfils-
spring-segment-routing-mpls-00 (work in progress), October spring-segment-routing-mpls-00 (work in progress), October
2013. 2013.
[I-D.ietf-mpls-seamless-mpls] [I-D.ietf-mpls-seamless-mpls]
Leymann, N., Decraene, B., Filsfils, C., Konstantynowicz, Leymann, N., Decraene, B., Filsfils, C., Konstantynowicz,
M., and D. Steinberg, "Seamless MPLS Architecture", draft- M., and D. Steinberg, "Seamless MPLS Architecture", draft-
ietf-mpls-seamless-mpls-06 (work in progress), February ietf-mpls-seamless-mpls-06 (work in progress), February
2014. 2014.
[I-D.ietf-sfc-problem-statement]
Quinn, P. and T. Nadeau, "Service Function Chaining
Problem Statement", draft-ietf-sfc-problem-statement-03
(work in progress), April 2014.
[I-D.kumar-sfc-dc-use-cases]
Surendra, S., Obediente, C., and M. Tufail, "Service
Function Chaining Use Cases In Data Centers", draft-kumar-
sfc-dc-use-cases-01 (work in progress), March 2014.
[I-D.lepape-6man-prefix-metadata] [I-D.lepape-6man-prefix-metadata]
Pape, M., Systems, C., and I. Farrer, "IPv6 Prefix Meta- Pape, M., Systems, C., and I. Farrer, "IPv6 Prefix Meta-
data and Usage", draft-lepape-6man-prefix-metadata-00 data and Usage", draft-lepape-6man-prefix-metadata-00
(work in progress), July 2013. (work in progress), July 2013.
[I-D.previdi-6man-segment-routing-header]
Previdi, S., Filsfils, C., Field, B., and I. Leung, "IPv6
Segment Routing Header (SRH)", draft-previdi-6man-segment-
routing-header-00 (work in progress), March 2014.
[I-D.quinn-sfc-nsh] [I-D.quinn-sfc-nsh]
Quinn, P., Guichard, J., Fernando, R., Surendra, S., Quinn, P., Guichard, J., Fernando, R., Surendra, S.,
Smith, M., Yadav, N., Agarwal, P., Manur, R., Chauhan, A., Smith, M., Yadav, N., Agarwal, P., Manur, R., Chauhan, A.,
Elzur, U., McConnell, B., and C. Wright, "Network Service Elzur, U., McConnell, B., and C. Wright, "Network Service
Header", draft-quinn-sfc-nsh-02 (work in progress), Header", draft-quinn-sfc-nsh-02 (work in progress),
February 2014. February 2014.
[I-D.troan-homenet-sadr] [I-D.troan-homenet-sadr]
Troan, O. and L. Colitti, "IPv6 Multihoming with Source Troan, O. and L. Colitti, "IPv6 Multihoming with Source
Address Dependent Routing (SADR)", draft-troan-homenet- Address Dependent Routing (SADR)", draft-troan-homenet-
skipping to change at page 11, line 41 skipping to change at page 12, line 4
Via Del Serafico, 200 Via Del Serafico, 200
Rome 00142 Rome 00142
Italy Italy
Email: sprevidi@cisco.com Email: sprevidi@cisco.com
Mark Townsley Mark Townsley
Cisco Systems Cisco Systems
Email: townsley@cisco.com Email: townsley@cisco.com
Christian Martin Christian Martin
Cisco Systems Cisco Systems
Email: martincj@cisco.com Email: martincj@cisco.com
Clarence Filsfils Clarence Filsfils
Cisco Systems Cisco Systems
Brussels Brussels
BE BE
Email: cfilsfil@cisco.com Email: cfilsfil@cisco.com
Roberta Maglione Roberta Maglione (editor)
Cisco Systems Cisco Systems
181 Bay Street 181 Bay Street
Toronto M5J 2T3 Toronto M5J 2T3
Canada Canada
Email: robmgl@cisco.com Email: robmgl@cisco.com
 End of changes. 37 change blocks. 
117 lines changed or deleted 121 lines changed or added

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