idnits 2.17.1 draft-ietf-lisp-mib-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document date (January 5, 2011) is 4859 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Unused Reference: 'RFC1035' is defined on line 1769, but no explicit reference was found in the text == Unused Reference: 'RFC2404' is defined on line 1775, but no explicit reference was found in the text == Unused Reference: 'RFC4634' is defined on line 1791, but no explicit reference was found in the text == Unused Reference: 'LISP-MCAST' is defined on line 1799, but no explicit reference was found in the text == Unused Reference: 'LISP-MN' is defined on line 1804, but no explicit reference was found in the text == Outdated reference: A later version (-06) exists of draft-ietf-lisp-interworking-01 == Outdated reference: A later version (-10) exists of draft-farinacci-lisp-lcaf-01 == Outdated reference: A later version (-24) exists of draft-ietf-lisp-07 == Outdated reference: A later version (-10) exists of draft-ietf-lisp-alt-04 == Outdated reference: A later version (-16) exists of draft-ietf-lisp-ms-05 ** Obsolete normative reference: RFC 4634 (Obsoleted by RFC 6234) == Outdated reference: A later version (-14) exists of draft-ietf-lisp-multicast-03 == Outdated reference: A later version (-16) exists of draft-meyer-lisp-mn-01 Summary: 1 error (**), 0 flaws (~~), 14 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group G. Schudel 3 Internet-Draft A. Jain 4 Intended status: Experimental V. Moreno 5 Expires: July 9, 2011 cisco Systems 6 January 5, 2011 8 LISP MIB 9 draft-ietf-lisp-mib-00 11 Abstract 13 This document defines managed objects for the Locator/ID Separation 14 Protocol (LISP). These objects provide information useful for 15 monitoring LISP devices, including basic configuration information, 16 LISP status, and operational statistics. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on July 9, 2011. 35 Copyright Notice 37 Copyright (c) 2011 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Requirements Notation . . . . . . . . . . . . . . . . . . . . 3 53 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 3. The Internet-Standard Management Framework . . . . . . . . . . 4 55 4. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 4 56 5. LISP MIB Objectives . . . . . . . . . . . . . . . . . . . . . 6 57 6. Structure of LISP MIB Module . . . . . . . . . . . . . . . . . 7 58 6.1. Overview of Defined Notifications . . . . . . . . . . . . 7 59 6.2. Overview of Defined Tables . . . . . . . . . . . . . . . . 7 60 7. LISP MIB Definition . . . . . . . . . . . . . . . . . . . . . 8 61 8. Relationship to Other MIB Modules . . . . . . . . . . . . . . 37 62 8.1. MIB modules required for IMPORTS . . . . . . . . . . . . . 37 63 9. Security Considerations . . . . . . . . . . . . . . . . . . . 37 64 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37 65 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 38 66 11.1. Normative References . . . . . . . . . . . . . . . . . . . 38 67 11.2. Informative References . . . . . . . . . . . . . . . . . . 39 68 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 39 69 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 39 70 Appendix C. Acknowledgments . . . . . . . . . . . . . . . . . . . 40 72 1. Requirements Notation 74 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 75 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 76 document are to be interpreted as described in [RFC2119]. 78 2. Introduction 80 This draft describes the Management Information Base (MIB) module for 81 use with network management protocols in the Internet community. 82 Specifically, the MIB for managing Locator/ID Separation Protocol 83 (LISP) devices is described. 85 LISP [LISP] specifies a network-based architecture and mechanisms 86 that implement a new semantic for IP addressing using two separate 87 name spaces: Endpoint Identifiers (EIDs), used within sites, and 88 Routing Locators (RLOCs), used on the transit networks that make up 89 the Internet infrastructure. To achieve this separation, LISP 90 defines protocol mechanisms for mapping from EIDs to RLOCs. In 91 addition, LISP assumes the existence of a database to store and 92 globally propagate those mappings [LISP-MS] [LISP-ALT]. 94 From a data plane perspective, LISP traffic is handled exclusively at 95 the network layer by devices performing Ingress Tunnel Router (ITR) 96 and Egress Tunnel Router (ETR) LISP functions. Data plane operations 97 performed by these devices are described in [LISP]. Additionally, 98 data plane interworking between legacy (Internet) and LISP sites is 99 implemented by devices performing Proxy ITR (PITR) and Proxy ETR 100 (PETR) functions. The data plane operations of these devices is 101 described in [INTERWORK]. 103 From a control plane perspective, LISP employs mechanisms related to 104 creating, maintaining, and resolving mappings from EIDs to RLOCs. 105 LISP ITRs, ETRs, PITRs, and PETRs perform specific control plane 106 functions, and these control plane operations are described in 107 [LISP]. Additionally, LISP infrastructure devices supporting LISP 108 control plane functionality include Map-Servers and Map-Resolvers, 109 and the control plane operations of these devices are described in 110 [LISP-MS]. Finally, while not specifically required, this document 111 assumes that a LISP+ALT database mapping infrastructure exists as 112 part of the LISP control plane. The control plane operations of the 113 ALT are described in [LISP-ALT]. Note that this MIB does not provide 114 support for the ALT since ALT statistics may be obtained through 115 existing BGP and tunnel MIBs. 117 3. The Internet-Standard Management Framework 119 For a detailed overview of the documents that describe the current 120 Internet-Standard Management Framework, please refer to section 7 of 121 RFC 3410 [RFC3410]. 123 Managed objects are accessed via a virtual information store, termed 124 the Management Information Base or MIB. MIB objects are generally 125 accessed through the Simple Network Management Protocol (SNMP). 126 Objects in the MIB are defined using the mechanisms defined in the 127 Structure of Management Information (SMI). This memo specifies a MIB 128 module that is compliant to the SMIv2, which is described in STD 58, 129 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 130 [RFC2580]. 132 4. Definition of Terms 134 Routing Locator (RLOC): a 32-bit (for IPv4) or 128-bit (for IPv6) 135 value used in the source and destination address fields of the 136 second (outer-most) IP header of a LISP packet. RLOC addresses 137 are allocated to an egress tunnel router (ETR) and numbered from 138 topologically-aggregatable blocks assigned to a site at each point 139 to which it attaches to the global Internet. 141 Endpoint ID (EID): a 32-bit (for IPv4) or 128-bit (for IPv6) value 142 used in the source and destination address fields of the first 143 (inner-most) IP header of a LISP packet. A source EID is 144 allocated to a host from an EID-prefix block associated with the 145 site where the host is located. A host determines a destination 146 EID in the same way that it determines a destination address 147 today, for example through a DNS lookup or SIP exchange. 149 EID-to-RLOC Map-Cache: a short-lived, on-demand table maintained 150 locally in an ITR or PITR that stores, tracks, and is responsible 151 for timing-out and otherwise validating EID-to-RLOC mappings. 152 This table is distinct from the full "database" of EID-to-RLOC 153 mappings in that it is dynamic and relatively small. At a given 154 moment in time, it consists only of entries for those sites to 155 which the ITR or PITR is currently communicating or has 156 communicated with within the configured TTL period. 158 EID-to-RLOC Mapping-Database: a global distributed database that 159 contains all known EID-to-RLOC mappings. Each potential ETR 160 typically contains a small piece of the database consisting of 161 only the EID-to-RLOC mappings for the EID prefix(es) for which the 162 ETR is "authoritative" and the RLOC(s) by which those EID 163 prefix(es) are reachable from the global Internet. 165 Ingress Tunnel Router (ITR): a router that accepts an IP packet with 166 a single IP header (more precisely, an IP packet that does not 167 contain a LISP header), treats this "inner" IP destination address 168 as an EID and performs an EID-to-RLOC mapping lookup, and then 169 prepends an "outer" IP header with one of its own globally- 170 routable RLOCs in the source address field and the RLOC resulting 171 from the mapping lookup in the destination address field. That 172 is, in general an ITR receives an IP packet from site end-systems 173 on one side and sends a LISP-encapsulated IP packet toward the 174 Internet on the other side. 176 Egress Tunnel Router (ETR): a router that accepts an IP packet where 177 the destination address in the "outer" IP header is one of its own 178 RLOCs, strips the "outer" header, and forwards the packet based on 179 the next IP header found. That is, in general an ETR receives 180 LISP-encapsulated IP packets from the Internet on one side and 181 sends decapsulated IP packets toward site end-systems on the other 182 side. 184 xTR: is a general reference to an ITR or ETR when direction of data 185 flow is not part of the context description. xTR refers to the 186 router that is the tunnel endpoint and performs both ITR and ETR 187 functionality. For example, "An xTR can be located at the 188 Customer Edge (CE) router", meaning both ITR and ETR functionality 189 is activated at the CE router. 191 Proxy ITR (PITR): a router that acts like an ITR but does so on 192 behalf of non-LISP sites which send packets to destinations at 193 LISP sites. The PITR, also known as a PTR, is defined and 194 described in [INTERWORK]. 196 Proxy ETR (PETR): a router that acts like an ETR but does so on 197 behalf of LISP sites which send packets to destinations at non- 198 LISP sites. The PETR is defined and described in [INTERWORK]. 200 LISP Site: is a set of routers in an edge network that are under a 201 single technical administration. LISP routers which reside in the 202 edge network are the demarcation points to separate the edge 203 network from the core network. 205 Map-Server: a LISP network infrastructure component which learns 206 EID-to-RLOC mapping entries from an authoritative source such as 207 an ETR though static configuration, or another out-of-band 208 mechanism. A Map-Server advertises these mappings into the 209 distributed mapping database such as that described in [LISP-ALT]. 211 Map-Resolver: a LISP network infrastructure component which accepts 212 LISP Encapsulated Map-Requests, typically from an ITR, and quickly 213 determines whether or not the destination IP address is part of 214 the EID namespace. If it is, the Map-Resolver finds the 215 appropriate EID-to-RLOC mapping by consulting the distributed 216 mapping database system such as that described in [LISP-ALT]. If 217 it is not, a Negative Map-Reply is immediately returned. 219 Map-Reply: a LISP Map-Reply message type returned in response to a 220 Map-Request for a destination EID that exists in the mapping 221 database and contains the locator-set and associated policy for 222 the queried EID. Information returned in a Map-Reply is stored in 223 the EID-to-RLOC Map-Cache. 225 Negative Map-Reply: a LISP Map-Reply message type that contains an 226 empty locator-set. Returned in response to a Map-Request if the 227 destination EID does not exist in the mapping database. 228 Typically, this means that the "EID" being requested is an IP 229 address connected to a non-LISP site. Information returned in a 230 Negative Map-Reply is stored in the EID-to-RLOC Map-Cache. 232 LISP+ALT: a static network built using Border Gateway Protocol (BGP, 233 [RFC4271]), BGP multi-protocol extension [RFC4760], and Generic 234 Routing Encapsulation (GRE, [RFC2784]) to construct an overlay 235 network of devices (ALT Routers) which operate on EID-prefixes and 236 use EIDs as forwarding destinations. This LISP+ALT network may, 237 but is not required to be, used by LISP to find EID-to-RLOC 238 mappings. LISP+ALT is described in [LISP-ALT]. 240 5. LISP MIB Objectives 242 The objectives for defining this LISP MIB module are as follows: 244 o Provide a means for obtaining a list of enabled LISP features and 245 the current status of configuration attributes related to those 246 features. As an example, LISP capabilities which could be enabled 247 include ITR, ETR, PITR, PETR, MS or MR support for IPv4 or IPv6 248 address families. Other examples include, indicating whether 249 rloc-probing is enabled, and indicating the configured map-cache 250 limit value. 252 o Provide a means for obtaining the current attributes of various 253 LISP tables, such as the EID-to-RLOC policy data contained in the 254 Map-Cache, or the local EID-to-RLOC policy data contained in the 255 Mapping-Database. 257 o Provide a means for obtaining the current operational statistics 258 of various LISP functions, such as the number of packets 259 encapsulated and decapsulated by the device. Other counters of 260 operational interest, depending on LISP function, include things 261 like the current number of map-cache entries, and the total number 262 and rate of map-requests received and sent. 264 6. Structure of LISP MIB Module 266 6.1. Overview of Defined Notifications 268 No LISP MIB notifications are defined. 270 6.2. Overview of Defined Tables 272 The LISP MIB module is composed of ten tables of objects, as follows: 274 Lisp - This table provides information representing the various lisp 275 features that can be enabled on LISP devices. 277 LispMappingDatabase - This table represents the EID-to-RLOC database 278 that contains the EID-prefix to RLOC mappings configured on an 279 ETR. In general, this table would be representative of all such 280 mappings for a given site that this device belongs to. 282 LispMappingDatabaseLocator - This table represents the set of 283 routing locators contained in the EID-to-RLOC database configured 284 on an ETR. 286 LispMapCache - This table represents the short-lived, on-demand 287 table on an ITR that stores, tracks, and is responsible for 288 timing-out and otherwise validating EID-to-RLOC mappings. 290 LispMapCacheLocator - This table represents the set of locators per 291 EID prefix contained in the map-cache table of an ITR. 293 LispSite - This table provides the properties of each lisp site that 294 is served by this device when configured to be a Map-Server. 296 LispSiteLocator - This table provides the properties of all locators 297 per lisp site that is served by this device when configured to be 298 a Map-Server. 300 LispMapServers - This table provides the properties of all Map- 301 Servers that this device is configured to use. 303 LispMapResolvers - This table provides the properties of all Map- 304 Resolvers that this device is configured to use. 306 lispUseProxyEtr - This table provides the properties of all Proxy 307 ETRs that this device is configured to use. 309 7. LISP MIB Definition 311 LISP-MIB DEFINITIONS ::= BEGIN 312 IMPORTS 313 MODULE-IDENTITY, OBJECT-TYPE, 314 Unsigned32, Counter64,TimeTicks, 315 NOTIFICATION-TYPE FROM SNMPv2-SMI -- [RFC2578] 316 MODULE-COMPLIANCE, OBJECT-GROUP 317 NOTIFICATION-GROUP FROM SNMPv2-CONF -- [RFC2580] 318 TEXTUAL-CONVENTION, TruthValue, 319 RowStatus FROM SNMPv2-TC -- [RFC2579] 320 AddressFamilyNumbers 321 FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB -- [IANA] 323 lispMIB MODULE-IDENTITY 324 LAST-UPDATED "201101050000Z" -- 05 January 2011" 325 ORGANIZATION 326 "IETF Locator/ID Separation Protocol (LISP) Working Group" 327 CONTACT-INFO 328 "Email: lisp@ietf.org 329 WG charter: 330 http://www.ietf.org/html.charters/lisp-charter.html" 331 DESCRIPTION 332 "This memo describes the Management Information Base (MIB) 333 module for use with network management protocols in the 334 management of Locator/ID Separation Protocol (LISP) devices. 336 Copyright (C) The IETF Trust (2010)." 337 REVISION "201101050000Z" -- 05 January 2011" 339 ::= { xxxxx } 341 -- 342 -- Textual Conventions 343 -- 344 LispAddressType ::= TEXTUAL-CONVENTION 345 STATUS current 346 DESCRIPTION 347 "LISP architecture can be applied to a wide variety of 348 address-families. This textual-convention is a 349 generalization for representing addresses that belong 350 to those address-families. For convenience, this 351 document refers to any such address as a lisp address. 352 LispAddressType textual-convention consists of 353 the following four tuples: 354 1. IANA Address Family Numbers: This tuple follows 355 the AddressFamilyNumbers textual-convention 356 described in [IANA]. The enumerations are listed 357 in [IANA]. Note that the list of address family 358 numbers is maintained by IANA. 359 2. Length of LISP address: This tuple is an INTEGER 360 to give the octet length of the next tuple. 361 3. Lisp address: A lisp address can be an address 362 belonging to any of the IANA Address Families. 363 Particularly, when the address family is Lisp 364 Canonical Address Format (LCAF) [LCAF] with IANA 365 assigned Address Family Number 16387, then 366 the first octet of this tuple indicates the LCAF 367 type, and the rest of this tuple is same as the 368 encoding format of the LISP Canonical Address 369 after the length field, as defined in [LCAF]. 370 4. Mask-length of lisp address." 371 REFERENCE "[LISP]" 372 SYNTAX OCTET STRING (SIZE (0..1024)) 374 lispTable OBJECT-TYPE 375 SYNTAX SEQUENCE OF lispEntry 376 MAX-ACCESS not-accessible 377 STATUS current 378 DESCRIPTION 379 "This table represents the various lisp features 380 that can be enabled on lisp devices." 382 REFERENCE "[LISP]" 383 ::= { lisp 1 } 385 lispEntry OBJECT-TYPE 386 SYNTAX lispEntry 387 MAX-ACCESS not-accessible 388 STATUS current 389 DESCRIPTION 390 "An entry (conceptual row) in the lispTable." 391 INDEX { lispAfi } 392 ::= { lispTable 1 } 394 lispEntry ::= SEQUENCE { 395 lispAddressFamily AddressFamilyNumbers, 396 lispItrEnabled TruthValue, 397 lispEtrEnabled TruthValue, 398 lispProxyItrEnabled TruthValue, 399 lispProxyEtrEnabled TruthValue, 400 lispMapServerEnabled TruthValue, 401 lispMapResolverEnabled TruthValue, 402 lispMapCacheSize Unsigned32, 403 lispMapCacheLimit Unsigned32, 404 lispEtrMapCacheTtl Unsigned32, 405 lispRlocProbeEnabled TruthValue, 406 lispEtrAcceptMapDataEnabled TruthValue, 407 lispEtrAcceptMapDataVerifyEnabled TruthValue, 408 lispMapRequestsIn Counter64, 409 lispMapRequestsOut Counter64, 410 lispMapRepliesIn Counter64, 411 lispMapRepliesOut Counter64, 412 lispMapRegistersIn Counter64, 413 lispMapRegistersOut Counter64 414 } 416 lispAddressFamily OBJECT-TYPE 417 SYNTAX AddressFamilyNumbers 418 MAX-ACCESS not-accessible 419 STATUS current 420 DESCRIPTION 421 "The address family number of the lisp device that 422 is able to lisp process a packet destined for 423 that address family." 424 ::= { lispEntry 1 } 426 lispItrEnabled OBJECT-TYPE 427 SYNTAX TruthValue 428 MAX-ACCESS accessible 429 STATUS current 430 DESCRIPTION 431 "Indicates the status of ITR role on this device." 432 ::= { lispEntry 2 } 434 lispEtrEnabled OBJECT-TYPE 435 SYNTAX TruthValue 436 MAX-ACCESS accessible 437 STATUS current 438 DESCRIPTION 439 "Indicates the status of ETR role on this device." 440 ::= { lispEntry 3 } 442 lispProxyItrEnabled OBJECT-TYPE 443 SYNTAX TruthValue 444 MAX-ACCESS accessible 445 STATUS current 446 DESCRIPTION 447 "Indicates the status of Proxy-ITR role on this 448 device." 449 ::= { lispEntry 4 } 451 lispProxyEtrEnabled OBJECT-TYPE 452 SYNTAX TruthValue 453 MAX-ACCESS accessible 454 STATUS current 455 DESCRIPTION 456 "Indicates the status of Proxy-ETR role on this 457 device." 458 ::= { lispEntry 5 } 460 lispMapServerEnabled OBJECT-TYPE 461 SYNTAX TruthValue 462 MAX-ACCESS accessible 463 STATUS current 464 DESCRIPTION 465 "Indicates the status of Map Server role on this 466 device." 467 ::= { lispEntry 6 } 469 lispMapResolverEnabled OBJECT-TYPE 470 SYNTAX TruthValue 471 MAX-ACCESS accessible 472 STATUS current 473 DESCRIPTION 474 "Indicates the status of Map Resolver role on 475 this device." 476 ::= { lispEntry 7 } 478 lispMapCacheSize OBJECT-TYPE 479 SYNTAX Unsigned32 480 MAX-ACCESS accessible 481 STATUS current 482 DESCRIPTION 483 "Size of EID-to-RLOC map cache on this device." 484 ::= { lispEntry 8 } 486 lispMapCacheLimit OBJECT-TYPE 487 SYNTAX Unsigned32 488 MAX-ACCESS accessible 489 STATUS current 490 DESCRIPTION 491 "Maximum permissible size of EID-to-RLOC map 492 cache on this device." 493 ::= { lispEntry 9 } 495 lispEtrMapCacheTtl OBJECT-TYPE 496 SYNTAX Unsigned32 497 MAX-ACCESS accessible 498 STATUS current 499 DESCRIPTION 500 "Time in minutes this device will store the 501 mapping record in the map cache." 502 ::= { lispEntry 10 } 504 lispRlocProbeEnabled OBJECT-TYPE 505 SYNTAX TruthValue 506 MAX-ACCESS accessible 507 STATUS current 508 DESCRIPTION 509 "Indicates the status of rloc-probing feature 510 on this device." 511 ::= { lispEntry 11 } 513 lispEtrAcceptMapData OBJECT-TYPE 514 SYNTAX TruthValue 515 MAX-ACCESS accessible 516 STATUS current 517 DESCRIPTION 518 "Indicates the status of this device for 519 accepting piggybacked mapping data received 520 in a map-request." 521 ::= { lispEntry 12 } 523 lispEtrAcceptMapDataVerify OBJECT-TYPE 524 SYNTAX TruthValue 525 MAX-ACCESS accessible 526 STATUS current 527 DESCRIPTION 528 "Indicates the status of this device for 529 verifying accepted piggybacked mapping data 530 received in a map-request." 531 ::= { lispEntry 13 } 533 lispMapRequestsIn OBJECT-TYPE 534 SYNTAX Counter64 535 MAX-ACCESS accessible 536 STATUS current 537 DESCRIPTION 538 "Total number of map requests received by this 539 device for any EID prefix of the given address 540 family." 541 ::= { lispEntry 14 } 543 lispMapRequestsOut OBJECT-TYPE 544 SYNTAX Counter64 545 MAX-ACCESS accessible 546 STATUS current 547 DESCRIPTION 548 "Total number of map requests sent by this device 549 for any EID prefix of the given address family." 550 ::= { lispEntry 15 } 552 lispMapRepliesIn OBJECT-TYPE 553 SYNTAX Counter64 554 MAX-ACCESS accessible 555 STATUS current 556 DESCRIPTION 557 "Total number of map replies received by this device 558 for any EID prefix of the given address family." 559 ::= { lispEntry 16 } 561 lispMapRepliesOut OBJECT-TYPE 562 SYNTAX Counter64 563 MAX-ACCESS accessible 564 STATUS current 565 DESCRIPTION 566 "Total number of map replies sent by this device for 567 any EID prefix of the given address family." 568 ::= { lispEntry 17 } 570 lispMapRegistersIn OBJECT-TYPE 571 SYNTAX Counter64 572 MAX-ACCESS accessible 573 STATUS current 574 DESCRIPTION 575 "Total number of map registers received by this device 576 for any EID prefix of the given address family." 577 ::= { lispEntry 18 } 579 lispMapRegistersOut OBJECT-TYPE 580 SYNTAX Counter64 581 MAX-ACCESS accessible 582 STATUS current 583 DESCRIPTION 584 "Total number of map registers sent by this device 585 for any EID prefix of the given address family." 586 ::= { lispEntry 19 } 588 lispMappingDatabaseTable OBJECT-TYPE 589 SYNTAX SEQUENCE OF lispMappingDatabaseEntry 590 MAX-ACCESS not-accessible 591 STATUS current 592 DESCRIPTION 593 "This table represents the EID-to-RLOC mapping database 594 that contains the EID-prefix to RLOC mappings 595 configured on an ETR. In general, this table would be 596 representative of all such mappings for a given site 597 that this device belongs to." 598 REFERENCE "[LISP]" 599 ::= { lisp 2 } 601 lispMappingDatabaseEntry OBJECT-TYPE 602 SYNTAX lispMappingDatabaseEntry 603 MAX-ACCESS not-accessible 604 STATUS current 605 DESCRIPTION 606 "An entry (conceptual row) in the 607 lispMappingDatabaseTable." 608 INDEX { lispMappingDatabaseEidLength 609 lispMappingDatabaseEid } 610 ::= { lispMappingDatabaseTable 1 } 612 lispMappingDatabaseEntry ::= SEQUENCE { 613 lispMappingDatabaseEidLength INTEGER, 614 lispMappingDatabaseEid LispAddressType, 615 lispMappingDatabaseLsb Unsigned32, 616 lispMappingDatabaseEidPartitioned TruthValue, 617 lispMappingDatabaseDecapOctets Counter64, 618 lispMappingDatabaseDecapPkts Counter64 619 lispMappingDatabaseEncapOctets Counter64, 620 lispMappingDatabaseEncapPkts Counter64 621 } 623 lispMappingDatabaseEidLength OBJECT-TYPE 624 SYNTAX INTEGER 625 MAX-ACCESS not-accessible 626 STATUS current 627 DESCRIPTION 628 "This object gives the length of 629 lispMappingDatabaseEid, the next object." 630 ::= { lispMappingDatabaseEntry 1 } 632 lispMappingDatabaseEid OBJECT-TYPE 633 SYNTAX LispAddressType 634 MAX-ACCESS not-accessible 635 STATUS current 636 DESCRIPTION 637 "The EID prefix of the mapping database." 638 ::= { lispMappingDatabaseEntry 2 } 640 lispMappingDatabaseLsb OBJECT-TYPE 641 SYNTAX Unsigned32 642 MAX-ACCESS accessible 643 STATUS current 644 DESCRIPTION 645 "The locator status bits for this EID prefix." 646 ::= { lispMappingDatabaseEntry 3 } 648 lispMappingDatabaseEidPartitioned OBJECT-TYPE 649 SYNTAX TruthValue 650 MAX-ACCESS accessible 651 STATUS current 652 DESCRIPTION 653 "Indicates if this device is partitioned from 654 the site that contains this EID prefix." 655 ::= { lispMappingDatabaseEntry 4 } 657 lispMappingDatabaseDecapOctets OBJECT-TYPE 658 SYNTAX Counter64 659 MAX-ACCESS accessible 660 STATUS current 661 DESCRIPTION 662 "The number of octets of Lisp packets that were 663 decapsulated by this device addressed to a host 664 within this EID-prefix." 665 ::= { lispMappingDatabaseEntry 5 } 667 lispMappingDatabaseDecapPackets OBJECT-TYPE 668 SYNTAX Counter64 669 MAX-ACCESS accessible 670 STATUS current 671 DESCRIPTION 672 "The number of Lisp packets that were decapsulated 673 by this device addressed to a host within this 674 EID-prefix." 675 ::= { lispMappingDatabaseEntry 6 } 677 lispMappingDatabaseEncapOctets OBJECT-TYPE 678 SYNTAX Counter64 679 MAX-ACCESS accessible 680 STATUS current 681 DESCRIPTION 682 "The number of octets of Lisp packets, that were 683 encapsulated by this device, whose inner header 684 source address matched this EID prefix." 685 ::= { lispMappingDatabaseEntry 7 } 687 lispMappingDatabaseEncapPackets OBJECT-TYPE 688 SYNTAX Counter64 689 MAX-ACCESS accessible 690 STATUS current 691 DESCRIPTION 692 "The number of Lisp packets, that were encapsulated 693 by this device, whose inner header source address 694 matched this EID prefix." 695 ::= { lispMappingDatabaseEntry 8 } 697 lispMappingDatabaseLocatorTable OBJECT-TYPE 698 SYNTAX SEQUENCE OF lispMappingDatabaseLocatorEntry 699 MAX-ACCESS not-accessible 700 STATUS current 701 DESCRIPTION 702 "This table represents the set of routing locators 703 per EID prefix contained in the EID-to-RLOC database 704 configured on an ETR." 705 REFERENCE "[LISP]" 706 ::= { lisp 3 } 708 lispMappingDatabaseLocatorEntry OBJECT-TYPE 709 SYNTAX lispMappingDatabaseLocatorEntry 710 MAX-ACCESS not-accessible 711 STATUS current 712 DESCRIPTION 713 "An entry (conceptual row) in the 714 lispMappingDatabaseLocatorTable." 715 INDEX { lispMappingDatabaseLocatorEidLength 716 lispMappingDatabaseLocatorEid 717 lispMappingDatabaseLocatorRlocAfi 718 lispMappingDatabaseLocatorEncodedRlocLength 719 lispMappingDatabaseLocatorEncodedRloc } 720 ::= { lispMappingDatabaseLocatorTable 1 } 722 lispMappingDatabaseLocatorEntry ::= SEQUENCE { 723 lispMappingDatabaseLocatorEidLength INTEGER, 724 lispMappingDatabaseLocatorEid LispAddressType, 725 lispMappingDatabaseLocatorRlocLength INTEGER, 726 lispMappingDatabaseLocatorRloc LispAddressType, 727 lispMappingDatabaseLocatorRlocPriority INTEGER, 728 lispMappingDatabaseLocatorRlocWeight INTEGER, 729 lispMappingDatabaseLocatorRlocMPriority INTEGER, 730 lispMappingDatabaseLocatorRlocMWeight INTEGER, 731 lispMappingDatabaseLocatorRlocState INTEGER, 732 lispMappingDatabaseLocatorRlocLocal INTEGER, 733 lispMappingDatabaseLocatorRlocDecapOctets Counter64, 734 lispMappingDatabaseLocatorRlocDecapPackets Counter64 735 lispMappingDatabaseLocatorRlocEncapOctets Counter64, 736 lispMappingDatabaseLocatorRlocEncapPackets Counter64 737 } 739 lispMappingDatabaseLocatorEidLength OBJECT-TYPE 740 SYNTAX INTEGER 741 MAX-ACCESS not-accessible 742 STATUS current 743 DESCRIPTION 744 "This object is used to get the length of 745 lispMappingDatabaseLocatorEid, the next 746 object." 747 ::= { lispMappingDatabaseLocatorEntry 1 } 749 lispMappingDatabaseLocatorEid OBJECT-TYPE 750 SYNTAX LispAddressType 751 MAX-ACCESS not-accessible 752 STATUS current 753 DESCRIPTION 754 "The EID prefix of the mapping database 755 mapped to the given locator." 756 ::= { lispMappingDatabaseLocatorEntry 2 } 758 lispMappingDatabaseLocatorRlocLength OBJECT-TYPE 759 SYNTAX INTEGER 760 MAX-ACCESS not-accessible 761 STATUS current 762 DESCRIPTION 763 "This object is used to get the length of 764 lispMappingDatabaseLocatorRloc, the next 765 object." 766 ::= { lispMappingDatabaseLocatorEntry 3 } 768 lispMappingDatabaseLocatorRloc OBJECT-TYPE 769 SYNTAX LispAddressType 770 MAX-ACCESS not-accessible 771 STATUS current 772 DESCRIPTION 773 "This object is a locator for the given 774 EID prefix in the mapping database." 775 ::= { lispMappingDatabaseLocatorEntry 4 } 777 lispMappingDatabaseLocatorRlocPriority OBJECT-TYPE 778 SYNTAX INTEGER 779 MAX-ACCESS accessible 780 STATUS current 781 DESCRIPTION 782 "The unicast priority of the RLOC." 784 ::= { lispMappingDatabaseLocatorEntry 5 } 786 lispMappingDatabaseLocatorRlocWeight OBJECT-TYPE 787 SYNTAX INTEGER 788 MAX-ACCESS accessible 789 STATUS current 790 DESCRIPTION 791 "The unicast weight of the RLOC." 792 ::= { lispMappingDatabaseLocatorEntry 6 } 794 lispMappingDatabaseLocatorRlocMPriority OBJECT-TYPE 795 SYNTAX INTEGER 796 MAX-ACCESS accessible 797 STATUS current 798 DESCRIPTION 799 "The multicast priority of the RLOC." 800 ::= { lispMappingDatabaseLocatorEntry 7 } 802 lispMappingDatabaseLocatorRlocMWeight OBJECT-TYPE 803 SYNTAX INTEGER 804 MAX-ACCESS accessible 805 STATUS current 806 DESCRIPTION 807 "The multicast weight of the RLOC." 808 ::= { lispMappingDatabaseLocatorEntry 8 } 810 lispMappingDatabaseLocatorRlocState OBJECT-TYPE 811 SYNTAX INTEGER 812 MAX-ACCESS accessible 813 STATUS current 814 DESCRIPTION 815 "The state of this RLOC as per this device. 816 0 is for up, 1 is for down ..." 817 ::= { lispMappingDatabaseLocatorEntry 9 } 819 lispMappingDatabaseLocatorRlocLocal OBJECT-TYPE 820 SYNTAX INTEGER 821 MAX-ACCESS accessible 822 STATUS current 823 DESCRIPTION 824 "Object value is 1 if the RLOC is an address 825 on this device, 0 if otherwise." 826 ::= { lispMappingDatabaseLocatorEntry 10 } 828 lispMappingDatabaseLocatorRlocDecapOctets OBJECT-TYPE 829 SYNTAX Counter64 830 MAX-ACCESS accessible 831 STATUS current 832 DESCRIPTION 833 "The number of octets of Lisp packets that were 834 addressed to this RLOC of the EID-prefix and 835 were decapsulated." 836 ::= { lispMappingDatabaseLocatorEntry 11 } 838 lispMappingDatabaseLocatorRlocDecapPackets OBJECT-TYPE 839 SYNTAX Counter64 840 MAX-ACCESS accessible 841 STATUS current 842 DESCRIPTION 843 "The number of Lisp packets that were addressed to 844 this RLOC of the EID-prefix and were decapsulated." 845 ::= { lispMappingDatabaseLocatorEntry 12 } 847 lispMappingDatabaseLocatorRlocEncapOctets OBJECT-TYPE 848 SYNTAX Counter64 849 MAX-ACCESS accessible 850 STATUS current 851 DESCRIPTION 852 "The number of octets of Lisp packets that were 853 encapsulated by this device using this RLOC 854 address as the source, and that were sourced by 855 an address of this EID-prefix." 856 ::= { lispMappingDatabaseLocatorEntry 13 } 858 lispMappingDatabaseLocatorRlocEncapPackets OBJECT-TYPE 859 SYNTAX Counter64 860 MAX-ACCESS accessible 861 STATUS current 862 DESCRIPTION 863 "The number of Lisp packets that were encapsulated 864 by this device using this RLOC address as the 865 source, and that were sourced by an address of 866 this EID-prefix." 867 ::= { lispMappingDatabaseLocatorEntry 14 } 869 lispMapCacheTable OBJECT-TYPE 870 SYNTAX SEQUENCE OF lispMapCacheEntry 871 MAX-ACCESS not-accessible 872 STATUS current 873 DESCRIPTION 874 "This table represents the short-lived, on-demand 875 table on an ITR that stores, tracks, and is 876 responsible for timing-out and otherwise 877 validating EID-to-RLOC mappings." 878 REFERENCE "[LISP]" 879 ::= { lisp 4 } 881 lispMapCacheEntry OBJECT-TYPE 882 SYNTAX lispMapCacheEntry 883 MAX-ACCESS not-accessible 884 STATUS current 885 DESCRIPTION 886 "An entry (conceptual row) in the lispMapCacheTable." 887 INDEX { lispMapCacheEidLength 888 lispMapCacheEid 889 lispMapCacheEidMaskLength } 890 ::= { lispMapCacheTable 1 } 892 lispMapCacheEntry ::= SEQUENCE { 893 lispMapCacheEidLength INTEGER, 894 lispMapCacheEid LispAddressType, 895 lispMapCacheEidUpTime TimeTicks, 896 lispMapCacheEidExpiryTime TimeTicks, 897 lispMapCacheEidState INTEGER, 898 lispMapCacheEidAuthoritative TruthValue, 899 lispMapCacheDecapOctets Counter64, 900 lispMapCacheDecapPkts Counter64 901 lispMapCacheEncapOctets Counter64, 902 lispMapCacheEncapPkts Counter64 903 } 905 lispMapCacheEidLength OBJECT-TYPE 906 SYNTAX INTEGER 907 MAX-ACCESS not-accessible 908 STATUS current 909 DESCRIPTION 910 "This object is used to get the length 911 of lispMapCacheEid, the next object." 912 ::= { lispMapCacheEntry 1 } 914 lispMapCacheEid OBJECT-TYPE 915 SYNTAX LispAddressType 916 MAX-ACCESS not-accessible 917 STATUS current 918 DESCRIPTION 919 "The EID prefix in the mapping cache." 920 ::= { lispMapCacheEntry 2 } 922 lispMapCacheEidUpTime OBJECT-TYPE 923 SYNTAX TimeTicks 924 MAX-ACCESS accessible 925 STATUS current 926 DESCRIPTION 927 "The up time of the EID prefix." 928 ::= { lispMapCacheEntry 3 } 930 lispMapCacheEidExpiryTime OBJECT-TYPE 931 SYNTAX TimeTicks 932 MAX-ACCESS accessible 933 STATUS current 934 DESCRIPTION 935 "The time remaining on the EID prefix before 936 the ITR times-out the prefix." 937 ::= { lispMapCacheEntry 4 } 939 lispMapCacheEidState OBJECT-TYPE 940 SYNTAX INTEGER 941 MAX-ACCESS accessible 942 STATUS current 943 DESCRIPTION 944 "This object is used to indicate the activty 945 of this EID prefix. A value of 0 implies the 946 EID prefix is idle. A value of 1 implies the 947 EID prefix is active. 948 ::= { lispMapCacheEntry 5 } 950 lispMapCacheEidAuthoritative OBJECT-TYPE 951 SYNTAX TruthValue 952 MAX-ACCESS accessible 953 STATUS current 954 DESCRIPTION 955 "This object is used to indicate whether the 956 EID prefix was installed by an authoritative 957 map-reply. A value of 0 implies the EID prefix 958 was installed by an authoritative map-reply, 959 and a value of 1, otherwise." 960 ::= { lispMapCacheEntry 6 } 962 lispMapCacheDecapOctets OBJECT-TYPE 963 SYNTAX Counter64 964 MAX-ACCESS accessible 965 STATUS current 966 DESCRIPTION 967 "The number of octets of Lisp packets that were 968 decapsulated by this device and were sourced 969 from a remote host within this EID-prefix." 970 ::= { lispMapCacheEntry 7 } 972 lispMapCacheDecapPackets OBJECT-TYPE 973 SYNTAX Counter64 974 MAX-ACCESS accessible 975 STATUS current 976 DESCRIPTION 977 "The number of Lisp packets that were 978 decapsulated by this device and were sourced 979 from a remote host within this EID-prefix." 980 ::= { lispMapCacheEntry 8 } 982 lispMapCacheEncapOctets OBJECT-TYPE 983 SYNTAX Counter64 984 MAX-ACCESS accessible 985 STATUS current 986 DESCRIPTION 987 "The number of octets of Lisp packets that were 988 encapsulated by this device using the given 989 EID-prefix in the map cache." 990 ::= { lispMapCacheEntry 9 } 992 lispMapCacheEncapPackets OBJECT-TYPE 993 SYNTAX Counter64 994 MAX-ACCESS accessible 995 STATUS current 996 DESCRIPTION 997 "The number of Lisp packets that were encapsulated 998 by this device using the given EID-prefix in the 999 map cache." 1000 ::= { lispMapCacheEntry 10 } 1002 lispMapCacheLocatorTable OBJECT-TYPE 1003 SYNTAX SEQUENCE OF lispMapCacheLocatorEntry 1004 MAX-ACCESS not-accessible 1005 STATUS current 1006 DESCRIPTION 1007 "This table represents the set of locators per 1008 EID prefix contained in the map-cache table of 1009 an ITR." 1010 REFERENCE "[LISP]" 1011 ::= { lisp 5 } 1013 lispMapCacheLocatorEntry OBJECT-TYPE 1014 SYNTAX lispMapCacheLocatorEntry 1015 MAX-ACCESS not-accessible 1016 STATUS current 1017 DESCRIPTION 1018 "An entry (conceptual row) in the lispMapCacheLocatorTable." 1019 INDEX { lispMapCacheLocatorEidLength 1020 lispMapCacheLocatorEid 1021 lispMapCacheLocatorRlocLength 1023 lispMapCacheLocatorRloc } 1024 ::= { lispMapCacheLocatorTable 1 } 1026 lispMapCacheLocatorEntry ::= SEQUENCE { 1027 lispMapCacheLocatorEidLength INTEGER, 1028 lispMapCacheLocatorEid LispAddressType, 1029 lispMapCacheLocatorRlocLength INTEGER, 1030 lispMapCacheLocatorRloc LispAddressType, 1031 lispMapCacheLocatorRlocPriority INTEGER, 1032 lispMapCacheLocatorRlocWeight INTEGER, 1033 lispMapCacheLocatorRlocMPriority INTEGER, 1034 lispMapCacheLocatorRlocMWeight INTEGER, 1035 lispMapCacheLocatorRlocState INTEGER, 1036 lispMapCacheLocatorRlocUpTime TimeTicks, 1037 lispMapCacheLocatorRlocLastPriorityChange TimeTicks, 1038 lispMapCacheLocatorRlocLastWeightChange TimeTicks, 1039 lispMapCacheLocatorRlocLastMPriorityChange TimeTicks, 1040 lispMapCacheLocatorRlocLastMWeightChange TimeTicks, 1041 lispMapCacheLocatorRlocLastStateChange TimeTicks, 1042 lispMapCacheLocatorRlocRtt TimeTicks, 1043 lispMapCacheLocatorRlocDecapOctets Counter64, 1044 lispMapCacheLocatorRlocDecapPackets Counter64 1045 lispMapCacheLocatorRlocEncapOctets Counter64, 1046 lispMapCacheLocatorRlocEncapPackets Counter64 1047 } 1049 lispMapCacheLocatorEidLength OBJECT-TYPE 1050 SYNTAX INTEGER 1051 MAX-ACCESS not-accessible 1052 STATUS current 1053 DESCRIPTION 1054 "This object is used to get the length of 1055 lispMapCacheLocatorEid, the next object." 1056 ::= { lispMapCacheLocatorEntry 1 } 1058 lispMapCacheLocatorEid OBJECT-TYPE 1059 SYNTAX LispAddressType 1060 MAX-ACCESS not-accessible 1061 STATUS current 1062 DESCRIPTION 1063 "The EID prefix of mapping cache mapped to the locator." 1064 ::= { lispMapCacheLocatorEntry 2 } 1066 lispMapCacheLocatorRlocLength OBJECT-TYPE 1067 SYNTAX INTEGER 1068 MAX-ACCESS not-accessible 1069 STATUS current 1070 DESCRIPTION 1071 "This object is used to get the length of 1072 lispMapCacheLocatorRloc, the next object." 1073 ::= { lispMapCacheLocatorEntry 3 } 1075 lispMapCacheLocatorRloc OBJECT-TYPE 1076 SYNTAX LispAddressType 1077 MAX-ACCESS not-accessible 1078 STATUS current 1079 DESCRIPTION 1080 "The locator for the EID prefix in the mapping cache." 1081 ::= { lispMapCacheLocatorEntry 4 } 1083 lispMapCacheLocatorRlocPriority OBJECT-TYPE 1084 SYNTAX INTEGER 1085 MAX-ACCESS accessible 1086 STATUS current 1087 DESCRIPTION 1088 "The unicast priority of the RLOC for this EID prefix." 1089 ::= { lispMapCacheLocatorEntry 5 } 1091 lispMapCacheLocatorRlocWeight OBJECT-TYPE 1092 SYNTAX INTEGER 1093 MAX-ACCESS accessible 1094 STATUS current 1095 DESCRIPTION 1096 "The unicast weight of the RLOC for this EID prefix." 1097 ::= { lispMapCacheLocatorEntry 6 } 1099 lispMapCacheLocatorRlocMPriority OBJECT-TYPE 1100 SYNTAX INTEGER 1101 MAX-ACCESS accessible 1102 STATUS current 1103 DESCRIPTION 1104 "The multicast priority of the RLOC for this EID prefix." 1105 ::= { lispMapCacheLocatorEntry 7 } 1107 lispMapCacheLocatorRlocMWeight OBJECT-TYPE 1108 SYNTAX INTEGER 1109 MAX-ACCESS accessible 1110 STATUS current 1111 DESCRIPTION 1112 "The multicast weight of the RLOC for this EID prefix." 1113 ::= { lispMapCacheLocatorEntry 8 } 1115 lispMapCacheLocatorRlocState OBJECT-TYPE 1116 SYNTAX INTEGER 1117 MAX-ACCESS accessible 1118 STATUS current 1119 DESCRIPTION 1120 "The state of this RLOC as per this device. 1121 0 is for up, 1 is for down ..." 1122 ::= { lispMapCacheLocatorEntry 9 } 1124 lispMapCacheLocatorRlocUpTime OBJECT-TYPE 1125 SYNTAX TimeTicks 1126 MAX-ACCESS accessible 1127 STATUS current 1128 DESCRIPTION 1129 "The up-time of this RLOC." 1130 ::= { lispMapCacheLocatorEntry 10 } 1132 lispMapCacheLocatorRlocLastPriorityChange OBJECT-TYPE 1133 SYNTAX TimeTicks 1134 MAX-ACCESS accessible 1135 STATUS current 1136 DESCRIPTION 1137 "Time since the last change of the unicast 1138 priority of the RLOC for this EID prefix." 1139 ::= { lispMapCacheLocatorEntry 11 } 1141 lispMapCacheLocatorRlocLastWeightChange OBJECT-TYPE 1142 SYNTAX TimeTicks 1143 MAX-ACCESS accessible 1144 STATUS current 1145 DESCRIPTION 1146 "Time since the last change of the unicast weight 1147 of the RLOC for this EID prefix." 1148 ::= { lispMapCacheLocatorEntry 12 } 1150 lispMapCacheLocatorRlocLastMPriorityChange OBJECT-TYPE 1151 SYNTAX TimeTicks 1152 MAX-ACCESS accessible 1153 STATUS current 1154 DESCRIPTION 1155 "Time since the last change of the multicast 1156 priority of the RLOC for this EID prefix." 1157 ::= { lispMapCacheLocatorEntry 13 } 1159 lispMapCacheLocatorRlocLastMWeightChange OBJECT-TYPE 1160 SYNTAX TimeTicks 1161 MAX-ACCESS accessible 1162 STATUS current 1163 DESCRIPTION 1164 "Time since the last change of the multicast 1165 weight of the RLOC for this EID prefix." 1166 ::= { lispMapCacheLocatorEntry 14 } 1168 lispMapCacheLocatorRlocLastStateChange OBJECT-TYPE 1169 SYNTAX TimeTicks 1170 MAX-ACCESS accessible 1171 STATUS current 1172 DESCRIPTION 1173 "Time since the last change of the up/down 1174 state of the RLOC for this EID prefix." 1175 ::= { lispMapCacheLocatorEntry 15 } 1177 lispMapCacheLocatorRlocRtt OBJECT-TYPE 1178 SYNTAX TimeTicks 1179 MAX-ACCESS accessible 1180 STATUS current 1181 DESCRIPTION 1182 "Round trip time of RLOC probe and map-reply 1183 for this RLOC address for this prefix." 1184 ::= { lispMapCacheLocatorEntry 16 } 1186 lispMapCacheLocatorRlocDecapOctets OBJECT-TYPE 1187 SYNTAX Counter64 1188 MAX-ACCESS accessible 1189 STATUS current 1190 DESCRIPTION 1191 "The number of octets of Lisp packets that were 1192 decapsulated by this device and were sourced 1193 from a remote host within this EID-prefix and 1194 were encapsulated for this RLOC." 1195 ::= { lispMapCacheLocatorEntry 17 } 1197 lispMapCacheLocatorRlocDecapPackets OBJECT-TYPE 1198 SYNTAX Counter64 1199 MAX-ACCESS accessible 1200 STATUS current 1201 DESCRIPTION 1202 "The number of octets of Lisp packets that were 1203 decapsulated by this device and were sourced 1204 from a remote host within this EID-prefix and 1205 were encapsulated for this RLOC." 1206 ::= { lispMapCacheLocatorEntry 18 } 1208 lispMapCacheLocatorRlocEncapOctets OBJECT-TYPE 1209 SYNTAX Counter64 1210 MAX-ACCESS accessible 1211 STATUS current 1212 DESCRIPTION 1213 "The number of octets of Lisp packets that matched 1214 this EID-prefix and were encapsulated using this 1215 RLOC address." 1217 ::= { lispMapCacheLocatorEntry 19 } 1219 lispMapCacheLocatorRlocEncapPackets OBJECT-TYPE 1220 SYNTAX Counter64 1221 MAX-ACCESS accessible 1222 STATUS current 1223 DESCRIPTION 1224 "The number of Lisp packets that matched this 1225 EID-prefix and were encapsulated using this 1226 RLOC address." 1227 ::= { lispMapCacheLocatorEntry 20 } 1229 lispSiteTable OBJECT-TYPE 1230 SYNTAX SEQUENCE OF lispSiteEntry 1231 MAX-ACCESS not-accessible 1232 STATUS current 1233 DESCRIPTION 1234 "This table provides the properties of each lisp 1235 site that is served by this device when configured 1236 to be a Map-Server." 1237 REFERENCE "[LISP]" 1238 ::= { lisp 6 } 1240 lispSiteEntry OBJECT-TYPE 1241 SYNTAX lispSiteEntry 1242 MAX-ACCESS not-accessible 1243 STATUS current 1244 DESCRIPTION 1245 "An entry (conceptual row) in the lispSiteTable." 1246 INDEX { lispSiteName 1247 lispSiteEidLength 1248 lispSiteEid } 1249 ::= { lispSiteTable 1 } 1251 lispSiteEntry ::= SEQUENCE { 1252 lispSiteName OCTET STRING, 1253 lispSiteEidLength INTEGER, 1254 lispSiteEid LispAddressType, 1255 lispSiteEidRegisterState TruthValue, 1256 lispSiteEidFirstRegisterTime TimeTicks, 1257 lispSiteEidRegisterSenderLength INTEGER, 1258 lispSiteEidRegisterSender LispAddressType, 1259 lispSiteEidRouteTag Unsigned32, 1260 lispSiteEidAuthenticationErrors Counter64, 1261 lispSiteEidRegisterRlocsMismatch Counter64 1262 } 1263 lispSiteName OBJECT-TYPE 1264 SYNTAX OCTET STRING (SIZE(0..63)) 1265 MAX-ACCESS not-accessible 1266 STATUS current 1267 DESCRIPTION 1268 "Site name used by a Map-Server to distinguish 1269 different lisp sites that are registering with it." 1270 ::= { lispSiteEntry 1 } 1272 lispSiteEidLength OBJECT-TYPE 1273 SYNTAX INTEGER 1274 MAX-ACCESS not-accessible 1275 STATUS current 1276 DESCRIPTION 1277 "This object is used to get the length of 1278 lispSiteEid, the next object." 1279 ::= { lispSiteEntry 2 } 1281 lispSiteEid OBJECT-TYPE 1282 SYNTAX LispAddressType 1283 MAX-ACCESS not-accessible 1284 STATUS current 1285 DESCRIPTION 1286 "The EID prefix belonging to this site." 1287 ::= { lispSiteEntry 3 } 1289 lispSiteEidRegisterState OBJECT-TYPE 1290 SYNTAX TruthValue 1291 MAX-ACCESS accessible 1292 STATUS current 1293 DESCRIPTION 1294 "Indicates the registration status of the given 1295 EID prefix. Value 1 implies registered, value 0 1296 implies not registered." 1297 ::= { lispEntry 4 } 1299 lispSiteEidFirstRegisterTime OBJECT-TYPE 1300 SYNTAX TimeTicks 1301 MAX-ACCESS accessible 1302 STATUS current 1303 DESCRIPTION 1304 "Time since a first valid register message for 1305 the given EID prefix was received by this device." 1306 ::= { lispSiteEntry 5 } 1308 lispSiteEidRegisterSenderLength OBJECT-TYPE 1309 SYNTAX INTEGER 1310 MAX-ACCESS accessible 1311 STATUS current 1312 DESCRIPTION 1313 "This object is used to get the length of 1314 lispSiteEidRegisterSender, the next object." 1315 ::= { lispSiteEntry 6 } 1317 lispSiteEidRegisterSender OBJECT-TYPE 1318 SYNTAX LispAddressType 1319 MAX-ACCESS accessible 1320 STATUS current 1321 DESCRIPTION 1322 "Source address of the last valid register message for 1323 the given EID prefix that was received by this device." 1324 ::= { lispSiteEntry 7 } 1326 lispSiteEidRouteTag OBJECT-TYPE 1327 SYNTAX Unsigned32 1328 MAX-ACCESS accessible 1329 STATUS current 1330 DESCRIPTION 1331 "Value of the routing table tag that contains the 1332 given EID prefix." 1333 ::= { lispSiteEntry 8 } 1335 lispSiteEidAuthenticationErrors OBJECT-TYPE 1336 SYNTAX Counter64 1337 MAX-ACCESS accessible 1338 STATUS current 1339 DESCRIPTION 1340 "Count of total authentication errors of map-registers 1341 received for the given EID prefix." 1342 ::= { lispSiteEntry 9 } 1344 lispSiteEidRegisterRlocsMismatch OBJECT-TYPE 1345 SYNTAX Counter64 1346 MAX-ACCESS accessible 1347 STATUS current 1348 DESCRIPTION 1349 "Count of total map-registers received that had at 1350 least one RLOC that was not in the allowed list of 1351 RLOCs for the given EID prefix." 1352 ::= { lispSiteEntry 10 } 1354 lispSiteLocatorTable OBJECT-TYPE 1355 SYNTAX SEQUENCE OF lispSiteLocatorEntry 1356 MAX-ACCESS not-accessible 1357 STATUS current 1358 DESCRIPTION 1359 "This table provides the properties of all locators 1360 per lisp site that is served by this device when 1361 configured to be a Map-Server." 1362 REFERENCE "[LISP]" 1363 ::= { lisp 7 } 1365 lispSiteLocatorEntry OBJECT-TYPE 1366 SYNTAX lispSiteLocatorEntry 1367 MAX-ACCESS not-accessible 1368 STATUS current 1369 DESCRIPTION 1370 "An entry (conceptual row) in the lispSiteLocatorTable." 1371 INDEX { lispSiteLocatorName 1372 lispSiteLocatorEid 1373 lispSiteLocatorEidMaskLength 1374 lispSiteLocatorRlocLength 1375 lispSiteLocatorRloc 1376 lispSiteLocatorRlocState } 1377 ::= { lispSiteLocatorTable 1 } 1379 lispSiteLocatorEntry ::= SEQUENCE { 1380 lispSiteLocatorName OCTET STRING, 1381 lispSiteLocatorEidLength INTEGER, 1382 lispSiteLocatorEid LispAddressType, 1383 lispSiteLocatorRlocLength INTEGER, 1384 lispSiteLocatorRloc LispAddressType, 1385 lispSiteLocatorRlocState INTEGER, 1386 lispSiteLocatorRlocPriority INTEGER, 1387 lispSiteLocatorRlocWeight INTEGER, 1388 lispSiteLocatorRlocMPriority INTEGER, 1389 lispSiteLocatorRlocMWeight INTEGER, 1390 lispSiteLocatorRlocRegisterState TruthValue, 1391 lispSiteLocatorRlocFirstRegisterTime TimeTicks, 1392 lispSiteLocatorRlocRegisterTimeLast TimeTicks, 1393 lispSiteLocatorRlocRegisterSenderLength INTEGER, 1394 lispSiteLocatorRlocRegisterSender LispAddressType, 1395 lispSiteLocatorRlocProxyReply TruthValue 1396 } 1398 lispSiteLocatorIdentifier OBJECT-TYPE 1399 SYNTAX OCTET STRING (SIZE(0..63)) 1400 MAX-ACCESS not-accessible 1401 STATUS current 1402 DESCRIPTION 1403 "Site name used by a Map-Server to distinguish 1404 different lisp sites that are registering with it." 1405 ::= { lispSiteLocatorEntry 1 } 1407 lispSiteLocatorEidLength OBJECT-TYPE 1408 SYNTAX INTEGER 1409 MAX-ACCESS not-accessible 1410 STATUS current 1411 DESCRIPTION 1412 "This object is used to get the length of 1413 lispSiteLocatorEid, the next object." 1414 ::= { lispSiteLocatorEntry 2 } 1416 lispSiteLocatorEid OBJECT-TYPE 1417 SYNTAX LispAddressType 1418 MAX-ACCESS not-accessible 1419 STATUS current 1420 DESCRIPTION 1421 "The EID prefix belonging to this site." 1422 ::= { lispSiteLocatorEntry 3 } 1424 lispSiteLocatorRlocLength OBJECT-TYPE 1425 SYNTAX INTEGER 1426 MAX-ACCESS not-accessible 1427 STATUS current 1428 DESCRIPTION 1429 "This object is used to get the length of 1430 lispSiteLocatorRloc, the next object." 1431 ::= { lispSiteLocatorEntry 4 } 1433 lispSiteLocatorRloc OBJECT-TYPE 1434 SYNTAX LispAddressType 1435 MAX-ACCESS not-accessible 1436 STATUS current 1437 DESCRIPTION 1438 "The locator of the given EID prefix belonging 1439 to this site." 1440 ::= { lispSiteLocatorEntry 5 } 1442 lispSiteLocatorRlocState OBJECT-TYPE 1443 SYNTAX INTEGER 1444 MAX-ACCESS accessible 1445 STATUS current 1446 DESCRIPTION 1447 "The cached state of this RLOC received in 1448 map-register by the device, in the capacity of 1449 a Map-Server. Value 0 refers to down, value 1 1450 refers to up." 1451 ::= { lispSiteLocatorEntry 6 } 1453 lispSiteLocatorRlocPriority OBJECT-TYPE 1454 SYNTAX INTEGER 1455 MAX-ACCESS accessible 1456 STATUS current 1457 DESCRIPTION 1458 "The unicast priority of the RLOC for this EID prefix." 1459 ::= { lispSiteLocatorEntry 7 } 1461 lispSiteLocatorRlocWeight OBJECT-TYPE 1462 SYNTAX INTEGER 1463 MAX-ACCESS accessible 1464 STATUS current 1465 DESCRIPTION 1466 "The unicast weight of the RLOC for this EID prefix." 1467 ::= { lispSiteLocatorEntry 8 } 1469 lispSiteLocatorRlocMPriority OBJECT-TYPE 1470 SYNTAX INTEGER 1471 MAX-ACCESS accessible 1472 STATUS current 1473 DESCRIPTION 1474 "The multicast priority of the RLOC for this EID prefix." 1475 ::= { lispSiteLocatorEntry 9 } 1477 lispSiteLocatorRlocMWeight OBJECT-TYPE 1478 SYNTAX INTEGER 1479 MAX-ACCESS accessible 1480 STATUS current 1481 DESCRIPTION 1482 "The multicast weight of the RLOC for this EID prefix." 1483 ::= { lispSiteLocatorEntry 10 } 1485 lispSiteLocatorRlocRegisterState OBJECT-TYPE 1486 SYNTAX TruthValue 1487 MAX-ACCESS accessible 1488 STATUS current 1489 DESCRIPTION 1490 "Indicates the registration status of the EID prefix by 1491 this locator. Value 1 implies registered, value 0 1492 implies not registered." 1493 ::= { lispSiteLocatorEntry 11 } 1495 lispSiteLocatorRlocFirstRegisterTime OBJECT-TYPE 1496 SYNTAX TimeTicks 1497 MAX-ACCESS accessible 1498 STATUS current 1499 DESCRIPTION 1500 "Time since a first valid register message for this 1501 EID prefix was received from this locator." 1502 ::= { lispSiteLocatorEntry 12 } 1504 lispSiteLocatorRlocLastRegisterTime OBJECT-TYPE 1505 SYNTAX TimeTicks 1506 MAX-ACCESS accessible 1507 STATUS current 1508 DESCRIPTION 1509 "Time since a last valid register message for this 1510 EID prefix was received from this locator." 1511 ::= { lispSiteLocatorEntry 13 } 1513 lispSiteLocatorRlocRegisterSenderLength OBJECT-TYPE 1514 SYNTAX INTEGER 1515 MAX-ACCESS accessible 1516 STATUS current 1517 DESCRIPTION 1518 "This object is used to get the length of 1519 lispSiteLocatorRlocRegisterSender, the next object." 1520 ::= { lispSiteLocatorEntry 14 } 1522 lispSiteLocatorRlocRegisterSender OBJECT-TYPE 1523 SYNTAX LispAddressType 1524 MAX-ACCESS accessible 1525 STATUS current 1526 DESCRIPTION 1527 "Source address of the last valid register message for 1528 this EID prefix that was received from this locator." 1529 ::= { lispSiteLocatorEntry 15 } 1531 lispSiteLocatorRlocProxyReply OBJECT-TYPE 1532 SYNTAX TruthValue 1533 MAX-ACCESS accessible 1534 STATUS current 1535 DESCRIPTION 1536 "Indicates proxy-replying status of the registering 1537 locator of this EID prefix." 1538 ::= { lispSiteLocatorEntry 16 } 1540 lispMapServersTable OBJECT-TYPE 1541 SYNTAX SEQUENCE OF lispMapServersEntry 1542 MAX-ACCESS not-accessible 1543 STATUS current 1544 DESCRIPTION 1545 "This table provides the properties of the map-servers 1546 with which this device is configured to register." 1547 REFERENCE "[LISP]" 1548 ::= { lisp 8 } 1550 lispMapServersEntry OBJECT-TYPE 1551 SYNTAX lispMapServersEntry 1552 MAX-ACCESS not-accessible 1553 STATUS current 1554 DESCRIPTION 1555 "An entry (conceptual row) in the lispMapServersTable." 1556 INDEX { lispMapServersAddressLength 1557 lispMapServersAddress } 1558 ::= { lispMapServersTable 1 } 1560 lispMapServersEntry ::= SEQUENCE { 1561 lispMapServersAddressLength INTEGER, 1562 lispMapServersAddress LispAddressType, 1563 lispMapServersState INTEGER 1564 } 1566 lispMapServersAddressLength OBJECT-TYPE 1567 SYNTAX INTEGER 1568 MAX-ACCESS not-accessible 1569 STATUS current 1570 DESCRIPTION 1571 "This object is used to get the length of 1572 lispMapServersAddress, the next object." 1573 ::= { lispMapServersEntry 1 } 1575 lispMapServersAddress OBJECT-TYPE 1576 SYNTAX LispAddressType 1577 MAX-ACCESS not-accessible 1578 STATUS current 1579 DESCRIPTION 1580 "Address of Map-Server configured on this device." 1581 ::= { lispMapServersEntry 2 } 1583 lispMapServersState OBJECT-TYPE 1584 SYNTAX TruthValue 1585 MAX-ACCESS accessible 1586 STATUS current 1587 DESCRIPTION 1588 "State of this Map-Server configured on this device. 1589 Value 0 implies that the Map-Server is down, and a 1590 value of 1 implies that the Map-Server is up." 1591 ::= { lispMapServersEntry 3 } 1593 lispMapResolversTable OBJECT-TYPE 1594 SYNTAX SEQUENCE OF lispMapResolversEntry 1595 MAX-ACCESS not-accessible 1596 STATUS current 1597 DESCRIPTION 1598 "This table provides the properties of all map 1599 resolvers that this device is configured to use." 1600 REFERENCE "[LISP]" 1601 ::= { lisp 9 } 1603 lispMapResolversEntry OBJECT-TYPE 1604 SYNTAX lispMapResolversEntry 1605 MAX-ACCESS not-accessible 1606 STATUS current 1607 DESCRIPTION 1608 "An entry (conceptual row) in the lispMapResolversTable." 1609 INDEX { lispMapResolversAddressLength 1610 lispMapResolversAddress } 1611 ::= { lispMapResolversTable 1 } 1613 lispMapResolversEntry ::= SEQUENCE { 1614 lispMapResolversAddressLength INTEGER, 1615 lispMapResolversAddress LispAddressType, 1616 lispMapResolversState INTEGER 1617 } 1619 lispMapResolversAddressLength OBJECT-TYPE 1620 SYNTAX INTEGER 1621 MAX-ACCESS not-accessible 1622 STATUS current 1623 DESCRIPTION 1624 "This object is used to get the length of 1625 lispMapResolversAddress, the next object." 1626 ::= { lispMapResolversEntry 1 } 1628 lispMapResolversAddress OBJECT-TYPE 1629 SYNTAX LispAddressType 1630 MAX-ACCESS not-accessible 1631 STATUS current 1632 DESCRIPTION 1633 "Address of map-resolver configured on this device." 1634 ::= { lispMapResolversEntry 2 } 1636 lispMapResolversState OBJECT-TYPE 1637 SYNTAX TruthValue 1638 MAX-ACCESS accessible 1639 STATUS current 1640 DESCRIPTION 1641 "State of this map-resolver configured on this device. 1642 Value 0 implies that the map-resolver is down, and a 1643 value of 1 implies that this map-resolver is up." 1644 ::= { lispMapResolversEntry 3 } 1646 lispUseProxyEtrTable OBJECT-TYPE 1647 SYNTAX SEQUENCE OF lispUseProxyEtrEntry 1648 MAX-ACCESS not-accessible 1649 STATUS current 1650 DESCRIPTION 1651 "This table provides the properties of all Proxy ETRs 1652 that this device is configured to use." 1653 REFERENCE "[LISP]" 1654 ::= { lisp 10 } 1656 lispUseProxyEtrEntry OBJECT-TYPE 1657 SYNTAX lispUseProxyEtrEntry 1658 MAX-ACCESS not-accessible 1659 STATUS current 1660 DESCRIPTION 1661 "An entry (conceptual row) in the lispUseProxyEtrTable." 1662 INDEX { lispUseProxyEtrAddressLength 1663 lispUseProxyEtrAddress } 1664 ::= { lispUseProxyEtrTable 1 } 1666 lispUseProxyEtrEntry ::= SEQUENCE { 1667 lispUseProxyEtrAddressLength INTEGER, 1668 lispUseProxyEtrAddress LispAddressType, 1669 lispUseProxyEtrState INTEGER 1670 } 1672 lispUseProxyEtrAddressLength OBJECT-TYPE 1673 SYNTAX INTEGER 1674 MAX-ACCESS not-accessible 1675 STATUS current 1676 DESCRIPTION 1677 "This object is used to get the length of 1678 lispUseProxyEtrAddress, the next object." 1679 ::= { lispUseProxyEtrEntry 1 } 1681 lispUseProxyEtrAddress OBJECT-TYPE 1682 SYNTAX LispAddressType 1683 MAX-ACCESS not-accessible 1684 STATUS current 1685 DESCRIPTION 1686 "Address of Proxy ETR configured on this device." 1687 ::= { lispUseProxyEtrEntry 2 } 1689 lispUseProxyEtrState OBJECT-TYPE 1690 SYNTAX TruthValue 1691 MAX-ACCESS accessible 1692 STATUS current 1693 DESCRIPTION 1694 "State of this Proxy ETR configured on this device. 1695 Value 0 implies that this Proxy ETR is down, and a 1696 value of 1 implies that this Proxy ETR is up." 1697 ::= { lispUseProxyEtrEntry 3 } 1699 8. Relationship to Other MIB Modules 1701 8.1. MIB modules required for IMPORTS 1703 The LISP MIB imports the textual-convention AddressFamilyNumbers from 1704 the IANA-ADDRESS-FAMILY-NUMBERS-MIB [IANA]. 1706 9. Security Considerations 1708 There are no management objects defined in this MIB module that have 1709 a MAX-ACCESS clause of read-write and/or read-create. As long as 1710 these MIB modules are implemented correctly, there are no risks that 1711 any management objects of this MIB module can modify device settings 1712 via direct SNMP SET operations. 1714 There are no readable objects in this MIB module (i.e., objects with 1715 a MAX-ACCESS other than not-accessible) that are considered 1716 sensitive. 1718 SNMP versions prior to SNMPv3 did not include adequate security. 1719 Even if the network itself is secure (for example by using IPsec), 1720 there is no control as to who on the secure network is allowed to 1721 access and GET/SET (read/change/create/delete) the objects in this 1722 MIB module. 1724 It is RECOMMENDED that implementers consider the security features as 1725 provided by the SNMPv3 framework (see [RFC3410], section 8), 1726 including full support for the SNMPv3 cryptographic mechanisms (for 1727 authentication and privacy). 1729 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1730 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1731 enable cryptographic security. It is then a customer/operator 1732 responsibility to ensure that the SNMP entity giving access to an 1733 instance of these MIB modules is properly configured to give access 1734 to the objects only to those principals (users) that have legitimate 1735 rights to indeed GET or SET (change/create/delete) them. 1737 10. IANA Considerations 1739 LISP is an experimental protocol and the LISP MIB is an experimental 1740 MIB. No IANA actions are required by this document. 1742 11. References 1744 11.1. Normative References 1746 [INTERWORK] Lewis, D., Meyer, D., Farinacci, D., and V. Fuller, 1747 "Interworking LISP with IPv4 and IPv6", 1748 draft-ietf-lisp-interworking-01.txt (work in progress), 1749 March 2010. 1751 [LCAF] Farinacci, D., Meyer, D., and J. Snijders, "LISP 1752 Canonical Address Format", 1753 draft-farinacci-lisp-lcaf-01.txt (work in progress), 1754 April 2010. 1756 [LISP] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, 1757 "Locator/ID Separation Protocol (LISP)", 1758 draft-ietf-lisp-07.txt (work in progress), April 2010. 1760 [LISP-ALT] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, 1761 "LISP Alternative Topology (LISP-ALT)", 1762 draft-ietf-lisp-alt-04.txt (work in progress), 1763 April 2010. 1765 [LISP-MS] Farinacci, D. and V. Fuller, "LISP Map Server", 1766 draft-ietf-lisp-ms-05.txt (work in progress), 1767 April 2010. 1769 [RFC1035] Mockapetris, P., "Domain names - implementation and 1770 specification", STD 13, RFC 1035, November 1987. 1772 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1773 Requirement Levels", BCP 14, RFC 2119, March 1997. 1775 [RFC2404] Madson, C. and R. Glenn, "The Use of HMAC-SHA-1-96 1776 within ESP and AH", RFC 2404, November 1998. 1778 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1779 Schoenwaelder, Ed., "Structure of Management 1780 Information Version 2 (SMIv2)", STD 58, RFC 2578, 1781 April 1999. 1783 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1784 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 1785 STD 58, RFC 2579, April 1999. 1787 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1788 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1789 April 1999. 1791 [RFC4634] Eastlake, D. and T. Hansen, "US Secure Hash Algorithms 1792 (SHA and HMAC-SHA)", RFC 4634, July 2006. 1794 11.2. Informative References 1796 [IANA] "IANA-ADDRESS-FAMILY-NUMBERS-MIB DEFINITIONS", . 1799 [LISP-MCAST] Farinacci, D., Meyer, D., Zwiebel, J., and S. Venaas, 1800 "LISP for Multicast Environments", 1801 draft-ietf-lisp-multicast-03.txt (work in progress), 1802 April 2010. 1804 [LISP-MN] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, 1805 "LISP Mobile Node Architecture", 1806 draft-meyer-lisp-mn-01.txt (work in progress), 1807 February 2010. 1809 [RFC2784] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. 1810 Traina, "Generic Routing Encapsulation (GRE)", 1811 RFC 2784, March 2000. 1813 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1814 "Introduction and Applicability Statements for 1815 Internet-Standard Management Framework", RFC 3410, 1816 December 2002. 1818 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 1819 Protocol 4 (BGP-4)", RFC 4271, January 2006. 1821 [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, 1822 "Multiprotocol Extensions for BGP-4", RFC 4760, 1823 January 2007. 1825 Appendix A. Change Log 1827 This is the first version of draft-schudel-lisp-mib-00. 1829 Appendix B. Open Issues 1831 Open issues for the LISP MIB include the following: 1833 1. This initial version of the LISP MIB draft does not include LISP 1834 Multicast considerations. Multicast considerations will be added 1835 in the next version of this draft. 1837 Appendix C. Acknowledgments 1839 An initial thank you goes to Dino Farinacci for his inputs and review 1840 comments on the initial versions of this draft. In addition, the 1841 authors would like to gratefully acknowledge many people who have 1842 reviewed and commented on this draft. They include: Darrel Lewis, 1843 Isidor Kouvelas, Jesper Skriver, and Selina Heimlich. 1845 Authors' Addresses 1847 Gregg Schudel 1848 cisco Systems 1849 Tasman Drive 1850 San Jose, CA 95134 1851 USA 1853 EMail: gschudel@cisco.com 1855 Amit Jain 1856 cisco Systems 1857 Tasman Drive 1858 San Jose, CA 95134 1859 USA 1861 EMail: amijain@cisco.com 1863 Victor Moreno 1864 cisco Systems 1865 Tasman Drive 1866 San Jose, CA 95134 1867 USA 1869 EMail: vimoreno@cisco.com