LISP Mapping Bulk Retrieval
draft-boucadair-lisp-bulk-06
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-10-09
|
|
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)
|
Network Working Group M. Boucadair
Internet-Draft C. Jacquenet
Intended status: Standards Track Orange
Expires: April 11, 2018 October 8, 2017
LISP Mapping Bulk Retrieval
draft-boucadair-lisp-bulk-06
Abstract
This document extends Locator/ID Separation Protocol (LISP) with a
capability for bulk mapping retrieval. It does so by defining new
LISP messages that are meant to facilitate state recovery of mapping
tables and improve Ingress Tunnel Routers (ITR) recovery times, in
particular. In addition, this document allows to request mappings
that match destination IP prefixes, names, or AS numbers.
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 April 11, 2018.
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
(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
Boucadair & Jacquenet Expires April 11, 2018 [Page 1]
Internet-Draft LISP Map-Bulk October 2017
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. Bulk Mapping Retrieval: Message Formats . . . . . . . . . . . 3
3.1. Map-Bulk-Request Message Format . . . . . . . . . . . . . 3
3.2. Map-Bulk-Response Message Format . . . . . . . . . . . . 5
4. Generating a Map-Bulk-Request Message . . . . . . . . . . . 7
5. Processing a Map-Bulk-Request Message . . . . . . . . . . . . 8
6. Processing a Map-Bulk-Reply Message . . . . . . . . . . . . . 9
7. Bulk Mapping Retrival from Multiple Resolvers . . . . . . . . 10
8. Sample Examples . . . . . . . . . . . . . . . . . . . . . . . 11
9. Security Considerations . . . . . . . . . . . . . . . . . . . 12
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
12.1. Normative references . . . . . . . . . . . . . . . . . . 13
12.2. Informative references . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction
Locator/ID Separation Protocol (LISP, [RFC6830] ) operation relies
upon a mapping mechanism that is used by ingress/egress Tunnel
Routers (xTR) to forward traffic over the LISP network. This
document extends LISP with a capability for bulk mappings retrieval.
It does so by defining new LISP messages that are meant to facilitate
state recovery of mapping tables and improve Ingress Tunnel Routers
(ITR) recovery times, in particular.
The base LISP specification does not define how a requestor may ask
for multiple EIDs. Indeed, the current LISP specification [RFC6830]
states the following:
Support for requesting multiple EIDs in a single Map-Request
message will be specified in a future version of the protocol.
[I-D.boucadair-lisp-multiple-records] defines a backward compatible
extension of the LISP Map-Request message to request multiple
records.
This document defines a more reliable method for the retrieval of
mapping records from one or multiple Map-Resolvers (Section 3). It
does so by using TCP ([RFC0793]) as a transport protocol for
exchanges the bulk retrieval messages. Other proposals have been
Show full document text