draft-ietf-lisp-mib-10.txt   draft-ietf-lisp-mib-11.txt 
Network Working Group G. Schudel Network Working Group G. Schudel
Internet-Draft cisco Systems Internet-Draft cisco Systems
Intended status: Experimental A. Jain Intended status: Experimental A. Jain
Expires: November 23, 2013 Juniper Networks Expires: December 19, 2013 Juniper Networks
V. Moreno V. Moreno
cisco Systems cisco Systems
May 22, 2013 June 17, 2013
LISP MIB LISP MIB
draft-ietf-lisp-mib-10 draft-ietf-lisp-mib-11
Abstract Abstract
This document defines managed objects for the Locator/ID Separation This document defines the MIB module that contains managed objects to
support the monitoring devices that support the Locator/ID Separation
Protocol (LISP). These objects provide information useful for Protocol (LISP). These objects provide information useful for
monitoring LISP devices, including determining basic LISP monitoring LISP devices, including determining basic LISP
configuration information, LISP functional status, and operational configuration information, LISP functional status, and operational
counters and other statistics. counters and other statistics.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 November 23, 2013. This Internet-Draft will expire on December 19, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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
skipping to change at page 2, line 21 skipping to change at page 2, line 22
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. The Internet-Standard Management Framework . . . . . . . . . . 3 3. The Internet-Standard Management Framework . . . . . . . . . . 3
4. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 4 4. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 4
5. LISP MIB Objectives . . . . . . . . . . . . . . . . . . . . . 4 5. LISP MIB Objectives . . . . . . . . . . . . . . . . . . . . . 4
6. Structure of LISP MIB Module . . . . . . . . . . . . . . . . . 5 6. Structure of LISP MIB Module . . . . . . . . . . . . . . . . . 5
6.1. Overview of Defined Notifications . . . . . . . . . . . . 5 6.1. Overview of Defined Notifications . . . . . . . . . . . . 5
6.2. Overview of Defined Tables . . . . . . . . . . . . . . . . 5 6.2. Overview of Defined Tables . . . . . . . . . . . . . . . . 5
7. LISP MIB Definitions . . . . . . . . . . . . . . . . . . . . . 6 7. LISP MIB Definitions . . . . . . . . . . . . . . . . . . . . . 6
8. Relationship to Other MIB Modules . . . . . . . . . . . . . . 61 8. Relationship to Other MIB Modules . . . . . . . . . . . . . . 61
8.1. MIB modules required for IMPORTS . . . . . . . . . . . . . 61 8.1. MIB modules required for IMPORTS . . . . . . . . . . . . . 61
9. Security Considerations . . . . . . . . . . . . . . . . . . . 61 9. Security Considerations . . . . . . . . . . . . . . . . . . . 62
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 62 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 62
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 62 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 63
11.1. Normative References . . . . . . . . . . . . . . . . . . . 62 11.1. Normative References . . . . . . . . . . . . . . . . . . . 63
11.2. Informative References . . . . . . . . . . . . . . . . . . 63 11.2. Informative References . . . . . . . . . . . . . . . . . . 63
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 64 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 64
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", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
[RFC2119]. [RFC2119].
2. Introduction 2. Introduction
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 devices that support the
(LISP) devices is described. Locator/ID Separation Protocol (LISP) is described.
LISP [RFC6830] specifies a network-based architecture and mechanisms LISP [RFC6830] 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. defines protocol mechanisms for mapping from EIDs to RLOCs.
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)
skipping to change at page 4, line 51 skipping to change at page 4, line 51
Map-Request: [RFC6833] Map-Request: [RFC6833]
Map-Reply: [RFC6833] Map-Reply: [RFC6833]
Negative Map-Reply: [RFC6833] Negative Map-Reply: [RFC6833]
5. LISP MIB Objectives 5. LISP MIB Objectives
The objectives for this LISP MIB module are to provide a read-only The objectives for this LISP MIB module are to provide a read-only
meachanisms to support the following functions: meachanism to support the following functions:
o Provide a means for obtaining an ON/OFF list of LISP features o Provide a means for obtaining (read-only) a current status of LISP
configured on a device, and the current status of configuration features enabled on a device, and (read-only) a current status of
attributes related to those features. As an example, LISP configuration attributes related to those features. (This MIB
features that could be enabled might include ITR, ETR, PITR, PETR, provides read-only capabilities; it does not provide any
MS or MR support for IPv4 or IPv6 address families. Other capablities for setting or changing features.) As one example,
examples could include indicating whether rloc-probing is enabled, this MIB could determine the ON/OFF status of LISP features such
or whether the use of a PETR is enabled. Configuration attributes as ITR, ETR, PITR, PETR, MS or MR support, specifically as
related to these features could include the setting of a realated to both IPv4 or IPv6 address families. Other examples
configured map-cache limit value, or the setting of a mapping could include: obtaining the (read-only) status of whether rloc-
time-to-live value. probing is enabled, 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 value.
o Provide a means for obtaining the current attributes of various o Provide a means for obtaining (read-only) the current attributes
LISP tables, such as the EID-to-RLOC policy data contained in the of various LISP tables, such as the EID-to-RLOC policy data
Map-Cache, or the local EID-to-RLOC policy data contained in the contained in the Map-Cache, or the local EID-to-RLOC policy data
Mapping-Database. contained in the Mapping-Database.
o Provide a means for obtaining the current operational statistics o Provide a means for obtaining (read-only) the current operational
of various LISP functions, such as the number of packets statistics of various LISP functions, such as the number of
encapsulated and decapsulated by the device. Other counters of packets encapsulated and decapsulated by the device. Other
operational interest, depending on LISP function, include things counters of operational interest, depending on LISP function,
like the current number of map-cache entries, and the total number include things like the current number of map-cache entries, and
and rate of map-requests received and sent by the device. the total number and rate of map-requests received and sent by the
device.
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 the following tables of objects: The LISP MIB module is composed of the following tables of objects:
skipping to change at page 7, line 9 skipping to change at page 7, line 14
Integer32, TimeTicks FROM SNMPv2-SMI -- [RFC2578] Integer32, TimeTicks FROM SNMPv2-SMI -- [RFC2578]
TruthValue, TEXTUAL-CONVENTION, TruthValue, TEXTUAL-CONVENTION,
TimeStamp FROM SNMPv2-TC -- [RFC2579] TimeStamp FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580] MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580]
MplsL3VpnName MplsL3VpnName
FROM MPLS-L3VPN-STD-MIB -- [RFC4382] FROM MPLS-L3VPN-STD-MIB -- [RFC4382]
AddressFamilyNumbers AddressFamilyNumbers
FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB; -- [IANA] FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB; -- [IANA]
lispMIB MODULE-IDENTITY lispMIB MODULE-IDENTITY
LAST-UPDATED "201305240000Z" -- 22 May 2013 LAST-UPDATED "201306170000Z" -- 17 June 2013
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
"Locator/ID Separation Protocol (LISP) MIB Managed Object "This MIB module contains managed objects to support
module. The LISP MIB is intended for management of LISP monitoring devices that support the Locator/ID Separation
devices. Protocol (LISP).
Copyright (C) The IETF Trust (2013)." Copyright (C) The IETF Trust (2013)."
REVISION "201305240000Z" -- 22 May 2013 REVISION "201306170000Z" -- 17 June 2013
DESCRIPTION "Initial version of the IETF LISP-MIB module. Published DESCRIPTION "Initial version of the IETF LISP-MIB module. Published
as RFC xxxx." as RFC xxxx."
-- RFC Ed.: RFC-editor pls fill in xxxx -- RFC Ed.: RFC-editor pls fill in xxxx
::= { mib-2 XXX } ::= { mib-2 XXX }
-- RFC Ed.: assigned by IANA, see section 10 for details -- RFC Ed.: assigned by IANA, see section 10 for details
-- --
-- Textual Conventions -- Textual Conventions
-- --
LispAddressType ::= TEXTUAL-CONVENTION LispAddressType ::= TEXTUAL-CONVENTION
DISPLAY-HINT "39a" DISPLAY-HINT "39a"
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
generalization for representing addresses that belong to for representing addresses belonging to those address-families.
those address-families. For convenience, this document For convenience, this document refers to any such address as a
refers to any such address as a LISP address. LISP address. LispAddressType textual-convention consists of
LispAddressType textual-convention consists of the the following four-tuple:
following four-tuple:
1. IANA Address Family Number: A field of length 2-octets, 1. IANA Address Family Number: A field of length 2-octets,
whose value is of the form following the assigned whose value is of the form following the assigned
AddressFamilyNumbers textual-convention described in AddressFamilyNumbers textual-convention described in
[IANA]. The enumerations are listed in [IANA]. Note [IANA]. The enumerations are listed in [IANA]. Note
that this list of address family numbers is maintained that this list of address family numbers is maintained
by IANA. by IANA.
2. Length of LISP address: A field of length 1-octet, whose 2. Length of LISP address: A field of length 1-octet, whose
value indicates the octet-length of the next (third) value indicates the octet-length of the next (third)
field of this LispAddressType four-tuple. field of this LispAddressType four-tuple.
3. LISP address: A field of variable length as indicated in 3. LISP address: A field of variable length as indicated in
skipping to change at page 9, line 36 skipping to change at page 9, line 40
where 11 is the total length in octets of the next object where 11 is the total length in octets of the next object
(lispMapCacheEID of type LispAddressType). Then, the value (lispMapCacheEID of type LispAddressType). Then, the value
16387 indicates the LCAF AF (see [IANA]), the value 7 16387 indicates the LCAF AF (see [IANA]), the value 7
indicates that the LCAF AF is 7-octets in length in this indicates that the LCAF AF is 7-octets in length in this
case, 2 indicates that LCAF Type 2 encoding is used (see case, 2 indicates that LCAF Type 2 encoding is used (see
[LCAF]), 101 gives the Instance ID, 1 gives the AFI (per [LCAF]), 101 gives the Instance ID, 1 gives the AFI (per
[IANA]) for an IPv4 address, 192.0.2.0 is the IPv4 address, [IANA]) for an IPv4 address, 192.0.2.0 is the IPv4 address,
and 24 is the mask-length in bits. Note that the and 24 is the mask-length in bits. Note that the
lispMapCacheEidLength value of 11 octets is used to compute lispMapCacheEidLength value of 11 octets is used to compute
the length of the last field in lispMapCacheEid to be 1 octet, the length of the last field in lispMapCacheEid to be 1 octet,
as computed by 11 - (2 + 1 + 1 + 1 + 1 + 1 + 4) = 1." as computed by 11 - (2 + 1 + 1 + 1 + 1 + 1 + 4) = 1.
Note: all LISP header formats and locations of specific
flags, bits, and fields are as given in the base LISP
references of RFC6830, RFC6832, and RFC6833."
REFERENCE REFERENCE
"RFC6830, Section 14.2, draft-ietf-lisp-lcaf-02.txt." "RFC6830, Section 14.2, draft-ietf-lisp-lcaf-02.txt."
SYNTAX OCTET STRING (SIZE (5..39)) SYNTAX OCTET STRING (SIZE (5..39))
-- --
-- Top level components of this MIB. -- Top level components of this MIB.
-- --
lispObjects OBJECT IDENTIFIER ::= { lispMIB 1 } lispObjects OBJECT IDENTIFIER ::= { lispMIB 1 }
lispConformance OBJECT IDENTIFIER ::= { lispMIB 2 } lispConformance OBJECT IDENTIFIER ::= { lispMIB 2 }
skipping to change at page 30, line 47 skipping to change at page 31, line 5
of the RLOC for this EID prefix. Note that this is of the RLOC for this EID prefix. Note that this is
independent of lispMapCacheLocatorRlocTimeStamp." independent of lispMapCacheLocatorRlocTimeStamp."
::= { lispMapCacheLocatorEntry 9 } ::= { 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 elapsed since the last change of the unicast weight "Time elapsed since the last change of the unicast weight
of the RLOC for this EID prefix.Note that this is of the RLOC for this EID prefix. Note that this is
independent of lispMapCacheLocatorRlocTimeStamp." independent of lispMapCacheLocatorRlocTimeStamp."
::= { lispMapCacheLocatorEntry 10 } ::= { 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 of the "Time since the last change of the multicast priority of the
RLOC for this EID prefix." RLOC for this EID prefix."
 End of changes. 18 change blocks. 
44 lines changed or deleted 51 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/