tech-invite   World Map     

IETF     RFCs     Groups     SIP     ABNFs    |    3GPP     Specs     Glossaries     Architecture     IMS     UICC    |    search     info

RFC 7052

 Errata 
Experimental
Pages: 66
Top     in Index     Prev     Next
in Group Index     Prev in Group     Next in Group     Group: LISP

Locator/ID Separation Protocol (LISP) MIB

Part 1 of 3, p. 1 to 6
None       Next RFC Part

 


Top       ToC       Page 1 
Internet Engineering Task Force (IETF)                        G. Schudel
Request for Comments: 7052                                 Cisco Systems
Category: Experimental                                           A. Jain
ISSN: 2070-1721                                         Juniper Networks
                                                               V. Moreno
                                                           Cisco Systems
                                                            October 2013


               Locator/ID Separation Protocol (LISP) MIB

Abstract

   This document defines the MIB module that contains managed objects to
   support the monitoring devices of the Locator/ID Separation Protocol
   (LISP).  These objects provide information useful for monitoring LISP
   devices, including determining basic LISP configuration information,
   LISP functional status, and operational counters and other
   statistics.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for examination, experimental implementation, and
   evaluation.

   This document defines an Experimental Protocol for the Internet
   community.  This document is a product of the Internet Engineering
   Task Force (IETF).  It represents the consensus of the IETF
   community.  It has received public review and has been approved for
   publication by the Internet Engineering Steering Group (IESG).  Not
   all documents approved by the IESG are a candidate for any level of
   Internet Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc7052.

Page 2 
Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Requirements Notation  . . . . . . . . . . . . . . . . . . . .  3
   3.  The Internet-Standard Management Framework . . . . . . . . . .  3
   4.  Definition of Terms  . . . . . . . . . . . . . . . . . . . . .  4
   5.  LISP MIB Objectives  . . . . . . . . . . . . . . . . . . . . .  5
   6.  Structure of LISP MIB Module . . . . . . . . . . . . . . . . .  5
     6.1.  Overview of Defined Notifications  . . . . . . . . . . . .  5
     6.2.  Overview of Defined Tables . . . . . . . . . . . . . . . .  5
   7.  LISP MIB Definitions . . . . . . . . . . . . . . . . . . . . .  7
   8.  Relationship to Other MIB Modules  . . . . . . . . . . . . . . 62
     8.1.  MIB Modules Required for IMPORTS . . . . . . . . . . . . . 62
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 63
   10. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 64
   11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 64
     11.1. Normative References . . . . . . . . . . . . . . . . . . . 64
     11.2. Informative References . . . . . . . . . . . . . . . . . . 65
   Appendix A.  Acknowledgments . . . . . . . . . . . . . . . . . . . 66

Top      ToC       Page 3 
1.  Introduction

   This document describes the Management Information Base (MIB) module
   for use with network management protocols in the Internet community.
   Specifically, the MIB for managing devices that support the
   Locator/ID Separation Protocol (LISP) is described.

   LISP [RFC6830] specifies a network-based architecture and mechanisms
   that implement a new semantic for IP addressing using two separate
   name spaces: Endpoint Identifiers (EIDs), used within sites, and
   Routing Locators (RLOCs), used on the transit networks that make up
   the Internet infrastructure.  To achieve this separation, LISP
   defines protocol mechanisms for mapping from EIDs to RLOCs.

   From a data-plane perspective, LISP traffic is handled exclusively at
   the network layer by devices performing Ingress Tunnel Router (ITR)
   and Egress Tunnel Router (ETR) LISP functions.  Data-plane operations
   performed by these devices are described in [RFC6830].  Additionally,
   data-plane interworking between legacy (Internet) and LISP sites is
   implemented by devices performing Proxy ITR (PITR) and Proxy ETR
   (PETR) functions.  The data-plane operations of these devices is
   described in [RFC6832].

   From a control-plane perspective, LISP employs mechanisms related to
   creating, maintaining, and resolving mappings from EIDs to RLOCs.
   LISP ITRs, ETRs, PITRs, and PETRs perform specific control-plane
   functions, and these control-plane operations are described in
   [RFC6830].  Additionally, LISP infrastructure devices supporting LISP
   control-plane functionality include Map-Servers and Map-Resolvers,
   and the control-plane operations of these devices are described in
   [RFC6833].

2.  Requirements Notation

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   [RFC2119].

3.  The Internet-Standard Management Framework

   For a detailed overview of the documents that describe the current
   Internet-Standard Management Framework, please refer to section 7 of
   RFC 3410 [RFC3410].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  MIB objects are generally
   accessed through the Simple Network Management Protocol (SNMP).

