MS-originated SMRs
draft-rodrigueznatal-lisp-ms-smr-07
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2018-10-01
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
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 A. Rodriguez-Natal
Internet-Draft Cisco Systems
Intended status: Informational A. Cabellos-Aparicio
Expires: April 4, 2019 Technical University of Catalonia
V. Ermagan
F. Maino
Cisco Systems
S. Barkai
Fermi Serverless
October 1, 2018
MS-originated SMRs
draft-rodrigueznatal-lisp-ms-smr-07
Abstract
This document extends [I-D.ietf-lisp-rfc6833bis] to allow Map Servers
to send SMR messages.
This extension is intended to be used in some SDN deployments that
use LISP as a southbound protocol with (P)ITRs that are compliant
with [I-D.ietf-lisp-rfc6833bis]. In this use-case mapping updates do
not come from ETRs, but rather from a centralized controller that
pushes the updates directly to the Mapping System. In such
deployments, Map Servers will benefit from having a mechanism to
inform directly (P)ITRs about updates in the mappings they are
serving. Although implementations of this extension exist, this
extension is deprecated by [I-D.ietf-lisp-pubsub] and it is being
documented for informational purposes. Newer implementations should
look into [I-D.ietf-lisp-pubsub] to support PubSub in LISP
deployments.
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."
Rodriguez-Natal, et al. Expires April 4, 2019 [Page 1]
Internet-Draft MS-originated SMRs October 2018
This Internet-Draft will expire on April 4, 2019.
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 . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. Map Server extension . . . . . . . . . . . . . . . . . . . . 3
3. Interoperability with legacy (P)ITRs . . . . . . . . . . . . 4
4. Deployment considerations . . . . . . . . . . . . . . . . . . 4
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
7. Security Considerations . . . . . . . . . . . . . . . . . . . 5
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
8.1. Normative References . . . . . . . . . . . . . . . . . . 5
8.2. Informative References . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
The Locator/ID Separation Protocol (LISP) [I-D.ietf-lisp-rfc6833bis]
splits current IP addresses in two different namespaces, Endpoint
Identifiers (EIDs) and Routing Locators (RLOCs). LISP uses a map-
and-encap approach that relies in two entities, the Mapping System
and the Tunnel Routers. The Tunnel Routers are deployed at LISP
sites edge points and perform encapsulation and decapsulation of LISP
data packets. The Mapping System is a distributed database that
stores and disseminates EID-RLOC bindings across different Map-
Servers. LISP Tunnel Routers keep a cache of EID-RLOC mappings
pulled from the Mapping System.
There are several ways to keep this cache updated as described in
[I-D.ietf-lisp-rfc6833bis]. Among them, the Solicit Map-Request
(SMR) message allows to explicitly signal (P)ITRs to let them know
Show full document text