LISP L2/L3 EID Mobility Using a Unified Control Plane
draft-ietf-lisp-eid-mobility-02
Network Working Group M. Portoles
Internet-Draft V. Ashtaputre
Intended status: Experimental V. Moreno
Expires: November 15, 2018 F. Maino
Cisco Systems
D. Farinacci
lispers.net
May 14, 2018
LISP L2/L3 EID Mobility Using a Unified Control Plane
draft-ietf-lisp-eid-mobility-02
Abstract
The LISP control plane offers the flexibility to support multiple
overlay flavors simultaneously. This document specifies how LISP can
be used to provide control-plane support to deploy a unified L2 and
L3 overlay solution, as well as analyzing possible deployment options
and models.
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 https://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."
This Internet-Draft will expire on November 15, 2018.
Portoles, et al. Expires November 15, 2018 [Page 1]
Internet-Draft L2/L3 EID Mobility May 2018
Copyright Notice
Copyright (c) 2018 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
(https://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 . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 4
3. Reference System . . . . . . . . . . . . . . . . . . . . . . 4
4. L3 Overlays and Mobility Support . . . . . . . . . . . . . . 5
4.1. Reference Architecture and packet flows . . . . . . . . . 5
4.1.1. Routed Traffic Flow: L3 Overlay use . . . . . . . . . 6
4.1.2. L3 Mobility Flow . . . . . . . . . . . . . . . . . . 6
4.2. Implementation Considerations . . . . . . . . . . . . . . 7
4.2.1. L3 Segmentation . . . . . . . . . . . . . . . . . . . 7
4.2.2. L3 Database-Mappings . . . . . . . . . . . . . . . . 8
4.2.3. LISP Mapping System support . . . . . . . . . . . . . 8
4.2.4. Using SMRs to Track Moved-Away Hosts . . . . . . . . 9
4.2.5. L3 multicast support . . . . . . . . . . . . . . . . 9
4.2.6. Time-to-Live Handling in Data-Plane . . . . . . . . . 9
5. L2 Overlays and Mobility Support . . . . . . . . . . . . . . 9
5.1. Reference Architecture and packet flows . . . . . . . . . 9
5.1.1. Bridged Traffic Flow: L2 Overlay use . . . . . . . . 10
5.1.2. L2 Mobility Flow . . . . . . . . . . . . . . . . . . 11
5.2. Implementation Considerations . . . . . . . . . . . . . . 11
5.2.1. L2 Segmentation . . . . . . . . . . . . . . . . . . . 11
5.2.2. L2 Database-Mappings . . . . . . . . . . . . . . . . 12
5.2.3. Interface to the LISP Mapping System . . . . . . . . 13
5.2.4. SMR support to track L2 hosts that moved away . . . . 13
5.2.5. L2 Broadcast and Multicast traffic . . . . . . . . . 14
5.2.6. L2 Unknown Unicast Support . . . . . . . . . . . . . 14
5.2.7. Time-to-Live Handling in Data-Plane . . . . . . . . . 15
5.3. Support to ARP resolution through Mapping System . . . . 15
5.3.1. Map-Server support to ARP resolution: Packet Flow . . 15
5.3.2. ARP registrations: MAC as a locator record . . . . . 16
5.3.3. Implementation Considerations . . . . . . . . . . . . 18
Show full document text