LISP Based FlowMapping for Scaling NFV
draft-barkai-lisp-nfv-10

Document Type Active Internet-Draft (individual)
Last updated 2017-06-08
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
LISP Working Group                                             S. Barkai
Internet-Draft                                Hewlett Packard Enterprise
Intended status: Experimental                               D. Farinacci
Expires: December 10, 2017                                   lispers.net
                                                                D. Meyer
                                                                 Brocade
                                                                F. Maino
                                                              V. Ermagan
                                                      A. Rodriguez-Natal
                                                           Cisco Systems
                                                    A. Cabellos-Aparicio
                                       Technical University of Catalonia
                                                            June 8, 2017

                 LISP Based FlowMapping for Scaling NFV
                        draft-barkai-lisp-nfv-10

Abstract

   This draft describes an RFC 6830 Locator ID Separation Protocol
   (LISP) based distributed flow-mapping-fabric for dynamic scaling of
   virtualized network functions (NFV).  Network functions such as
   subscriber-management, content-optimization, security and quality of
   service, are typically delivered using proprietary hardware
   appliances embedded into the network as turn-key service-nodes or
   service-blades within routers.  Next generation network functions are
   being implemented as pure software instances running on standard
   servers - unbundled virtualized components of capacity and
   functionality.  LISP-SDN based flow-mapping, dynamically assembles
   these components to whole solutions by steering the right traffic in
   the right sequence to the right virtual function instance.

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/.

Barkai, et al.          Expires December 10, 2017               [Page 1]
Internet-Draft                  LISP-NFV                       June 2017

   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 December 10, 2017.

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Connectivity Model  . . . . . . . . . . . . . . . . . . . . .   5
   4.  Flow-Mapping Elements . . . . . . . . . . . . . . . . . . . .   7
   5.  Day-in-life of a Mapped Flow  . . . . . . . . . . . . . . . .   8
     5.1.  XTR Flow Edge . . . . . . . . . . . . . . . . . . . . . .   9
     5.2.  Map Resolvers-Servers . . . . . . . . . . . . . . . . . .  11
     5.3.  XTRs-Mappers Scaling  . . . . . . . . . . . . . . . . . .  11
   6.  Message Formats . . . . . . . . . . . . . . . . . . . . . . .  11
   7.  QOS and Echo Measurements . . . . . . . . . . . . . . . . . .  14
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  14
   11. Normative References  . . . . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  15
Show full document text