Top      ToC       Page 4 
   Objects in the MIB are defined using the mechanisms defined in the
   Structure of Management Information (SMI).  This memo specifies a MIB
   module that is compliant to the SMIv2, which is described in STD 58,
   RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
   [RFC2580].

4.  Definition of Terms

   This document does not define any new terms.  All terms used in this
   document are listed here for completeness; the authoritative
   definition of each term can be found in the definition section of the
   respective specified reference.

   Endpoint ID (EID):  [RFC6830]

   Routing Locator (RLOC):  [RFC6830]

   EID-to-RLOC Cache:  [RFC6830]

   EID-to-RLOC Database:  [RFC6830]

   Ingress Tunnel Router (ITR):  [RFC6830]

   Egress Tunnel Router (ETR):  [RFC6830]

   xTR:  [RFC6830]

   Proxy ITR (PITR):  [RFC6832]

   Proxy ETR (PETR):  [RFC6832]

   LISP Site:  [RFC6830]

   Map-Server:  [RFC6833]

   Map-Resolver:  [RFC6833]

   Map-Request:  [RFC6833]

   Map-Reply:  [RFC6833]

   Negative Map-Reply:  [RFC6833]

Top      ToC       Page 5 
5.  LISP MIB Objectives

   The objectives for this LISP MIB module are to provide a read-only
   mechanism to support the following functions:

   o  Provide a means for obtaining (read-only) a current status of LISP
      features enabled on a device, and (read-only) a current status of
      configuration attributes related to those features.  As one
      example, this MIB could determine the ON/OFF status of LISP
      features such as ITR, ETR, PITR, PETR, MS, or MR support,
      specifically as related to IPv4 or IPv6 address families as well
      as the LISP Canonical Address Format (LCAF) [LCAF] with IANA
      assigned Address Family Number 16387.  Other examples could
      include obtaining the (read-only) status of whether RLOC-Probing
      is enabled, obtaining the status of whether the use of a PETR is
      configured, and obtaining the (read-only) values of other related
      attributes such as the map-cache limit value, or a mapping time-
      to-live (TTL) value.

   o  Provide a means for obtaining (read-only) the current attributes
      of various LISP tables, such as the EID-to-RLOC policy data
      contained in the map-cache, or the local EID-to-RLOC policy data
      contained in the mapping-database.

   o  Provide a means for obtaining (read-only) the current operational
      statistics of various LISP functions, such as the number of
      packets encapsulated and decapsulated by the device.  Other
      counters of operational interest, depending on LISP function,
      include things like the current number of map-cache entries, and
      the total number and rate of map-requests received and sent by the
      device.

6.  Structure of LISP MIB Module

6.1.  Overview of Defined Notifications

   No LISP MIB notifications are defined.

6.2.  Overview of Defined Tables

   The LISP MIB module is composed of the following tables of objects:

   lispFeatures -  This table provides information representing the
      various lisp features that can be enabled on LISP devices.

   lispIidToVrf -  This table provides information representing the
      mapping of a LISP Instance ID to a VRF (Virtual Routing and
      Forwarding).

Top      ToC       Page 6 
   lispGlobalStats -  This table provides global statistics for a given
      Instance ID per address family on a LISP device.

   lispMappingDatabase -  This table represents the EID-to-RLOC database
      that contains the EID-Prefix to RLOC mappings configured on an
      ETR.  In general, this table would be representative of all such
      mappings for a given site to which this device belongs.

   lispMappingDatabaseLocator -  This table represents the set of
      routing locators contained in the EID-to-RLOC database configured
      on an ETR.

   lispMapCache -  This table represents the short-lived, on-demand
      table maintained on an ITR that stores, tracks, and times-out EID-
      to-RLOC mappings.

   lispMapCacheLocator -  This table represents the set of locators per
      EID-Prefix contained in the map-cache table of an ITR.

   lispConfiguredLocator -  This table represents the set of routing
      locators configured on a LISP device.

   lispEidRegistration -  This table provides the properties of each
      EID-Prefix that is registered with this device when configured to
      be a Map-Server.

   lispEidRegistrationEtr -  This table provides the properties of the
      different ETRs that send registers, for a given EID-Prefix, to
      this device when configured to be a Map-Server.

   lispEidRegistrationLocator -  This table provides the properties of
      the different locators per EID prefix that is registered with this
      device when configured to be a Map-Server.

   lispUseMapServer -  This table provides the properties of all Map-
      Servers that this device is configured to use.

   lispUseMapResolver -  This table provides the properties of all Map-
      Resolvers that this device is configured to use.

   lispUseProxyEtr -  This table provides the properties of all Proxy
      ETRs that this device is configured to use.


Next RFC Part