draft-ietf-lisp-mib-03.txt   draft-ietf-lisp-mib-04.txt 
Network Working Group G. Schudel Network Working Group G. Schudel
Internet-Draft A. Jain Internet-Draft A. Jain
Intended status: Experimental V. Moreno Intended status: Experimental V. Moreno
Expires: June 2, 2012 cisco Systems Expires: December 24, 2012 cisco Systems
November 30, 2011 June 22, 2012
LISP MIB LISP MIB
draft-ietf-lisp-mib-03 draft-ietf-lisp-mib-04
Abstract Abstract
This document defines managed objects for the Locator/ID Separation This document defines managed objects for the Locator/ID Separation
Protocol (LISP). These objects provide information useful for Protocol (LISP). These objects provide information useful for
monitoring LISP devices, including basic configuration information, monitoring LISP devices, including basic configuration information,
LISP status, and operational statistics. LISP status, and operational statistics.
Status of This Memo Status of This Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 2, 2012. This Internet-Draft will expire on December 24, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Requirements Notation . . . . . . . . . . . . . . . . . . . . 3 1. Requirements Notation . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. The Internet-Standard Management Framework . . . . . . . . . . 4 3. The Internet-Standard Management Framework . . . . . . . . . . 3
4. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 4 4. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 4
5. LISP MIB Objectives . . . . . . . . . . . . . . . . . . . . . 6 5. LISP MIB Objectives . . . . . . . . . . . . . . . . . . . . . 6
6. Structure of LISP MIB Module . . . . . . . . . . . . . . . . . 7 6. Structure of LISP MIB Module . . . . . . . . . . . . . . . . . 6
6.1. Overview of Defined Notifications . . . . . . . . . . . . 7 6.1. Overview of Defined Notifications . . . . . . . . . . . . 6
6.2. Overview of Defined Tables . . . . . . . . . . . . . . . . 7 6.2. Overview of Defined Tables . . . . . . . . . . . . . . . . 7
7. LISP MIB Definitions . . . . . . . . . . . . . . . . . . . . . 8 7. LISP MIB Definitions . . . . . . . . . . . . . . . . . . . . . 8
8. Relationship to Other MIB Modules . . . . . . . . . . . . . . 51 8. Relationship to Other MIB Modules . . . . . . . . . . . . . . 52
8.1. MIB modules required for IMPORTS . . . . . . . . . . . . . 51 8.1. MIB modules required for IMPORTS . . . . . . . . . . . . . 52
9. Security Considerations . . . . . . . . . . . . . . . . . . . 51 9. Security Considerations . . . . . . . . . . . . . . . . . . . 52
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 52 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 52
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 52 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 53
11.1. Normative References . . . . . . . . . . . . . . . . . . . 52 11.1. Normative References . . . . . . . . . . . . . . . . . . . 53
11.2. Informative References . . . . . . . . . . . . . . . . . . 53 11.2. Informative References . . . . . . . . . . . . . . . . . . 53
Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . . 54 Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . . 54
Appendix B. Acknowledgments . . . . . . . . . . . . . . . . . . . 54 Appendix B. Acknowledgments . . . . . . . . . . . . . . . . . . . 54
1. Requirements Notation 1. Requirements Notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
skipping to change at page 3, line 23 skipping to change at page 3, line 23
This draft describes the Management Information Base (MIB) module for This draft describes the Management Information Base (MIB) module for
use with network management protocols in the Internet community. use with network management protocols in the Internet community.
Specifically, the MIB for managing Locator/ID Separation Protocol Specifically, the MIB for managing Locator/ID Separation Protocol
(LISP) devices is described. (LISP) devices is described.
LISP [LISP] specifies a network-based architecture and mechanisms LISP [LISP] specifies a network-based architecture and mechanisms
that implement a new semantic for IP addressing using two separate that implement a new semantic for IP addressing using two separate
name spaces: Endpoint Identifiers (EIDs), used within sites, and name spaces: Endpoint Identifiers (EIDs), used within sites, and
Routing Locators (RLOCs), used on the transit networks that make up Routing Locators (RLOCs), used on the transit networks that make up
the Internet infrastructure. To achieve this separation, LISP the Internet infrastructure. To achieve this separation, LISP
defines protocol mechanisms for mapping from EIDs to RLOCs. In defines protocol mechanisms for mapping from EIDs to RLOCs.
addition, LISP assumes the existence of a database to store and
globally propagate those mappings [LISP-MS] [LISP-ALT].
From a data plane perspective, LISP traffic is handled exclusively at From a data plane perspective, LISP traffic is handled exclusively at
the network layer by devices performing Ingress Tunnel Router (ITR) the network layer by devices performing Ingress Tunnel Router (ITR)
and Egress Tunnel Router (ETR) LISP functions. Data plane operations and Egress Tunnel Router (ETR) LISP functions. Data plane operations
performed by these devices are described in [LISP]. Additionally, performed by these devices are described in [LISP]. Additionally,
data plane interworking between legacy (Internet) and LISP sites is data plane interworking between legacy (Internet) and LISP sites is
implemented by devices performing Proxy ITR (PITR) and Proxy ETR implemented by devices performing Proxy ITR (PITR) and Proxy ETR
(PETR) functions. The data plane operations of these devices is (PETR) functions. The data plane operations of these devices is
described in [INTERWORK]. described in [INTERWORK].
From a control plane perspective, LISP employs mechanisms related to From a control plane perspective, LISP employs mechanisms related to
creating, maintaining, and resolving mappings from EIDs to RLOCs. creating, maintaining, and resolving mappings from EIDs to RLOCs.
LISP ITRs, ETRs, PITRs, and PETRs perform specific control plane LISP ITRs, ETRs, PITRs, and PETRs perform specific control plane
functions, and these control plane operations are described in functions, and these control plane operations are described in
[LISP]. Additionally, LISP infrastructure devices supporting LISP [LISP]. Additionally, LISP infrastructure devices supporting LISP
control plane functionality include Map-Servers and Map-Resolvers, control plane functionality include Map-Servers and Map-Resolvers,
and the control plane operations of these devices are described in and the control plane operations of these devices are described in
[LISP-MS]. Finally, while not specifically required, this document [LISP-MS]. Finally, while not specifically required, this document
assumes that a LISP+ALT database mapping infrastructure exists as assumes the existence of a database to store and propagate those
part of the LISP control plane. The control plane operations of the mappings globally.
ALT are described in [LISP-ALT]. Note that this MIB does not provide
support for the ALT since ALT statistics may be obtained through
existing BGP and tunnel MIBs.
3. The Internet-Standard Management Framework 3. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
skipping to change at page 4, line 27 skipping to change at page 4, line 18
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
4. Definition of Terms 4. Definition of Terms
Endpoint ID (EID): a 32-bit (for IPv4) or 128-bit (for IPv6) value Endpoint ID (EID): a 32-bit (for IPv4) or 128-bit (for IPv6) value
used in the source and destination address fields of the first used in the source and destination address fields of the first
(inner-most) IP header of a LISP packet. A source EID is (inner-most) IP header of a LISP packet. A source EID is
allocated to a host from an EID-prefix block associated with the allocated to a host from an EID-prefix block associated with the
site where the host is located. A host determines a destination site where the host is located. A host determines a destination
EID in the same way that it determines a destination address address in the same way that it determines a destination address
today, for example through a DNS lookup or SIP exchange. today, for example through a DNS lookup or SIP exchange.
Routing Locator (RLOC): a 32-bit (for IPv4) or 128-bit (for IPv6) Routing Locator (RLOC): a 32-bit (for IPv4) or 128-bit (for IPv6)
value used in the source and destination address fields of the value used in the source and destination address fields of the
second (outer-most) IP header of a LISP packet. RLOC addresses second (outer-most) IP header of a LISP packet. RLOC addresses
are allocated to an egress tunnel router (ETR) and numbered from are allocated to an egress tunnel router (ETR) and numbered from
topologically-aggregatable blocks assigned to a site at each point topologically-aggregatable blocks assigned to a site at each point
to which it attaches to the global Internet. to which it attaches to the global Internet.
EID-to-RLOC Map-Cache: a short-lived, on-demand table maintained EID-to-RLOC Map-Cache: a short-lived, on-demand table maintained
skipping to change at page 5, line 24 skipping to change at page 5, line 15
Internet on the other side. Internet on the other side.
Egress Tunnel Router (ETR): a router that accepts an IP packet where Egress Tunnel Router (ETR): a router that accepts an IP packet where
the destination address in the "outer" IP header is one of its own the destination address in the "outer" IP header is one of its own
RLOCs, strips the "outer" header, and forwards the packet based on RLOCs, strips the "outer" header, and forwards the packet based on
the next IP header found. That is, in general an ETR receives the next IP header found. That is, in general an ETR receives
LISP-encapsulated IP packets from the Internet on one side and LISP-encapsulated IP packets from the Internet on one side and
sends decapsulated IP packets toward site end-systems on the other sends decapsulated IP packets toward site end-systems on the other
side. side.
xTR: is a general reference to an ITR or ETR when direction of data xTR: a term of general reference to an ITR or ETR when direction of
flow is not part of the context description. xTR refers to the data flow is not part of the context description. xTR refers to
router that is the tunnel endpoint and performs both ITR and ETR the router that is the tunnel endpoint and performs both ITR and
functionality. For example, "An xTR can be located at the ETR functionality. For example, "An xTR can be located at the
Customer Edge (CE) router", meaning both ITR and ETR functionality Customer Edge (CE) router," meaning both ITR and ETR functionality
is activated at the CE router. is activated at the CE router.
Proxy ITR (PITR): a router that acts like an ITR but does so on Proxy ITR (PITR): a router that acts like an ITR but does so on
behalf of non-LISP sites which send packets to destinations at behalf of non-LISP sites which send packets to destinations at
LISP sites. The PITR, also known as a PTR, is defined and LISP sites. The PITR, also known as a PTR, is defined and
described in [INTERWORK]. described in [INTERWORK].
Proxy ETR (PETR): a router that acts like an ETR but does so on Proxy ETR (PETR): a router that acts like an ETR but does so on
behalf of LISP sites which send packets to destinations at non- behalf of LISP sites which send packets to destinations at non-
LISP sites. The PETR is defined and described in [INTERWORK]. LISP sites. The PETR is defined and described in [INTERWORK].
LISP Site: is a set of routers in an edge network that are under a LISP Site: a set of routers in an edge network that are under a
single technical administration. LISP routers which reside in the single technical administration. LISP routers which reside in the
edge network are the demarcation points to separate the edge edge network are the demarcation points to separate the edge
network from the core network. network from the core network.
Map-Server: a LISP network infrastructure component which learns Map-Server: a LISP network infrastructure component which learns
EID-to-RLOC mapping entries from an authoritative source such as EID-to-RLOC mapping entries from an authoritative source such as
an ETR though static configuration, or another out-of-band an ETR though static configuration, or another out-of-band
mechanism. A Map-Server advertises these mappings into the mechanism. A Map-Server advertises these mappings into the
distributed mapping database such as that described in [LISP-ALT]. distributed mapping database.
Map-Resolver: a LISP network infrastructure component which accepts Map-Resolver: a LISP network infrastructure component which accepts
LISP Encapsulated Map-Requests, typically from an ITR, and quickly LISP Encapsulated Map-Requests, typically from an ITR, and quickly
determines whether or not the destination IP address is part of determines whether or not the destination IP address is part of
the EID namespace. If it is, the Map-Resolver finds the the EID namespace. If it is, the Map-Resolver finds the
appropriate EID-to-RLOC mapping by consulting the distributed appropriate EID-to-RLOC mapping by consulting the distributed
mapping database system such as that described in [LISP-ALT]. If mapping database. If it is not, a Negative Map-Reply is
it is not, a Negative Map-Reply is immediately returned. immediately returned.
Map-Request: a LISP Map-Request message type sent by an ITR or PITR
to a Map-Resolver when it needs a mapping for an EID, wants to
test an RLOC for reachability, or wants to refresh a mapping
before TTL expiration.
Map-Reply: a LISP Map-Reply message type returned in response to a Map-Reply: a LISP Map-Reply message type returned in response to a
Map-Request for a destination EID that exists in the mapping Map-Request for a destination EID that exists in the mapping
database and contains the locator-set and associated policy for database and contains the locator-set and associated policy for
the queried EID. Information returned in a Map-Reply is stored in the queried EID. Information returned in a Map-Reply is stored in
the EID-to-RLOC Map-Cache. the EID-to-RLOC Map-Cache.
Negative Map-Reply: a LISP Map-Reply message type that contains an Negative Map-Reply: a LISP Map-Reply message type that contains an
empty locator-set. Returned in response to a Map-Request if the empty locator-set. Returned in response to a Map-Request if the
destination EID does not exist in the mapping database. destination EID does not exist in the mapping database.
Typically, this means that the "EID" being requested is an IP Typically, this means that the "EID" being requested is an IP
address connected to a non-LISP site. Information returned in a address connected to a non-LISP site. Information returned in a
Negative Map-Reply is stored in the EID-to-RLOC Map-Cache. Negative Map-Reply is stored in the EID-to-RLOC Map-Cache.
LISP+ALT: a static network built using Border Gateway Protocol (BGP,
[RFC4271]), BGP multi-protocol extension [RFC4760], and Generic
Routing Encapsulation (GRE, [RFC2784]) to construct an overlay
network of devices (ALT Routers) which operate on EID-prefixes and
use EIDs as forwarding destinations. This LISP+ALT network may,
but is not required to be, used by LISP to find EID-to-RLOC
mappings. LISP+ALT is described in [LISP-ALT].
5. LISP MIB Objectives 5. LISP MIB Objectives
The objectives for defining this LISP MIB module are as follows: The objectives for defining this LISP MIB module are as follows:
o Provide a means for obtaining a list of enabled LISP features and o Provide a means for obtaining a list of enabled LISP features and
the current status of configuration attributes related to those the current status of configuration attributes related to those
features. As an example, LISP capabilities which could be enabled features. As an example, LISP capabilities which could be enabled
include ITR, ETR, PITR, PETR, MS or MR support for IPv4 or IPv6 include ITR, ETR, PITR, PETR, MS or MR support for IPv4 or IPv6
address families. Other examples include, indicating whether address families. Other examples include, indicating whether
rloc-probing is enabled, and indicating the configured map-cache rloc-probing is enabled, and indicating the configured map-cache
skipping to change at page 7, line 17 skipping to change at page 7, line 7
and rate of map-requests received and sent. and rate of map-requests received and sent.
6. Structure of LISP MIB Module 6. Structure of LISP MIB Module
6.1. Overview of Defined Notifications 6.1. Overview of Defined Notifications
No LISP MIB notifications are defined. No LISP MIB notifications are defined.
6.2. Overview of Defined Tables 6.2. Overview of Defined Tables
The LISP MIB module is composed of ten tables of objects, as follows: The LISP MIB module is composed of the following tables of objects:
lispFeatures - This table provides information representing the lispFeatures - This table provides information representing the
various lisp features that can be enabled on LISP devices. various lisp features that can be enabled on LISP devices.
lispMappingDatabase - This table represents the EID-to-RLOC database lispMappingDatabase - This table represents the EID-to-RLOC database
that contains the EID-prefix to RLOC mappings configured on an that contains the EID-prefix to RLOC mappings configured on an
ETR. In general, this table would be representative of all such ETR. In general, this table would be representative of all such
mappings for a given site that this device belongs to. mappings for a given site that this device belongs to.
lispMappingDatabaseLocator - This table represents the set of lispMappingDatabaseLocator - This table represents the set of
skipping to change at page 8, line 28 skipping to change at page 8, line 19
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
mib-2, Unsigned32, Counter64, mib-2, Unsigned32, Counter64,
Integer32, TimeTicks FROM SNMPv2-SMI -- [RFC2578] Integer32, TimeTicks FROM SNMPv2-SMI -- [RFC2578]
TruthValue, TEXTUAL-CONVENTION FROM SNMPv2-TC -- [RFC2579] TruthValue, TEXTUAL-CONVENTION FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580] MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580]
AddressFamilyNumbers AddressFamilyNumbers
FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB; -- [IANA] FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB; -- [IANA]
lispMIB MODULE-IDENTITY lispMIB MODULE-IDENTITY
LAST-UPDATED "201111300000Z" -- 30 November 2011 LAST-UPDATED "201206200000Z" -- 20 June 2012
ORGANIZATION ORGANIZATION
"IETF Locator/ID Separation Protocol (LISP) Working Group" "IETF Locator/ID Separation Protocol (LISP) Working Group"
CONTACT-INFO CONTACT-INFO
"Email: lisp@ietf.org "Email: lisp@ietf.org
WG charter: WG charter:
http://www.ietf.org/html.charters/lisp-charter.html" http://www.ietf.org/html.charters/lisp-charter.html"
DESCRIPTION DESCRIPTION
"The mib module for management of LISP routers. "Locator/ID Separation Protocol (LISP) MIB Textual
Conventions module. The LISP MIB is intended for
management of LISP routers.
Copyright (C) The IETF Trust (2011)." Copyright (C) The IETF Trust (2012)."
REVISION "201111300000Z" -- 30 November 2011 REVISION "201206200000Z" -- 20 June 2012
DESCRIPTION "Initial Revision" DESCRIPTION "Initial version of the IETF LISP-MIB module"
::= { mib-x xxx } ::= { mib-x xxx }
-- --
-- Textual Conventions -- Textual Conventions
-- --
LispAddressType ::= TEXTUAL-CONVENTION lispAddressType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"LISP architecture can be applied to a wide variety of "LISP architecture can be applied to a wide variety of
address-families. This textual-convention is a address-families. This textual-convention is a
generalization for representing addresses that belong generalization for representing addresses that belong
to those address-families. For convenience, this to those address-families. For convenience, this
document refers to any such address as a lisp address. document refers to any such address as a lisp address.
LispAddressType textual-convention consists of lispAddressType textual-convention consists of
the following four-tuple: the following four-tuple:
1. IANA Address Family Number: A field of length 1. IANA Address Family Number: A field of length
2-octets, whose value is of the form following the 2-octets, whose value is of the form following the
assigned AddressFamilyNumbers textual-convention assigned AddressFamilyNumbers textual-convention
described in [IANA]. The enumerations are listed described in [IANA]. The enumerations are listed
in [IANA]. Note that this list of address family in [IANA]. Note that this list of address family
numbers is maintained by IANA. numbers is maintained by IANA.
2. Length of LISP address: A field of length 1-octet, 2. Length of LISP address: A field of length 1-octet,
whose value indicates the octet-length of the next whose value indicates the octet-length of the next
(third) field of this LispAddressType four-tuple. (third) field of this LispAddressType four-tuple.
skipping to change at page 9, line 36 skipping to change at page 9, line 29
Number 16387, then the first octet of this field Number 16387, then the first octet of this field
indicates the LCAF type, and the rest of this field indicates the LCAF type, and the rest of this field
is same as the encoding format of the LISP Canonical is same as the encoding format of the LISP Canonical
Address after the length field, as defined in [LCAF]. Address after the length field, as defined in [LCAF].
4. Mask-length of address: A variable-length field 4. Mask-length of address: A variable-length field
comprised of the remaining octets of this comprised of the remaining octets of this
LispAddressType four-tuple, whose value is the LispAddressType four-tuple, whose value is the
mask-length to be applied to the lisp address mask-length to be applied to the lisp address
specified in the previous (third) field. specified in the previous (third) field.
To illustrate the use of this object, consider the To illustrate the use of this object, consider the LISP MIB
LISP MIB Object below entitled lispMapCacheEntry. Object below entitled lispMapCacheEntry. This object begins
This object begins with the following entities: with the following entities:
lispMapCacheEntry ::= SEQUENCE { lispMapCacheEntry ::= SEQUENCE {
lispMapCacheEidLength INTEGER, lispMapCacheEidLength INTEGER,
lispMapCacheEid LispAddressType, lispMapCacheEid LispAddressType,
... [skip] ... ... [skip] ...
Example 1: Suppose that the IPv4 EID prefix stored is Example 1: Suppose that the IPv4 EID prefix stored is
10.10.10.0/24. In this case, the values within 10.10.10.0/24. In this case, the values within
lispMapCacheEntry would be: lispMapCacheEntry would be:
skipping to change at page 19, line 27 skipping to change at page 19, line 21
lispMappingDatabaseLocatorRlocEncapPackets Counter64 lispMappingDatabaseLocatorRlocEncapPackets Counter64
} }
lispMappingDatabaseLocatorRlocLength OBJECT-TYPE lispMappingDatabaseLocatorRlocLength OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to get the octet-length of "This object is used to get the octet-length of
lispMappingDatabaseLocatorRloc, the next object." lispMappingDatabaseLocatorRloc, the next object."
::= { lispMappingDatabaseLocatorEntry 3 } ::= { lispMappingDatabaseLocatorEntry 1 }
lispMappingDatabaseLocatorRloc OBJECT-TYPE lispMappingDatabaseLocatorRloc OBJECT-TYPE
SYNTAX LispAddressType SYNTAX LispAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is a locator for the given EID prefix "This object is a locator for the given EID prefix
in the mapping database." in the mapping database."
::= { lispMappingDatabaseLocatorEntry 4 } ::= { lispMappingDatabaseLocatorEntry 2 }
lispMappingDatabaseLocatorRlocPriority OBJECT-TYPE lispMappingDatabaseLocatorRlocPriority OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The unicast priority of the RLOC." "The unicast priority of the RLOC."
::= { lispMappingDatabaseLocatorEntry 5 } ::= { lispMappingDatabaseLocatorEntry 3 }
lispMappingDatabaseLocatorRlocWeight OBJECT-TYPE lispMappingDatabaseLocatorRlocWeight OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The unicast weight of the RLOC." "The unicast weight of the RLOC."
::= { lispMappingDatabaseLocatorEntry 6 } ::= { lispMappingDatabaseLocatorEntry 4 }
lispMappingDatabaseLocatorRlocMPriority OBJECT-TYPE lispMappingDatabaseLocatorRlocMPriority OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The multicast priority of the RLOC." "The multicast priority of the RLOC."
::= { lispMappingDatabaseLocatorEntry 7 } ::= { lispMappingDatabaseLocatorEntry 5 }
lispMappingDatabaseLocatorRlocMWeight OBJECT-TYPE lispMappingDatabaseLocatorRlocMWeight OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The multicast weight of the RLOC." "The multicast weight of the RLOC."
::= { lispMappingDatabaseLocatorEntry 8 } ::= { lispMappingDatabaseLocatorEntry 6 }
lispMappingDatabaseLocatorRlocState OBJECT-TYPE lispMappingDatabaseLocatorRlocState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
down (0), down (0),
up (1), up (1),
unreachable (2) unreachable (2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The state of this RLOC as per this device. "The state of this RLOC as per this device.
(0 = RLOC is down; 1 = RLOC is up; (0 = RLOC is down; 1 = RLOC is up;
2 = RLOC is unreachable)." 2 = RLOC is unreachable)."
::= { lispMappingDatabaseLocatorEntry 9 } ::= { lispMappingDatabaseLocatorEntry 7 }
lispMappingDatabaseLocatorRlocLocal OBJECT-TYPE lispMappingDatabaseLocatorRlocLocal OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
sitelocal (0), sitelocal (0),
siteself (1) siteself (1)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether the RLOC is local to this "Indicates whether the RLOC is local to this
device (or remote, meaning local to another device (or remote, meaning local to another
device in the same lisp site). (0 = RLOC is device in the same lisp site). (0 = RLOC is
an address on another device; 1 = RLOC is an an address on another device; 1 = RLOC is an
address on this device)." address on this device)."
::= { lispMappingDatabaseLocatorEntry 10 } ::= { lispMappingDatabaseLocatorEntry 8 }
lispMappingDatabaseLocatorRlocDecapOctets OBJECT-TYPE lispMappingDatabaseLocatorRlocDecapOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets of Lisp packets that were "The number of octets of Lisp packets that were
addressed to this RLOC of the EID-prefix and addressed to this RLOC of the EID-prefix and
were decapsulated." were decapsulated."
::= { lispMappingDatabaseLocatorEntry 11 } ::= { lispMappingDatabaseLocatorEntry 9 }
lispMappingDatabaseLocatorRlocDecapPackets OBJECT-TYPE lispMappingDatabaseLocatorRlocDecapPackets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Lisp packets that were addressed "The number of Lisp packets that were addressed
to this RLOC of the EID-prefix and were to this RLOC of the EID-prefix and were
decapsulated." decapsulated."
::= { lispMappingDatabaseLocatorEntry 12 } ::= { lispMappingDatabaseLocatorEntry 10 }
lispMappingDatabaseLocatorRlocEncapOctets OBJECT-TYPE lispMappingDatabaseLocatorRlocEncapOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets of Lisp packets that were "The number of octets of Lisp packets that were
encapsulated by this device using this RLOC encapsulated by this device using this RLOC
address as the source, and that were sourced address as the source, and that were sourced
by an address of this EID-prefix." by an address of this EID-prefix."
::= { lispMappingDatabaseLocatorEntry 13 } ::= { lispMappingDatabaseLocatorEntry 11 }
lispMappingDatabaseLocatorRlocEncapPackets OBJECT-TYPE lispMappingDatabaseLocatorRlocEncapPackets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Lisp packets that were "The number of Lisp packets that were
encapsulated by this device using this RLOC encapsulated by this device using this RLOC
address as the source, and that were sourced address as the source, and that were sourced
by an address of this EID-prefix." by an address of this EID-prefix."
::= { lispMappingDatabaseLocatorEntry 14 } ::= { lispMappingDatabaseLocatorEntry 12 }
lispMapCacheTable OBJECT-TYPE lispMapCacheTable OBJECT-TYPE
SYNTAX SEQUENCE OF LispMapCacheEntry SYNTAX SEQUENCE OF LispMapCacheEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table represents the short-lived, on-demand "This table represents the short-lived, on-demand
table on an ITR that stores, tracks, and is table on an ITR that stores, tracks, and is
responsible for timing-out and otherwise responsible for timing-out and otherwise
validating EID-to-RLOC mappings." validating EID-to-RLOC mappings."
skipping to change at page 25, line 35 skipping to change at page 25, line 31
lispMapCacheLocatorRlocEncapPackets Counter64 lispMapCacheLocatorRlocEncapPackets Counter64
} }
lispMapCacheLocatorRlocLength OBJECT-TYPE lispMapCacheLocatorRlocLength OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to get the octet-length of "This object is used to get the octet-length of
lispMapCacheLocatorRloc, the next object." lispMapCacheLocatorRloc, the next object."
::= { lispMapCacheLocatorEntry 3 } ::= { lispMapCacheLocatorEntry 1 }
lispMapCacheLocatorRloc OBJECT-TYPE lispMapCacheLocatorRloc OBJECT-TYPE
SYNTAX LispAddressType SYNTAX LispAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The locator for the EID prefix in the mapping cache." "The locator for the EID prefix in the mapping cache."
::= { lispMapCacheLocatorEntry 4 } ::= { lispMapCacheLocatorEntry 2 }
lispMapCacheLocatorRlocPriority OBJECT-TYPE lispMapCacheLocatorRlocPriority OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The unicast priority of the RLOC for this EID prefix "The unicast priority of the RLOC for this EID prefix
(0-255) lower more preferred. " (0-255) lower more preferred. "
::= { lispMapCacheLocatorEntry 3 }
::= { lispMapCacheLocatorEntry 5 }
lispMapCacheLocatorRlocWeight OBJECT-TYPE lispMapCacheLocatorRlocWeight OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The unicast weight of the RLOC for this EID prefix "The unicast weight of the RLOC for this EID prefix
(0 - 100) percentage. " (0 - 100) percentage. "
::= { lispMapCacheLocatorEntry 6 } ::= { lispMapCacheLocatorEntry 4 }
lispMapCacheLocatorRlocMPriority OBJECT-TYPE lispMapCacheLocatorRlocMPriority OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The multicast priority of the RLOC for this EID prefix." "The multicast priority of the RLOC for this EID prefix."
::= { lispMapCacheLocatorEntry 7 } ::= { lispMapCacheLocatorEntry 5 }
lispMapCacheLocatorRlocMWeight OBJECT-TYPE lispMapCacheLocatorRlocMWeight OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The multicast weight of the RLOC for this EID prefix." "The multicast weight of the RLOC for this EID prefix."
::= { lispMapCacheLocatorEntry 8 } ::= { lispMapCacheLocatorEntry 6 }
lispMapCacheLocatorRlocState OBJECT-TYPE lispMapCacheLocatorRlocState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
down (0), down (0),
up (1) up (1)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The state of this RLOC as per this device "The state of this RLOC as per this device
(0 = RLOC is down; 1 = RLOC is up)." (0 = RLOC is down; 1 = RLOC is up)."
::= { lispMapCacheLocatorEntry 9 } ::= { lispMapCacheLocatorEntry 7 }
lispMapCacheLocatorRlocUpTime OBJECT-TYPE lispMapCacheLocatorRlocUpTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The up-time of this RLOC." "The up-time of this RLOC."
::= { lispMapCacheLocatorEntry 10 } ::= { lispMapCacheLocatorEntry 8 }
lispMapCacheLocatorRlocLastPriorityChange OBJECT-TYPE lispMapCacheLocatorRlocLastPriorityChange OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time since the last change of the unicast priority "Time since the last change of the unicast priority
of the RLOC for this EID prefix." of the RLOC for this EID prefix."
::= { lispMapCacheLocatorEntry 11 } ::= { lispMapCacheLocatorEntry 9 }
lispMapCacheLocatorRlocLastWeightChange OBJECT-TYPE lispMapCacheLocatorRlocLastWeightChange OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time since the last change of the unicast weight of "Time since the last change of the unicast weight of
the RLOC for this EID prefix." the RLOC for this EID prefix."
::= { lispMapCacheLocatorEntry 12 } ::= { lispMapCacheLocatorEntry 10 }
lispMapCacheLocatorRlocLastMPriorityChange OBJECT-TYPE lispMapCacheLocatorRlocLastMPriorityChange OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time since the last change of the multicast priority "Time since the last change of the multicast priority
of the RLOC for this EID prefix." of the RLOC for this EID prefix."
::= { lispMapCacheLocatorEntry 13 } ::= { lispMapCacheLocatorEntry 11 }
lispMapCacheLocatorRlocLastMWeightChange OBJECT-TYPE lispMapCacheLocatorRlocLastMWeightChange OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time since the last change of the multicast weight "Time since the last change of the multicast weight
of the RLOC for this EID prefix." of the RLOC for this EID prefix."
::= { lispMapCacheLocatorEntry 14 } ::= { lispMapCacheLocatorEntry 12 }
lispMapCacheLocatorRlocLastStateChange OBJECT-TYPE lispMapCacheLocatorRlocLastStateChange OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time since the last change of the up/down state of "Time since the last change of the up/down state of
the RLOC for this EID prefix." the RLOC for this EID prefix."
::= { lispMapCacheLocatorEntry 15 } ::= { lispMapCacheLocatorEntry 13 }
lispMapCacheLocatorRlocRtt OBJECT-TYPE lispMapCacheLocatorRlocRtt OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Round trip time of RLOC probe and map-reply for "Round trip time of RLOC probe and map-reply for
this RLOC address for this prefix." this RLOC address for this prefix."
::= { lispMapCacheLocatorEntry 16 } ::= { lispMapCacheLocatorEntry 14 }
lispMapCacheLocatorRlocDecapOctets OBJECT-TYPE lispMapCacheLocatorRlocDecapOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets of Lisp packets that were "The number of octets of Lisp packets that were
decapsulated by this device and were sourced decapsulated by this device and were sourced
from a remote host within this EID-prefix and from a remote host within this EID-prefix and
were encapsulated for this RLOC." were encapsulated for this RLOC."
::= { lispMapCacheLocatorEntry 17 } ::= { lispMapCacheLocatorEntry 15 }
lispMapCacheLocatorRlocDecapPackets OBJECT-TYPE lispMapCacheLocatorRlocDecapPackets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Lisp packets that were decapsulated "The number of Lisp packets that were decapsulated
by this device and were sourced from a remote host by this device and were sourced from a remote host
within this EID-prefix and were encapsulated for within this EID-prefix and were encapsulated for
this RLOC." this RLOC."
::= { lispMapCacheLocatorEntry 18 } ::= { lispMapCacheLocatorEntry 16 }
lispMapCacheLocatorRlocEncapOctets OBJECT-TYPE lispMapCacheLocatorRlocEncapOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets of Lisp packets that matched "The number of octets of Lisp packets that matched
this EID-prefix and were encapsulated using this this EID-prefix and were encapsulated using this
RLOC address." RLOC address."
::= { lispMapCacheLocatorEntry 19 } ::= { lispMapCacheLocatorEntry 17 }
lispMapCacheLocatorRlocEncapPackets OBJECT-TYPE lispMapCacheLocatorRlocEncapPackets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Lisp packets that matched this EID "The number of Lisp packets that matched this EID
prefix and were encapsulated using this RLOC address." prefix and were encapsulated using this RLOC address."
::= { lispMapCacheLocatorEntry 20 } ::= { lispMapCacheLocatorEntry 18 }
lispEidRegistrationTable OBJECT-TYPE lispEidRegistrationTable OBJECT-TYPE
SYNTAX SEQUENCE OF LispEidRegistrationEntry SYNTAX SEQUENCE OF LispEidRegistrationEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides the properties of each lisp EID "This table provides the properties of each lisp EID
prefix that is registered with this device when prefix that is registered with this device when
configured to be a Map-Server." configured to be a Map-Server."
REFERENCE "[LISP]" REFERENCE "[LISP]"
skipping to change at page 31, line 4 skipping to change at page 30, line 47
the given EID prefix was received by this device." the given EID prefix was received by this device."
::= { lispEidRegistrationEntry 6 } ::= { lispEidRegistrationEntry 6 }
lispEidRegistrationLastRegisterTime OBJECT-TYPE lispEidRegistrationLastRegisterTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time since the last valid register message for "Time since the last valid register message for
the given EID prefix was received by this device." the given EID prefix was received by this device."
::= { lispEidRegistrationEntry 7 }
::= { lispEidRegistrationEntry 6 }
lispEidRegistrationLastRegisterSenderLength OBJECT-TYPE lispEidRegistrationLastRegisterSenderLength OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to get the octet-length of "This object is used to get the octet-length of
lispEidRegistrationLastRegisterSender, the next object." lispEidRegistrationLastRegisterSender, the next object."
::= { lispEidRegistrationEntry 7 } ::= { lispEidRegistrationEntry 8 }
lispEidRegistrationLastRegisterSender OBJECT-TYPE lispEidRegistrationLastRegisterSender OBJECT-TYPE
SYNTAX LispAddressType SYNTAX LispAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Source address of the last valid register message "Source address of the last valid register message
for the given EID prefix that was received by for the given EID prefix that was received by
this device." this device."
::= { lispEidRegistrationEntry 8 } ::= { lispEidRegistrationEntry 9 }
lispEidRegistrationRouteTag OBJECT-TYPE lispEidRegistrationRouteTag OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Value of the routing table tag assigned to the "Value of the routing table tag assigned to the
given EID prefix." given EID prefix."
::= { lispEidRegistrationEntry 9 } ::= { lispEidRegistrationEntry 10 }
lispEidRegistrationAuthenticationErrors OBJECT-TYPE lispEidRegistrationAuthenticationErrors OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of total authentication errors of "Count of total authentication errors of
map-registers received for the given EID map-registers received for the given EID
prefix." prefix."
::= { lispEidRegistrationEntry 10 } ::= { lispEidRegistrationEntry 11 }
lispEidRegistrationRlocsMismatch OBJECT-TYPE lispEidRegistrationRlocsMismatch OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of total map-registers received that had at "Count of total map-registers received that had at
least one RLOC that was not in the allowed list of least one RLOC that was not in the allowed list of
RLOCs for the given EID prefix." RLOCs for the given EID prefix."
::= { lispEidRegistrationEntry 12 }
::= { lispEidRegistrationEntry 11 }
lispEidRegistrationEtrTable OBJECT-TYPE lispEidRegistrationEtrTable OBJECT-TYPE
SYNTAX SEQUENCE OF LispEidRegistrationEtrEntry SYNTAX SEQUENCE OF LispEidRegistrationEtrEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides the properties of ETRs that register "This table provides the properties of ETRs that register
the given EID prefix with this device when configured to the given EID prefix with this device when configured to
be a Map-Server." be a Map-Server."
REFERENCE "[LISP]" REFERENCE "[LISP]"
::= { lisp 6 } ::= { lisp 7 }
lispEidRegistrationEtrEntry OBJECT-TYPE lispEidRegistrationEtrEntry OBJECT-TYPE
SYNTAX LispEidRegistrationEtrEntry SYNTAX LispEidRegistrationEtrEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (conceptual row) in the lispEidRegistrationTable." "An entry (conceptual row) in the lispEidRegistrationTable."
INDEX { lispEidRegistrationEidLength, INDEX { lispEidRegistrationEidLength,
lispEidRegistrationEid, lispEidRegistrationEid,
lispEidRegistrationEtrSenderLength, lispEidRegistrationEtrSenderLength,
skipping to change at page 32, line 46 skipping to change at page 32, line 41
lispEidRegistrationEtrWantsMapNotify TruthValue lispEidRegistrationEtrWantsMapNotify TruthValue
} }
lispEidRegistrationEtrSenderLength OBJECT-TYPE lispEidRegistrationEtrSenderLength OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to get the octet-length of "This object is used to get the octet-length of
lispEidRegistrationEtrSender, the next object." lispEidRegistrationEtrSender, the next object."
::= { lispEidRegistrationEtrEntry 6 } ::= { lispEidRegistrationEtrEntry 1 }
lispEidRegistrationEtrSender OBJECT-TYPE lispEidRegistrationEtrSender OBJECT-TYPE
SYNTAX LispAddressType SYNTAX LispAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Source address of the ETR that is sending valid register "Source address of the ETR that is sending valid register
messages for this EID prefix to this device." messages for this EID prefix to this device."
::= { lispEidRegistrationEtrEntry 7 } ::= { lispEidRegistrationEtrEntry 2 }
lispEidRegistrationEtrLastRegisterTime OBJECT-TYPE lispEidRegistrationEtrLastRegisterTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time since the last valid register message from this ETR "Time since the last valid register message from this ETR
for the given EID prefix was received by this device." for the given EID prefix was received by this device."
::= { lispEidRegistrationEtrEntry 6 } ::= { lispEidRegistrationEtrEntry 3 }
lispEidRegistrationEtrTtl OBJECT-TYPE lispEidRegistrationEtrTtl OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
"Time in minutes of the Record TTL of the "Time in minutes of the Record TTL of the
registering ETR device for this EID prefix." registering ETR device for this EID prefix."
::= { lispEidRegistrationEtrEntry 6 } ::= { lispEidRegistrationEtrEntry 4 }
lispEidRegistrationEtrProxyReply OBJECT-TYPE lispEidRegistrationEtrProxyReply OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates proxy-replying status of the registering "Indicates proxy-replying status of the registering
ETR for this EID prefix. (0 = Map-Server should not ETR for this EID prefix. (0 = Map-Server should not
proxy-reply; 1 = Map-Server may proxy-reply)." proxy-reply; 1 = Map-Server may proxy-reply)."
::= { lispEidRegistrationEtrEntry 16 } ::= { lispEidRegistrationEtrEntry 5 }
lispEidRegistrationEtrWantsMapNotify OBJECT-TYPE lispEidRegistrationEtrWantsMapNotify OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether the EID prefix wants "Indicates whether the EID prefix wants
Map-Notifications (0 = EID prefix does not want Map-Notifications (0 = EID prefix does not want
Map-Notifications; 1 = EID prefix wants Map-Notifications; 1 = EID prefix wants
Map-Notifications)." Map-Notifications)."
::= { lispEidRegistrationEntry 12 } ::= { lispEidRegistrationEtrEntry 6 }
lispEidRegistrationLocatorTable OBJECT-TYPE lispEidRegistrationLocatorTable OBJECT-TYPE
SYNTAX SEQUENCE OF LispEidRegistrationLocatorEntry SYNTAX SEQUENCE OF LispEidRegistrationLocatorEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides the properties of all locators "This table provides the properties of all locators
per lisp site that are served by this device when per lisp site that are served by this device when
configured to be a Map-Server." configured to be a Map-Server."
REFERENCE "[LISP]" REFERENCE "[LISP]"
::= { lisp 7 } ::= { lisp 8 }
lispEidRegistrationLocatorEntry OBJECT-TYPE lispEidRegistrationLocatorEntry OBJECT-TYPE
SYNTAX LispEidRegistrationLocatorEntry SYNTAX LispEidRegistrationLocatorEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (conceptual row) in the "An entry (conceptual row) in the
lispEidRegistrationLocatorTable." lispEidRegistrationLocatorTable."
INDEX { lispEidRegistrationEidLength, INDEX { lispEidRegistrationEidLength,
lispEidRegistrationEid, lispEidRegistrationEid,
skipping to change at page 34, line 45 skipping to change at page 34, line 39
lispEidRegistrationLocatorMWeight Integer32 lispEidRegistrationLocatorMWeight Integer32
} }
lispEidRegistrationLocatorRlocLength OBJECT-TYPE lispEidRegistrationLocatorRlocLength OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to get the octet-length of "This object is used to get the octet-length of
lispEidRegistrationLocatorRloc, the next object." lispEidRegistrationLocatorRloc, the next object."
::= { lispEidRegistrationLocatorEntry 4 } ::= { lispEidRegistrationLocatorEntry 1 }
lispEidRegistrationLocatorRloc OBJECT-TYPE lispEidRegistrationLocatorRloc OBJECT-TYPE
SYNTAX LispAddressType SYNTAX LispAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The locator of the given EID prefix being registered by "The locator of the given EID prefix being registered by
the given ETR with this device." the given ETR with this device."
::= { lispEidRegistrationLocatorEntry 5 } ::= { lispEidRegistrationLocatorEntry 2 }
lispEidRegistrationLocatorRlocState OBJECT-TYPE lispEidRegistrationLocatorRlocState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
down (0), down (0),
up (1) up (1)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The cached state of this RLOC received in "The cached state of this RLOC received in
map-register from the ETR by the device, in the map-register from the ETR by the device, in the
capacity of a Map-Server. Value 0 refers to down, capacity of a Map-Server. Value 0 refers to down,
value 1 refers to up." value 1 refers to up."
::= { lispEidRegistrationLocatorEntry 8 } ::= { lispEidRegistrationLocatorEntry 3 }
lispEidRegistrationLocatorIsLocal OBJECT-TYPE lispEidRegistrationLocatorIsLocal OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates if the given locator is local to the "Indicates if the given locator is local to the
registering ETR. Value 1 implies local, value 0 registering ETR. Value 1 implies local, value 0
implies not local." implies not local."
::= { lispEidRegistrationLocatorEntry 13 } ::= { lispEidRegistrationLocatorEntry 4 }
lispEidRegistrationLocatorRlocPriority OBJECT-TYPE lispEidRegistrationLocatorRlocPriority OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The unicast priority of the RLOC for this EID prefix "The unicast priority of the RLOC for this EID prefix
in the register message sent by the given ETR." in the register message sent by the given ETR."
::= { lispEidRegistrationLocatorEntry 9 } ::= { lispEidRegistrationLocatorEntry 5 }
lispEidRegistrationLocatorRlocWeight OBJECT-TYPE lispEidRegistrationLocatorRlocWeight OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The unicast weight of the RLOC for this EID prefix "The unicast weight of the RLOC for this EID prefix
in the register message sent by the given ETR." in the register message sent by the given ETR."
::= { lispEidRegistrationLocatorEntry 10 } ::= { lispEidRegistrationLocatorEntry 6 }
lispEidRegistrationLocatorRlocMPriority OBJECT-TYPE lispEidRegistrationLocatorRlocMPriority OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The multicast priority of the RLOC for this EID prefix "The multicast priority of the RLOC for this EID prefix
in the register message sent by the given ETR." in the register message sent by the given ETR."
::= { lispEidRegistrationLocatorEntry 11 } ::= { lispEidRegistrationLocatorEntry 7 }
lispEidRegistrationLocatorRlocMWeight OBJECT-TYPE lispEidRegistrationLocatorRlocMWeight OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The multicast weight of the RLOC for this EID prefix "The multicast weight of the RLOC for this EID prefix
in the register message sent by the given ETR." in the register message sent by the given ETR."
::= { lispEidRegistrationLocatorEntry 12 } ::= { lispEidRegistrationLocatorEntry 8 }
lispUseMapServerTable OBJECT-TYPE lispUseMapServerTable OBJECT-TYPE
SYNTAX SEQUENCE OF LispMapServersEntry SYNTAX SEQUENCE OF LispMapServersEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides the properties of the "This table provides the properties of the
map-server(s) with which this device is map-server(s) with which this device is
configured to register." configured to register."
REFERENCE "[LISP]" REFERENCE "[LISP]"
::= { lisp 8 } ::= { lisp 9 }
lispUseMapServerEntry OBJECT-TYPE lispUseMapServerEntry OBJECT-TYPE
SYNTAX LispMapServersEntry SYNTAX LispMapServersEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (conceptual row) in the lispUseMapServerTable." "An entry (conceptual row) in the lispUseMapServerTable."
INDEX { lispUseMapServerAddressLength, INDEX { lispUseMapServerAddressLength,
lispUseMapServerAddress } lispUseMapServerAddress }
::= { lispUseMapServerTable 1 } ::= { lispUseMapServerTable 1 }
skipping to change at page 37, line 38 skipping to change at page 37, line 31
::= { lispUseMapServerEntry 3 } ::= { lispUseMapServerEntry 3 }
lispUseMapResolverTable OBJECT-TYPE lispUseMapResolverTable OBJECT-TYPE
SYNTAX SEQUENCE OF LispMapResolversEntry SYNTAX SEQUENCE OF LispMapResolversEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides the properties of the "This table provides the properties of the
map-resolver(s) this device is configured to use." map-resolver(s) this device is configured to use."
REFERENCE "[LISP]" REFERENCE "[LISP]"
::= { lisp 9 } ::= { lisp 10 }
lispUseMapResolverEntry OBJECT-TYPE lispUseMapResolverEntry OBJECT-TYPE
SYNTAX LispMapResolversEntry SYNTAX LispMapResolversEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (conceptual row) in the "An entry (conceptual row) in the
lispUseMapResolverTable." lispUseMapResolverTable."
INDEX { lispUseMapResolverAddressLength, INDEX { lispUseMapResolverAddressLength,
lispUseMapResolverAddress } lispUseMapResolverAddress }
skipping to change at page 38, line 49 skipping to change at page 38, line 41
lispUseProxyEtrTable OBJECT-TYPE lispUseProxyEtrTable OBJECT-TYPE
SYNTAX SEQUENCE OF LispUseProxyEtrEntry SYNTAX SEQUENCE OF LispUseProxyEtrEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides the properties of all "This table provides the properties of all
Proxy ETRs that this device is configured Proxy ETRs that this device is configured
to use." to use."
REFERENCE "[LISP]" REFERENCE "[LISP]"
::= { lisp 10 } ::= { lisp 11 }
lispUseProxyEtrEntry OBJECT-TYPE lispUseProxyEtrEntry OBJECT-TYPE
SYNTAX LispUseProxyEtrEntry SYNTAX LispUseProxyEtrEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (conceptual row) in the lispUseProxyEtrTable." "An entry (conceptual row) in the lispUseProxyEtrTable."
INDEX { lispUseProxyEtrAddressLength, INDEX { lispUseProxyEtrAddressLength,
lispUseProxyEtrAddress } lispUseProxyEtrAddress }
::= { lispUseProxyEtrTable 1 } ::= { lispUseProxyEtrTable 1 }
LispUseProxyEtrEntry ::= SEQUENCE { LispUseProxyEtrEntry ::= SEQUENCE {
lispUseProxyEtrAddressLength Integer32, lispUseProxyEtrAddressLength Integer32,
lispUseProxyEtrAddress LispAddressType, lispUseProxyEtrAddress LispAddressType,
lispUseProxyEtrPriority Integer32,
lispUseProxyEtrWeight Integer32,
lispUseProxyEtrMPriority Integer32,
lispUseProxyEtrMWeight Integer32,
lispUseProxyEtrState INTEGER lispUseProxyEtrState INTEGER
} }
lispUseProxyEtrAddressLength OBJECT-TYPE lispUseProxyEtrAddressLength OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to get the octet-length of "This object is used to get the octet-length of
lispUseProxyEtrAddress, the next object." lispUseProxyEtrAddress, the next object."
::= { lispUseProxyEtrEntry 1 } ::= { lispUseProxyEtrEntry 1 }
lispUseProxyEtrAddress OBJECT-TYPE lispUseProxyEtrAddress OBJECT-TYPE
SYNTAX LispAddressType SYNTAX LispAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Address of Proxy ETR configured on this device." "Address of Proxy ETR configured on this device."
::= { lispUseProxyEtrEntry 2 } ::= { lispUseProxyEtrEntry 2 }
lispUseProxyEtrPriority OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The unicast priority of the PETR locator."
::= { lispUseProxyEtrEntry 3 }
lispUseProxyEtrWeight OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The unicast weight of the PETR locator."
::= { lispUseProxyEtrEntry 4 }
lispUseProxyEtrMPriority OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The multicast priority of the PETR locator."
::= { lispUseProxyEtrEntry 5 }
lispUseProxyEtrMWeight OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The multicast weight of the PETR locator."
::= { lispUseProxyEtrEntry 6 }
lispUseProxyEtrState OBJECT-TYPE lispUseProxyEtrState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
down (0), down (0),
up (1) up (1)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"State of this Proxy ETR configured on this device "State of this Proxy ETR configured on this device
(0 = Proxy ETR is down; 1 = Proxy ETR is up)." (0 = Proxy ETR is down; 1 = Proxy ETR is up)."
::= { lispUseProxyEtrEntry 3 } ::= { lispUseProxyEtrEntry 7 }
-- --
-- Conformance Information -- Conformance Information
-- --
lispMIBConformance OBJECT IDENTIFIER ::= { lispMIB 2 } lispMIBConformance OBJECT IDENTIFIER ::= { lispMIB 2 }
lispMIBCompliances OBJECT IDENTIFIER ::= { lispMIBConformance 1 } lispMIBCompliances OBJECT IDENTIFIER ::= { lispMIBConformance 1 }
lispMIBGroups OBJECT IDENTIFIER ::= { lispMIBConformance 2 } lispMIBGroups OBJECT IDENTIFIER ::= { lispMIBConformance 2 }
-- --
skipping to change at page 52, line 16 skipping to change at page 53, line 4
instance of these MIB modules is properly configured to give access instance of these MIB modules is properly configured to give access
to the objects only to those principals (users) that have legitimate to the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
10. IANA Considerations 10. IANA Considerations
LISP is an experimental protocol and the LISP MIB is an experimental LISP is an experimental protocol and the LISP MIB is an experimental
MIB. No IANA actions are required by this document. MIB. No IANA actions are required by this document.
11. References 11. References
11.1. Normative References 11.1. Normative References
[INTERWORK] Lewis, D., Meyer, D., Farinacci, D., and V. Fuller, [INTERWORK] Lewis, D., Meyer, D., Farinacci, D., and V. Fuller,
"Interworking LISP with IPv4 and IPv6", "Interworking LISP with IPv4 and IPv6",
draft-ietf-lisp-interworking-02.txt (work in progress), draft-ietf-lisp-interworking-06.txt (work in progress),
June 2011. March 2012.
[LCAF] Farinacci, D., Meyer, D., and J. Snijders, "LISP
Canonical Address Format",
draft-farinacci-lisp-lcaf-06.txt (work in progress),
October 2011.
[LISP] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, [LISP] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis,
"Locator/ID Separation Protocol (LISP)", "Locator/ID Separation Protocol (LISP)",
draft-ietf-lisp-16.txt (work in progress), draft-ietf-lisp-23.txt (work in progress), May 2012.
October 2011.
[LISP-ALT] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis,
"LISP Alternative Topology (LISP-ALT)",
draft-ietf-lisp-alt-09.txt (work in progress),
September 2011.
[LISP-MS] Farinacci, D. and V. Fuller, "LISP Map Server", [LISP-MS] Farinacci, D. and V. Fuller, "LISP Map Server",
draft-ietf-lisp-ms-12.txt (work in progress), draft-ietf-lisp-ms-16.txt (work in progress),
October 2011. March 2012.
[RFC1035] Mockapetris, P., "Domain names - implementation and [RFC1035] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, November 1987. specification", STD 13, RFC 1035, November 1987.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2404] Madson, C. and R. Glenn, "The Use of HMAC-SHA-1-96 [RFC2404] Madson, C. and R. Glenn, "The Use of HMAC-SHA-1-96
within ESP and AH", RFC 2404, November 1998. within ESP and AH", RFC 2404, November 1998.
skipping to change at page 53, line 26 skipping to change at page 53, line 49
April 1999. April 1999.
[RFC4634] Eastlake, D. and T. Hansen, "US Secure Hash Algorithms [RFC4634] Eastlake, D. and T. Hansen, "US Secure Hash Algorithms
(SHA and HMAC-SHA)", RFC 4634, July 2006. (SHA and HMAC-SHA)", RFC 4634, July 2006.
11.2. Informative References 11.2. Informative References
[IANA] "IANA-ADDRESS-FAMILY-NUMBERS-MIB DEFINITIONS", <http:// [IANA] "IANA-ADDRESS-FAMILY-NUMBERS-MIB DEFINITIONS", <http://
www.iana.org/assignments/ianaaddressfamilynumbers-mib>. www.iana.org/assignments/ianaaddressfamilynumbers-mib>.
[LCAF] Farinacci, D., Meyer, D., and J. Snijders, "LISP
Canonical Address Format",
draft-farinacci-lisp-lcaf-07.txt (work in progress),
March 2012.
[LISP-MCAST] Farinacci, D., Meyer, D., Zwiebel, J., and S. Venaas, [LISP-MCAST] Farinacci, D., Meyer, D., Zwiebel, J., and S. Venaas,
"LISP for Multicast Environments", "LISP for Multicast Environments",
draft-ietf-lisp-multicast-11.txt (work in progress), draft-ietf-lisp-multicast-14.txt (work in progress),
November 2011. February 2012.
[LISP-MN] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, [LISP-MN] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis,
"LISP Mobile Node Architecture", "LISP Mobile Node Architecture",
draft-meyer-lisp-mn-06.txt (work in progress), draft-meyer-lisp-mn-07.txt (work in progress),
October 2011. April 2012.
[RFC2784] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. [RFC2784] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P.
Traina, "Generic Routing Encapsulation (GRE)", Traina, "Generic Routing Encapsulation (GRE)",
RFC 2784, March 2000. RFC 2784, March 2000.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for "Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410, Internet-Standard Management Framework", RFC 3410,
December 2002. December 2002.
skipping to change at page 54, line 9 skipping to change at page 54, line 36
Protocol 4 (BGP-4)", RFC 4271, January 2006. Protocol 4 (BGP-4)", RFC 4271, January 2006.
[RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter,
"Multiprotocol Extensions for BGP-4", RFC 4760, "Multiprotocol Extensions for BGP-4", RFC 4760,
January 2007. January 2007.
Appendix A. Open Issues Appendix A. Open Issues
Open issues for the LISP MIB include the following: Open issues for the LISP MIB include the following:
1. This version of the LISP MIB draft does not include LISP 1. This LISP MIB draft does not include LISP Multicast
Multicast considerations. Multicast considerations will be added considerations. Multicast considerations will be added in a
in the next version of this draft. separate LISP Multicast MIB draft.
Appendix B. Acknowledgments Appendix B. Acknowledgments
An initial thank you goes to Dino Farinacci for his inputs and review A thank you is owed to Dino Farinacci for his inputs and review
comments on the initial versions of this draft. In addition, the comments on the initial versions of this draft. In addition, the
authors would like to gratefully acknowledge many people who have authors would like to gratefully acknowledge several others who have
reviewed and commented on this draft. They include: Darrel Lewis, reviewed and commented on this draft. They include: Darrel Lewis,
Isidor Kouvelas, Jesper Skriver, Selina Heimlich, and Parna Agrawal. Isidor Kouvelas, Jesper Skriver, Selina Heimlich, and Parna Agrawal.
Authors' Addresses Authors' Addresses
Gregg Schudel Gregg Schudel
cisco Systems cisco Systems
Tasman Drive Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
USA USA
 End of changes. 92 change blocks. 
135 lines changed or deleted 156 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/