LISP FlowMapping for NFV draft will be posted as soon as 00 window reopens.
Sorry for missing the deadline. Meanwhile attached. Thanks. Sharon
On Feb 25, 2013, at 17:15, Terry Manderson <[email protected]> wrote:
> All,
>
> I have posted a _DRAFT_ agenda at:
>
> http://www.ietf.org/proceedings/86/agenda/agenda-86-lisp
>
> Please review it and if you see that your requested slot is not there, AND
> you have not received an email from me saying it won't be on the agenda -
> please email me again.
>
> As with the last meeting The Intro and Architecture documents remain a
> gate to any further WG documents being adopted. Please review these
> documents and send comments to the list so that we can have these
> submitted to the IESG.
>
> You should note that the WG Goals and Milestones now feature as a part of
> the Agenda to remind us about the work we have (as a WG) committed to.
>
> Cheers
> Terry
> _______________________________________________
> lisp mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/lisp
>
>
LISP Working Group S. Barkai
Internet-Draft ConteXtream Inc.
Intended status: Experimental D. Farinacci
Expires: August 29, 2013 D. Meyer
F. Maino
V. Ermagan
Cisco Systems
February 25, 2013
LISP Based FlowMapping for Scaling NFV
draft-barkai-lisp-nfv-00
Abstract
This draft describes a flow-mapping method for scaling of virtualized
network functions (NFV) based on RFC 6830 Locator ID Separation
Protocol (LISP). Network functions such as subscriber mobility-
security-quality management are typically delivered using proprietary
appliances topologically embedded into the network. NGN virtualized
network functions run as software instances on standard servers and
are unbundled building blocks of capacity and functionality. LISP
based flow-mapping wires VNF instances and assembles them into the
data-path, resulting in a scalable, dynamically programmable, and
elastic solution based on subscriber-profiles and subscriber-demand
of network functions.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
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 http://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."
Barkai, et al. Expires August 29, 2013 [Page 1]
Internet-Draft LISP Based FlowMapping for Scaling NFV February 2013
This Internet-Draft will expire on August 29, 2013.
Copyright Notice
Copyright (c) 2013 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
(http://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.
Barkai, et al. Expires August 29, 2013 [Page 2]
Internet-Draft LISP Based FlowMapping for Scaling NFV February 2013
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Connectivity Models Used . . . . . . . . . . . . . . . . . . . 4
3. XTR FlowMapping Reference Architecture . . . . . . . . . . . . 7
3.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4. Intra-Provider Mappings . . . . . . . . . . . . . . . . . . . . 8
5. Mapping Subscription . . . . . . . . . . . . . . . . . . . . . 8
6. Inter-Provider Mappings . . . . . . . . . . . . . . . . . . . . 8
7. QOS and Echo Measurements . . . . . . . . . . . . . . . . . . . 8
8. Security Considerations . . . . . . . . . . . . . . . . . . . . 8
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8
11. Normative References . . . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8
Barkai, et al. Expires August 29, 2013 [Page 3]
Internet-Draft LISP Based FlowMapping for Scaling NFV February 2013
1. Introduction
This draft describes a flow-mapping method for scaling virtualized
network functions (NFV) based on the Locator ID Separation Protocol
(LISP).[RFC6830]Network functions such as subscriber mobility-
security-quality.. management are typically delivered using
proprietary appliances topologically embedded into the network as
service nodes or service blades.
This monolithic delivery model increases the complexity of roll-out
and capacity planning, complicates basic connectivity, as well as
limits and inhibits functional choices and service innovation.
Virtualized network functions on the other hand, run as software
instances on standard servers forming unbundled building blocks of
capacity and functionality. This componentized method of function
instantiation presents the network, or rather the virtual network,
with the task of assembling these components into whole solutions by
forwarding the right traffic to the right NFV instance at the right
sequence and the right time.
While it is possible to some extent to use traditional virtual
networking mechanisms such as virtual-LANs (VLAN) and virtual-
private-networks (VPN) for this task, these mechanisms are relatively
static and are bound to the topological network interfaces adding
complex line configuration. Next generation software-defined and
flow-based models on the other hand are much more programmable and
dynamic, and present a better fit to the next generation service-
provider data-center applications. LISP based flow-mapping wires VNF
instances into the data-path in a dynamically programmable and
elastic manner based on subscriber-profiles and subscriber-demand.
2. Connectivity Models Used
LISP implements an identity grid forwarding grid for NFVs. Unlike
topological forwarding which is based on source Subnet - routed hop
by hop to - destination Subnet, NFV grids are based on subscriber
flow-identity "patched" to VNF instance-identity. This is done using
the standard LISP distributed-overlay and network-database
mechanisms. In order to describe how LISP based NFV flow-mapping
works we will refer to 3 connectivity models that are applied
conjointly:
o The topological network or the "location" connectivity is based on
standard bridging and routing enabling both the physical capacity
and physical availability of connectivity. Typically spine-leafs
switching architecture that can cluster hundreds or computer
racks, and core-edge routing architecture inter-connecting these
Barkai, et al. Expires August 29, 2013 [Page 4]
Internet-Draft LISP Based FlowMapping for Scaling NFV February 2013
computer clusters across points of presence, as well as connecting
to the access networks and to the public Internet.
o The functional network or the "identity" grid is there to map
identified subscriber flows carrying an application thread to the
right function task or instance, enabling the logical scalability
and compute concurrency of NFV. This mapping is based on global
definitions of the business service and application, as well
global knowledge of capacity and availability of each functional
task or instance.
o The virtualized network or the location-identity overlay enables
the implementation of the functional network on the physical in-
place bridge-routed network. The network virtualization ring or
overlay is based on the encap/decap functionality of LISP XTR
working in conjunction with the LISP mmap services.
POP3 POP4
\ / \ /
EdgeR -- EdgeRouter
| |
Access ... | Core | ... Internet
| |
EdgeR -- EdgeR
/ \
/ \
^ Spine1 Spine2 ... Spine5
| / \ / \ __/ / .. |
| | \/ | __/ / |
P | /\ || / |
O Leaf1 Leaf2 ... Leaf300
P |-PC1 |-PC1
1 |-PC2 |-PC2
| |.. |..
| |-PC40 |-PC40
v
Topological Location Network
Barkai, et al. Expires August 29, 2013 [Page 5]
Internet-Draft LISP Based FlowMapping for Scaling NFV February 2013
v << FunctionA FunctionB .. FunctionN
v
Recursion Instance1..i Instance1..j Instance1..k
v | | | | | | | | | | | |
v | | | | | | | | | | | |
Subscriber1-o o o o - - -+ o o o - - -o o o o
| | | | | | | | | | | |
Subscriber2-o + o o - - -o o o o - - -o o o o
| | | | | | | | | | | |
. ... ... ...
. ... ... ...
. ... ... ...
| | | | | | | | | | | |
SubscriberM-o o o o - - -o o o o - - -+ o o o
| | | | | | | | | | | |
Functional Identity Grid
AoF AoF AoF Access or Functions AoF AoF AoF
\ | / \ | / \ | /
BoR BoR BoR
| | |
XTR XTR XTR
|| || ||
===============================
|| ||
B _|| ||_ B
o -XTR_ | | _XTR- o
R || Bridges or Routers || R
_|| ||_
B -XTR_ | | _XTR- B
o || || o
R || || R
===============================
|| || ||
XTR XTR XTR
| | |
BoR BoR BoR
/ | \ / | \ / | \
Identity-Location Virtualization Ring
Barkai, et al. Expires August 29, 2013 [Page 6]
Internet-Draft LISP Based FlowMapping for Scaling NFV February 2013
3. XTR FlowMapping Reference Architecture
In order to map subscriber flows to virtualized function instances
and essentially to overlay identity grid onto topology based bridge-
routed network we use the following XTR 3-tier reference
architecture:
1. Flow Switching, or the ability to process consistently and
encapsulate sequences of packets belonging to the same
subscriber-application threads using identity pattern masks.
This tier can be based on, but not limited to ONF OpenFlow
2. Flow Handlers, or the ability to have distinct software for
processing different protocol families and to further provision
flow-switching per specific subscriber-application threads
encapsulated based on application identity elements.
3. Global Mapping, or the ability to associate any globally
significant key to a set of globally assigned values and
attributes. For example mapping a functional VIP to function
instances, or mapping function instances to locations,
accessibility, and load.
Orchestration Authorization OSS/BSS
Mappings Mappings Mappings
v v v
(NFVMs etc.) (3A etc.) (Subs. etc)
v v v
_________________________________
| |
| LISP-MMAP |
|_________________________________|
^ ^ ^
Runtime Mappings(location, affinity, load, etc.)
^ ^ ^
^ ------- ------- -------
| |MMapper| |MMapper| |MMapper|
| |-------| |-------| |-------|
X |H H H H| |H H H H| |H H H H|
T |n n n n| |n n n n| |n n n n|
R |d d d d| |d d d d| |d d d d|
| |l l l l| |l l l l| |l l l l|
| |-------| |-------| |-------|
v | FlowX | | FlowX | | FlowX |
------- ------- -------
Barkai, et al. Expires August 29, 2013 [Page 7]
Internet-Draft LISP Based FlowMapping for Scaling NFV February 2013
FlowMapping XTR Architecture
3.1.
4. Intra-Provider Mappings
5. Mapping Subscription
6. Inter-Provider Mappings
7. QOS and Echo Measurements
8. Security Considerations
There are no security considerations related with this memo.
9. IANA Considerations
There are no IANA considerations related with this memo.
10. Acknowledgements
11. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC6830] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "The
Locator/ID Separation Protocol (LISP)", RFC 6830,
January 2013.
Barkai, et al. Expires August 29, 2013 [Page 8]
Internet-Draft LISP Based FlowMapping for Scaling NFV February 2013
Authors' Addresses
Sharon Barkai
ConteXtream Inc.
California
USA
Email: [email protected]
Dino Farinacci
California
USA
Email: [email protected]
David Meyer
California
USA
Email: [email protected]
Fabio Maino
Cisco Systems
California
USA
Email: [email protected]
Vina Ermagan
Cisco Systems
California
USA
Email: [email protected]
Barkai, et al. Expires August 29, 2013 [Page 9]
_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp
