| 1 |
<pre>Independent Submission D. Farinacci |
| 2 |
Request for Comments: 8112 lispers.net |
| 3 |
Category: Informational A. Jain |
| 4 |
ISSN: 2070-1721 Juniper Networks |
| 5 |
I. Kouvelas |
| 6 |
Arista |
| 7 |
D. Lewis |
| 8 |
Cisco Systems |
| 9 |
May 2017 |
| 10 |
|
| 11 |
|
| 12 |
<span class="h1">Locator/ID Separation Protocol Delegated Database Tree (LISP-DDT)</span> |
| 13 |
<span class="h1">Referral Internet Groper (RIG)</span> |
| 14 |
|
| 15 |
Abstract |
| 16 |
|
| 17 |
A simple tool called the Locator/ID Separation Protocol Delegated |
| 18 |
Database Tree (LISP-DDT) Referral Internet Groper (RIG), also |
| 19 |
referred to in this document as "rig", can be used to query the LISP- |
| 20 |
DDT hierarchy. This document describes how the "rig" tool works. |
| 21 |
|
| 22 |
Status of This Memo |
| 23 |
|
| 24 |
This document is not an Internet Standards Track specification; it is |
| 25 |
published for informational purposes. |
| 26 |
|
| 27 |
This is a contribution to the RFC Series, independently of any other |
| 28 |
RFC stream. The RFC Editor has chosen to publish this document at |
| 29 |
its discretion and makes no statement about its value for |
| 30 |
implementation or deployment. Documents approved for publication by |
| 31 |
the RFC Editor are not a candidate for any level of Internet |
| 32 |
Standard; see <a href="./rfc7841#section-2">Section 2 of RFC 7841</a>. |
| 33 |
|
| 34 |
Information about the current status of this document, any errata, |
| 35 |
and how to provide feedback on it may be obtained at |
| 36 |
<a href="http://www.rfc-editor.org/info/rfc8112">http://www.rfc-editor.org/info/rfc8112</a>. |
| 37 |
|
| 38 |
Copyright Notice |
| 39 |
|
| 40 |
Copyright (c) 2017 IETF Trust and the persons identified as the |
| 41 |
document authors. All rights reserved. |
| 42 |
|
| 43 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 44 |
Provisions Relating to IETF Documents |
| 45 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 46 |
publication of this document. Please review these documents |
| 47 |
carefully, as they describe your rights and restrictions with respect |
| 48 |
to this document. |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Farinacci, et al. Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc8112">RFC 8112</a> LISP-DDT Referral Internet Groper (RIG) May 2017</span> |
| 55 |
|
| 56 |
|
| 57 |
Table of Contents |
| 58 |
|
| 59 |
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a> |
| 60 |
<a href="#section-2">2</a>. Requirements Language ...........................................<a href="#page-3">3</a> |
| 61 |
<a href="#section-3">3</a>. Definitions of Terms ............................................<a href="#page-3">3</a> |
| 62 |
<a href="#section-4">4</a>. Basic Overview ..................................................<a href="#page-5">5</a> |
| 63 |
<a href="#section-5">5</a>. Implementation Details ..........................................<a href="#page-7">7</a> |
| 64 |
<a href="#section-6">6</a>. Security Considerations .........................................<a href="#page-9">9</a> |
| 65 |
<a href="#section-7">7</a>. IANA Considerations .............................................<a href="#page-9">9</a> |
| 66 |
<a href="#section-8">8</a>. References ......................................................<a href="#page-9">9</a> |
| 67 |
<a href="#section-8.1">8.1</a>. Normative References .......................................<a href="#page-9">9</a> |
| 68 |
<a href="#section-8.2">8.2</a>. Informative References ....................................<a href="#page-10">10</a> |
| 69 |
Acknowledgments ...................................................<a href="#page-11">11</a> |
| 70 |
Authors' Addresses ................................................<a href="#page-11">11</a> |
| 71 |
|
| 72 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 73 |
|
| 74 |
"The Locator/ID Separation Protocol (LISP)" [<a href="./rfc6830" title=""The Locator/ID Separation Protocol (LISP)"">RFC6830</a>] specifies an |
| 75 |
architecture and mechanism for replacing the semantics of an address |
| 76 |
currently used by IP with two separate namespaces: Endpoint |
| 77 |
Identifiers (EIDs), used within sites; and Routing Locators (RLOCs), |
| 78 |
used on the transit networks that make up the Internet |
| 79 |
infrastructure. To achieve this separation, LISP defines protocol |
| 80 |
mechanisms for mapping from EIDs to RLOCs. In addition, LISP assumes |
| 81 |
the existence of a database to store and propagate those mappings |
| 82 |
globally. This document focuses on the LISP Delegated Database Tree |
| 83 |
(LISP-DDT) [<a href="./rfc8111" title=""Locator/ID Separation Protocol Delegated Database Tree (LISP-DDT)"">RFC8111</a>] mapping database system. |
| 84 |
|
| 85 |
The "rig" tool is a manual management tool to query the LISP-DDT |
| 86 |
mapping database hierarchy. It can be run by all devices that |
| 87 |
implement LISP, including Ingress Tunnel Routers (ITRs), Egress |
| 88 |
Tunnel Routers (ETRs), Proxy ITRs (PITRs), Proxy ETRs (PETRs), |
| 89 |
Map-Resolvers, Map-Servers, and LISP-DDT nodes, as well as by a host |
| 90 |
system at either a LISP-capable or non-LISP-capable site. |
| 91 |
|
| 92 |
The LISP-DDT "rig" tool is similar to the "LISP Internet Groper" |
| 93 |
("lig") tool [<a href="./rfc6835" title=""The Locator/ID Separation Protocol Internet Groper (LIG)"">RFC6835</a>] in that they are both diagnostic tools to |
| 94 |
query a database. However, the "rig" tool is used to find |
| 95 |
Map-Servers serving an EID-prefix, specifically within a LISP-DDT |
| 96 |
mapping database framework. And "lig" can be used on top of any |
| 97 |
mapping database system to retrieve locators used for packet |
| 98 |
encapsulation. |
| 99 |
|
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Farinacci, et al. Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc8112">RFC 8112</a> LISP-DDT Referral Internet Groper (RIG) May 2017</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Requirements Language</span> |
| 114 |
|
| 115 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 116 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and |
| 117 |
"OPTIONAL" in this document are to be interpreted as described in |
| 118 |
<a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>] [<a href="./rfc8174" title=""Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"">RFC8174</a>] when, and only when, they appear in all |
| 119 |
capitals, as shown here. |
| 120 |
|
| 121 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Definitions of Terms</span> |
| 122 |
|
| 123 |
Endpoint Identifier (EID): a 32-bit (for IPv4) or 128-bit (for IPv6) |
| 124 |
value (or an address encoded per [<a href="./rfc8060" title=""LISP Canonical Address Format (LCAF)"">RFC8060</a>]) used in the source and |
| 125 |
destination address fields of the first (innermost) LISP header of |
| 126 |
a packet. The host obtains a destination EID the same way it |
| 127 |
obtains a destination address today -- for example, through a |
| 128 |
Domain Name System (DNS) [<a href="./rfc1034" title=""Domain names - concepts and facilities"">RFC1034</a>] lookup or a Session Initiation |
| 129 |
Protocol (SIP) [<a href="./rfc3261" title=""SIP: Session Initiation Protocol"">RFC3261</a>] exchange. The source EID is obtained via |
| 130 |
existing mechanisms used to set a host's "local" IP address. An |
| 131 |
EID used on the public Internet must have the same properties as |
| 132 |
any other IP address used in that manner; this means, among other |
| 133 |
things, that it must be globally unique. An EID is allocated to a |
| 134 |
host from an EID-prefix block associated with the site where the |
| 135 |
host is located. An EID can be used by a host to refer to other |
| 136 |
hosts. EIDs MUST NOT be used as LISP RLOCs. Note that EID blocks |
| 137 |
MAY be assigned in a hierarchical manner, independent of the |
| 138 |
network topology, to facilitate scaling of the mapping database. |
| 139 |
In addition, an EID block assigned to a site may have site-local |
| 140 |
structure (subnetting) for routing within the site; this structure |
| 141 |
is not visible to the global routing system. In theory, the bit |
| 142 |
string that represents an EID for one device can represent an RLOC |
| 143 |
for a different device. As the architecture is realized, if a |
| 144 |
given bit string is both an RLOC and an EID, it must refer to the |
| 145 |
same entity in both cases. When used in "discussions" with other |
| 146 |
Locator/ID separation proposals, a LISP EID will be called an |
| 147 |
"LEID". Throughout this document, any references to "EID" refer |
| 148 |
to an LEID. |
| 149 |
|
| 150 |
Extended EID (XEID): a LISP EID, optionally extended with a non-zero |
| 151 |
Instance ID (IID) if the EID is intended for use in a context |
| 152 |
where it may not be a unique value, such as in a Virtual Private |
| 153 |
Network where private address space [<a href="./rfc1918" title=""Address Allocation for Private Internets"">RFC1918</a>] is used. See |
| 154 |
<a href="./rfc6830#section-5.5">Section 5.5 of [RFC6830]</a> for more discussion of IIDs. |
| 155 |
|
| 156 |
Routing Locator (RLOC): an IPv4 [<a href="./rfc791" title=""Internet Protocol"">RFC791</a>] or IPv6 [<a href="./rfc2460" title=""Internet Protocol, Version 6 (IPv6) Specification"">RFC2460</a>] address |
| 157 |
of an Egress Tunnel Router (ETR). An RLOC is the output of an |
| 158 |
EID-to-RLOC mapping lookup. An EID maps to one or more RLOCs. |
| 159 |
Typically, RLOCs are numbered from topologically aggregatable |
| 160 |
blocks that are assigned to a site at each point to which it |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Farinacci, et al. Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc8112">RFC 8112</a> LISP-DDT Referral Internet Groper (RIG) May 2017</span> |
| 167 |
|
| 168 |
|
| 169 |
attaches to the global Internet; where the topology is defined by |
| 170 |
the connectivity of provider networks, RLOCs can be thought of as |
| 171 |
Provider-Assigned (PA) addresses. Multiple RLOCs can be assigned |
| 172 |
to the same ETR device or to multiple ETR devices at a site. |
| 173 |
|
| 174 |
DDT node: a network infrastructure component responsible for |
| 175 |
specific XEID-prefix(es) and for the delegation of more-specific |
| 176 |
sub-prefixes to other DDT nodes. |
| 177 |
|
| 178 |
DDT client: a network infrastructure component that sends DDT |
| 179 |
Map-Request messages and implements the iterative following of |
| 180 |
Map-Referral results. Typically, a DDT client will be a |
| 181 |
Map-Resolver (as defined by [<a href="./rfc6833" title=""Locator/ID Separation Protocol (LISP) Map-Server Interface"">RFC6833</a>]), but it is also possible |
| 182 |
for an ITR to implement DDT client functionality. A DDT client |
| 183 |
can be a device that is originating "rig" requests. |
| 184 |
|
| 185 |
DDT Map-Server: a DDT node that also implements Map-Server |
| 186 |
functionality (forwarding Map-Requests and/or returning |
| 187 |
Map-Replies if offering a proxy Map-Reply service) for a subset of |
| 188 |
its delegated prefixes. Map-Server functions, including proxying |
| 189 |
Map-Replies, are described in [<a href="./rfc6833" title=""Locator/ID Separation Protocol (LISP) Map-Server Interface"">RFC6833</a>]. |
| 190 |
|
| 191 |
DDT Map-Resolver: a network infrastructure element that accepts a |
| 192 |
Map-Request, adds the XEID to its lookup queue, then queries one |
| 193 |
or more DDT nodes for the requested EID, following returned |
| 194 |
referrals until it receives one with the MS-ACK action code |
| 195 |
[<a href="./rfc8111" title=""Locator/ID Separation Protocol Delegated Database Tree (LISP-DDT)"">RFC8111</a>]. This indicates that the Map-Request has been sent to a |
| 196 |
Map-Server that will forward it to an ETR that, in turn, will |
| 197 |
provide a Map-Reply to the original sender. A DDT Map-Resolver |
| 198 |
maintains both (1) a cache of Map-Referral message results (termed |
| 199 |
the "referral cache") containing RLOCs for DDT nodes responsible |
| 200 |
for XEID-prefixes of interest and (2) a lookup queue of XEIDs that |
| 201 |
are being resolved through iterative querying of DDT nodes. |
| 202 |
|
| 203 |
Encapsulated Map-Request: a LISP Map-Request that is carried within |
| 204 |
an Encapsulated Control Message (ECM) and that has an additional |
| 205 |
LISP header prepended. Sent to UDP destination port 4342. The |
| 206 |
"outer" addresses are globally routable IP addresses, also known |
| 207 |
as RLOCs. Used by an ITR when sending a Map-Request to a |
| 208 |
Map-Resolver and by a Map-Server when forwarding a Map-Request to |
| 209 |
an ETR as documented in [<a href="./rfc6833" title=""Locator/ID Separation Protocol (LISP) Map-Server Interface"">RFC6833</a>]. |
| 210 |
|
| 211 |
Map-Referral: a LISP message sent by a DDT node when it receives a |
| 212 |
DDT Map-Request for an XEID that matches a configured XEID-prefix |
| 213 |
delegation. A non-Negative Map-Referral message includes a |
| 214 |
"referral" -- a set of RLOCs for DDT nodes that have more |
| 215 |
information about the sub-prefix; a DDT client "follows the |
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Farinacci, et al. Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc8112">RFC 8112</a> LISP-DDT Referral Internet Groper (RIG) May 2017</span> |
| 223 |
|
| 224 |
|
| 225 |
referral" by sending another DDT Map-Request to one of those RLOCs |
| 226 |
to obtain either an answer or another referral to DDT nodes |
| 227 |
responsible for a more-specific XEID-prefix. |
| 228 |
|
| 229 |
Authoritative XEID-prefix: an XEID-prefix delegated to a DDT node |
| 230 |
and for which the DDT node may provide further delegations of |
| 231 |
more-specific sub-prefixes. |
| 232 |
|
| 233 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Basic Overview</span> |
| 234 |
|
| 235 |
LISP-DDT [<a href="./rfc8111" title=""Locator/ID Separation Protocol Delegated Database Tree (LISP-DDT)"">RFC8111</a>] is a hierarchical distributed database that |
| 236 |
embodies the delegation of authority to provide mappings from LISP |
| 237 |
EIDs to RLOCs. It is a statically defined distribution of the EID |
| 238 |
namespace among a set of LISP-speaking servers called "DDT nodes". |
| 239 |
Each DDT node is configured as "authoritative" for one or more |
| 240 |
EID-prefixes, along with the set of RLOCs for Map-Servers or "child" |
| 241 |
DDT nodes to which more-specific EID-prefixes are delegated. |
| 242 |
|
| 243 |
Map-Resolvers send Map-Requests to the DDT hierarchy and maintain |
| 244 |
referral caches by receiving Map-Referral messages from DDT nodes. |
| 245 |
Map-Resolvers follow the DDT hierarchy for a given EID lookup based |
| 246 |
on the EID-prefix and delegation referrals contained in the |
| 247 |
Map-Referral messages. The "rig" tool is intended to perform the |
| 248 |
same operation as that of a Map-Resolver but to also be used as a |
| 249 |
management tool for the network administrator. |
| 250 |
|
| 251 |
When the "rig" command is run, an Encapsulated Control Message |
| 252 |
Map-Request is sent for a destination EID. When a LISP-DDT |
| 253 |
Map-Referral is returned, the contents are displayed to the user. |
| 254 |
The information displayed includes: |
| 255 |
|
| 256 |
o A delegated EID-prefix configured in a DDT node or a configured |
| 257 |
site EID-prefix in a DDT Map-Server that matches the |
| 258 |
requested EID. |
| 259 |
|
| 260 |
o The type of DDT node that sent the Map-Referral. |
| 261 |
|
| 262 |
o The action code and TTL set by the sender of the Map-Referral. |
| 263 |
|
| 264 |
o The referral RLOC addresses from the Map-Referral message. |
| 265 |
|
| 266 |
o A round-trip-time estimate for the ECM-Map-Request / Map-Referral |
| 267 |
message exchange. |
| 268 |
|
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Farinacci, et al. Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc8112">RFC 8112</a> LISP-DDT Referral Internet Groper (RIG) May 2017</span> |
| 279 |
|
| 280 |
|
| 281 |
A possible syntax for a "rig" command MAY be: |
| 282 |
|
| 283 |
rig [instance-id <iid>] <eid> to <ddt-node> [follow-all-referrals] |
| 284 |
|
| 285 |
Parameter descriptions: |
| 286 |
|
| 287 |
[instance-id <iid>]: <iid> is the IID portion of the XEID used as a |
| 288 |
VPN identifier or for other future purposes. When the DDT |
| 289 |
hierarchy is not configured with IIDs, this argument is omitted |
| 290 |
from the command line. |
| 291 |
|
| 292 |
<eid>: <eid> is either a Fully Qualified Domain Name or a |
| 293 |
destination EID that is being queried in the LISP-DDT mapping |
| 294 |
database. |
| 295 |
|
| 296 |
<ddt-node>: <ddt-node> is the RLOC address of any DDT node in the |
| 297 |
DDT hierarchy. This can be the DDT root node, a DDT transit node, |
| 298 |
or a DDT Map-Server. |
| 299 |
|
| 300 |
[follow-all-referrals]: When this keyword is used, each referral |
| 301 |
RLOC is queried so "rig" can descend the entire DDT hierarchy |
| 302 |
starting from the node <ddt-node>. When this keyword is not used, |
| 303 |
one of the referral RLOCs will be selected to descend a branch of |
| 304 |
the DDT hierarchy. |
| 305 |
|
| 306 |
The "rig" utility not only shows branches of the delegation hierarchy |
| 307 |
but can also report: |
| 308 |
|
| 309 |
o When a DDT Map-Server would forward a Map-Request to the ETRs at a |
| 310 |
registered LISP site. This is known as an "MS-ACK" action. |
| 311 |
|
| 312 |
o When a DDT Map-Server sends a Negative Map-Referral indicating |
| 313 |
that a requested EID is configured but not registered to the |
| 314 |
mapping database system. This is known as an "MS-NOT-REGISTERED" |
| 315 |
action. |
| 316 |
|
| 317 |
o When a DDT node is sending referrals for a transit or leaf node in |
| 318 |
the hierarchy. These are known as "NODE-REFERRAL" and |
| 319 |
"MS-REFERRAL" actions, respectively. |
| 320 |
|
| 321 |
o When a DDT node finds a hole in the address space that has not |
| 322 |
been allocated or configured in the delegation hierarchy. This is |
| 323 |
typically associated with a hole in a DDT node's configured |
| 324 |
authoritative prefix. This is known as a "DELEGATION-HOLE" |
| 325 |
action. |
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Farinacci, et al. Informational [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc8112">RFC 8112</a> LISP-DDT Referral Internet Groper (RIG) May 2017</span> |
| 335 |
|
| 336 |
|
| 337 |
o When a DDT node finds a hole in the address space that has not |
| 338 |
been allocated or configured in the delegation hierarchy at all. |
| 339 |
This is typically associated with a hole that is outside of a DDT |
| 340 |
node's authoritative prefix. This is known as a |
| 341 |
"NOT-AUTHORITATIVE" action. |
| 342 |
|
| 343 |
Refer to [<a href="./rfc8111" title=""Locator/ID Separation Protocol Delegated Database Tree (LISP-DDT)"">RFC8111</a>] for more details about Map-Referral actions. |
| 344 |
|
| 345 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Implementation Details</span> |
| 346 |
|
| 347 |
The Cisco LISP prototype implementations on IOS and NX-OS have "rig" |
| 348 |
support for IPv4 and IPv6 EIDs in either the default instance or a |
| 349 |
non-zero IID. |
| 350 |
|
| 351 |
The IOS syntax is: |
| 352 |
|
| 353 |
rig [instance-id <iid>] <eid> to <ddt-node> [follow-all-referrals] |
| 354 |
|
| 355 |
The NX-OS syntax is: |
| 356 |
|
| 357 |
rig [instance-id <iid>] { <hostname> | {<eid> | <eid6>} } |
| 358 |
to { <ddt-hostname> | {<ddt> | <ddt6>} } |
| 359 |
|
| 360 |
Here is some sample IOS output: |
| 361 |
|
| 362 |
Router# rig 12.0.1.1 to 1.1.1.1 |
| 363 |
|
| 364 |
Send Map-Request to DDT-node 1.1.1.1 ... node referral, rtt: 0 ms |
| 365 |
EID-prefix: [0] 12.0.0.0/16, ttl: 1440 |
| 366 |
referrals: 2.2.2.2 |
| 367 |
|
| 368 |
Send Map-Request to DDT-node 2.2.2.2 ... node referral, rtt: 0 ms |
| 369 |
EID-prefix: [0] 12.0.1.0/24, ttl: 1440 |
| 370 |
referrals: 4.4.4.4, 5.5.5.5 |
| 371 |
|
| 372 |
Send Map-Request to DDT-node 4.4.4.4 ... map-server acknowledgement, |
| 373 |
rtt: 0 ms |
| 374 |
EID-prefix: [0] 12.0.1.0/28, ttl: 1440 |
| 375 |
referrals: 4.4.4.4, 5.5.5.5 |
| 376 |
|
| 377 |
Router# rig 12.0.1.1 to 1.1.1.1 follow-all-referrals |
| 378 |
|
| 379 |
Send Map-Request to DDT-node 1.1.1.1 ... node referral, rtt: 4 ms |
| 380 |
EID-prefix: [0] 12.0.0.0/16, ttl: 1440 |
| 381 |
referrals: 2.2.2.2 |
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Farinacci, et al. Informational [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc8112">RFC 8112</a> LISP-DDT Referral Internet Groper (RIG) May 2017</span> |
| 391 |
|
| 392 |
|
| 393 |
Send Map-Request to DDT-node 2.2.2.2 ... node referral, rtt: 0 ms |
| 394 |
EID-prefix: [0] 12.0.1.0/24, ttl: 1440 |
| 395 |
referrals: 4.4.4.4, 5.5.5.5 |
| 396 |
|
| 397 |
Send Map-Request to DDT-node 4.4.4.4 ... map-server acknowledgement, |
| 398 |
rtt: 0 ms |
| 399 |
EID-prefix: [0] 12.0.1.0/28, ttl: 1440 |
| 400 |
referrals: 4.4.4.4, 5.5.5.5 |
| 401 |
|
| 402 |
Send Map-Request to DDT-node 5.5.5.5 ... map-server acknowledgement, |
| 403 |
rtt: 0 ms |
| 404 |
EID-prefix: [0] 12.0.1.0/28, ttl: 1440 |
| 405 |
referrals: 4.4.4.4, 5.5.5.5 |
| 406 |
|
| 407 |
No more referrals to pursue. |
| 408 |
|
| 409 |
Here is some sample NX-OS output: |
| 410 |
|
| 411 |
Router# rig 12.0.1.1 to 1.1.1.1 |
| 412 |
|
| 413 |
rig LISP-DDT hierarchy for EID [0] 12.0.1.1 |
| 414 |
Send Map-Request to DDT-node 1.1.1.1 ... replied, rtt: 0.003509 secs |
| 415 |
EID-prefix [0] *, ttl: 1440, action: node-referral, referrals: |
| 416 |
2.2.2.2, priority/weight: 0/0 |
| 417 |
|
| 418 |
Send Map-Request to DDT-node 2.2.2.2 ... replied, rtt: 0.003173 secs |
| 419 |
EID-prefix [0] 12.0.0.0/20, ttl: 1440, action: node-referral, |
| 420 |
referrals: |
| 421 |
3.3.3.3, priority/weight: 0/0 |
| 422 |
|
| 423 |
Send Map-Request to DDT-node 3.3.3.3 ... replied, rtt: 0.004145 secs |
| 424 |
EID-prefix [0] 12.0.1.0/24, ttl: 1440, action: node-referral, |
| 425 |
referrals: |
| 426 |
5.5.5.5, priority/weight: 0/0 |
| 427 |
6.6.6.6, priority/weight: 0/0 |
| 428 |
|
| 429 |
Send Map-Request to DDT-node 6.6.6.6 ... replied, rtt: 0.005800 secs |
| 430 |
EID-prefix [0] 12.0.1.0/28, ttl: 1440, action: ms-ack, referrals: |
| 431 |
5.5.5.5, priority/weight: 0/0 |
| 432 |
6.6.6.6, priority/weight: 0/0 |
| 433 |
|
| 434 |
|
| 435 |
|
| 436 |
|
| 437 |
|
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Farinacci, et al. Informational [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc8112">RFC 8112</a> LISP-DDT Referral Internet Groper (RIG) May 2017</span> |
| 447 |
|
| 448 |
|
| 449 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span> |
| 450 |
|
| 451 |
The use of "rig" does not affect the security of the LISP |
| 452 |
infrastructure, as it is simply a tool that facilitates diagnostic |
| 453 |
querying. See [<a href="./rfc6830" title=""The Locator/ID Separation Protocol (LISP)"">RFC6830</a>], [<a href="./rfc6833" title=""Locator/ID Separation Protocol (LISP) Map-Server Interface"">RFC6833</a>], [<a href="./rfc7835" title=""Locator/ID Separation Protocol (LISP) Threat Analysis"">RFC7835</a>], and [<a href="./rfc8111" title=""Locator/ID Separation Protocol Delegated Database Tree (LISP-DDT)"">RFC8111</a>] for |
| 454 |
descriptions of the security properties of the LISP infrastructure. |
| 455 |
|
| 456 |
LISP "rig" provides easy access to the information in the public |
| 457 |
mapping database. Therefore, it is important to protect the mapping |
| 458 |
information for private use. This can be provided by disallowing |
| 459 |
access to specific mapping entries or placing such entries in a |
| 460 |
private mapping database system. |
| 461 |
|
| 462 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. IANA Considerations</span> |
| 463 |
|
| 464 |
This document does not require any IANA actions. |
| 465 |
|
| 466 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span> |
| 467 |
|
| 468 |
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span> |
| 469 |
|
| 470 |
[<a id="ref-RFC791">RFC791</a>] Postel, J., "Internet Protocol", STD 5, <a href="./rfc791">RFC 791</a>, |
| 471 |
DOI 10.17487/RFC0791, September 1981, |
| 472 |
<<a href="http://www.rfc-editor.org/info/rfc791">http://www.rfc-editor.org/info/rfc791</a>>. |
| 473 |
|
| 474 |
[<a id="ref-RFC1034">RFC1034</a>] Mockapetris, P., "Domain names - concepts and facilities", |
| 475 |
STD 13, <a href="./rfc1034">RFC 1034</a>, DOI 10.17487/RFC1034, November 1987, |
| 476 |
<<a href="http://www.rfc-editor.org/info/rfc1034">http://www.rfc-editor.org/info/rfc1034</a>>. |
| 477 |
|
| 478 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 479 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, |
| 480 |
DOI 10.17487/RFC2119, March 1997, |
| 481 |
<<a href="http://www.rfc-editor.org/info/rfc2119">http://www.rfc-editor.org/info/rfc2119</a>>. |
| 482 |
|
| 483 |
[<a id="ref-RFC6830">RFC6830</a>] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "The |
| 484 |
Locator/ID Separation Protocol (LISP)", <a href="./rfc6830">RFC 6830</a>, |
| 485 |
DOI 10.17487/RFC6830, January 2013, |
| 486 |
<<a href="http://www.rfc-editor.org/info/rfc6830">http://www.rfc-editor.org/info/rfc6830</a>>. |
| 487 |
|
| 488 |
[<a id="ref-RFC6833">RFC6833</a>] Fuller, V. and D. Farinacci, "Locator/ID Separation |
| 489 |
Protocol (LISP) Map-Server Interface", <a href="./rfc6833">RFC 6833</a>, |
| 490 |
DOI 10.17487/RFC6833, January 2013, |
| 491 |
<<a href="http://www.rfc-editor.org/info/rfc6833">http://www.rfc-editor.org/info/rfc6833</a>>. |
| 492 |
|
| 493 |
[<a id="ref-RFC6835">RFC6835</a>] Farinacci, D. and D. Meyer, "The Locator/ID Separation |
| 494 |
Protocol Internet Groper (LIG)", <a href="./rfc6835">RFC 6835</a>, |
| 495 |
DOI 10.17487/RFC6835, January 2013, |
| 496 |
<<a href="http://www.rfc-editor.org/info/rfc6835">http://www.rfc-editor.org/info/rfc6835</a>>. |
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Farinacci, et al. Informational [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc8112">RFC 8112</a> LISP-DDT Referral Internet Groper (RIG) May 2017</span> |
| 503 |
|
| 504 |
|
| 505 |
[<a id="ref-RFC8111">RFC8111</a>] Fuller, V., Lewis, D., Ermagan, V., Jain, A., and A. |
| 506 |
Smirnov, "Locator/ID Separation Protocol Delegated |
| 507 |
Database Tree (LISP-DDT)", <a href="./rfc8111">RFC 8111</a>, DOI 10.17487/RFC8111, |
| 508 |
May 2017, <<a href="http://www.rfc-editor.org/info/rfc8111">http://www.rfc-editor.org/info/rfc8111</a>>. |
| 509 |
|
| 510 |
[<a id="ref-RFC8174">RFC8174</a>] Leiba, B., "Ambiguity of Uppercase vs Lowercase in |
| 511 |
<a href="./rfc2119">RFC 2119</a> Key Words", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc8174">RFC 8174</a>, |
| 512 |
DOI 10.17487/RFC8174, May 2017, |
| 513 |
<<a href="http://www.rfc-editor.org/info/rfc8174">http://www.rfc-editor.org/info/rfc8174</a>>. |
| 514 |
|
| 515 |
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span> |
| 516 |
|
| 517 |
[<a id="ref-RFC1918">RFC1918</a>] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G., |
| 518 |
and E. Lear, "Address Allocation for Private Internets", |
| 519 |
<a href="https://www.rfc-editor.org/bcp/bcp5">BCP 5</a>, <a href="./rfc1918">RFC 1918</a>, DOI 10.17487/RFC1918, February 1996, |
| 520 |
<<a href="http://www.rfc-editor.org/info/rfc1918">http://www.rfc-editor.org/info/rfc1918</a>>. |
| 521 |
|
| 522 |
[<a id="ref-RFC2460">RFC2460</a>] Deering, S. and R. Hinden, "Internet Protocol, Version 6 |
| 523 |
(IPv6) Specification", <a href="./rfc2460">RFC 2460</a>, DOI 10.17487/RFC2460, |
| 524 |
December 1998, <<a href="http://www.rfc-editor.org/info/rfc2460">http://www.rfc-editor.org/info/rfc2460</a>>. |
| 525 |
|
| 526 |
[<a id="ref-RFC3261">RFC3261</a>] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, |
| 527 |
A., Peterson, J., Sparks, R., Handley, M., and E. |
| 528 |
Schooler, "SIP: Session Initiation Protocol", <a href="./rfc3261">RFC 3261</a>, |
| 529 |
DOI 10.17487/RFC3261, June 2002, |
| 530 |
<<a href="http://www.rfc-editor.org/info/rfc3261">http://www.rfc-editor.org/info/rfc3261</a>>. |
| 531 |
|
| 532 |
[<a id="ref-RFC7835">RFC7835</a>] Saucez, D., Iannone, L., and O. Bonaventure, "Locator/ID |
| 533 |
Separation Protocol (LISP) Threat Analysis", <a href="./rfc7835">RFC 7835</a>, |
| 534 |
DOI 10.17487/RFC7835, April 2016, |
| 535 |
<<a href="http://www.rfc-editor.org/info/rfc7835">http://www.rfc-editor.org/info/rfc7835</a>>. |
| 536 |
|
| 537 |
[<a id="ref-RFC8060">RFC8060</a>] Farinacci, D., Meyer, D., and J. Snijders, "LISP Canonical |
| 538 |
Address Format (LCAF)", <a href="./rfc8060">RFC 8060</a>, DOI 10.17487/RFC8060, |
| 539 |
February 2017, <<a href="http://www.rfc-editor.org/info/rfc8060">http://www.rfc-editor.org/info/rfc8060</a>>. |
| 540 |
|
| 541 |
|
| 542 |
|
| 543 |
|
| 544 |
|
| 545 |
|
| 546 |
|
| 547 |
|
| 548 |
|
| 549 |
|
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Farinacci, et al. Informational [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc8112">RFC 8112</a> LISP-DDT Referral Internet Groper (RIG) May 2017</span> |
| 559 |
|
| 560 |
|
| 561 |
Acknowledgments |
| 562 |
|
| 563 |
The authors would like to thank Damien Saucez and Fabio Maino for |
| 564 |
their ideas and comments. Appreciation also goes to Joel Halpern, |
| 565 |
Luigi Iannone, and Nevil Brownlee for their help with this document. |
| 566 |
|
| 567 |
Authors' Addresses |
| 568 |
|
| 569 |
Dino Farinacci |
| 570 |
lispers.net |
| 571 |
San Jose, California |
| 572 |
United States of America |
| 573 |
|
| 574 |
Phone: 408-718-2001 |
| 575 |
Email: [email protected] |
| 576 |
|
| 577 |
|
| 578 |
Amit Jain |
| 579 |
Juniper Networks |
| 580 |
San Jose, California |
| 581 |
United States of America |
| 582 |
|
| 583 |
Email: [email protected] |
| 584 |
|
| 585 |
|
| 586 |
Isidor Kouvelas |
| 587 |
Arista |
| 588 |
Santa Clara, California |
| 589 |
United States of America |
| 590 |
|
| 591 |
Email: [email protected] |
| 592 |
|
| 593 |
|
| 594 |
Darrel Lewis |
| 595 |
Cisco Systems |
| 596 |
Tasman Ave. |
| 597 |
San Jose, California |
| 598 |
United States of America |
| 599 |
|
| 600 |
Email: [email protected] |
| 601 |
|
| 602 |
|
| 603 |
|
| 604 |
|
| 605 |
|
| 606 |
|
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
Farinacci, et al. Informational [Page 11] |
| 613 |
</pre> |