LISP MIB
draft-ietf-lisp-mib-04
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (lisp WG)
|
|
Last updated |
|
2012-06-25
|
|
Replaces |
|
draft-schudel-lisp-mib
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
None
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group G. Schudel
Internet-Draft A. Jain
Intended status: Experimental V. Moreno
Expires: December 24, 2012 cisco Systems
June 22, 2012
LISP MIB
draft-ietf-lisp-mib-04
Abstract
This document defines managed objects for the Locator/ID Separation
Protocol (LISP). These objects provide information useful for
monitoring LISP devices, including basic configuration information,
LISP status, and operational statistics.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 24, 2012.
Copyright Notice
Copyright (c) 2012 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.
Schudel, et al. Expires December 24, 2012 [Page 1]
Internet-Draft LISP MIB June 2012
Table of Contents
1. Requirements Notation . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. The Internet-Standard Management Framework . . . . . . . . . . 3
4. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 4
5. LISP MIB Objectives . . . . . . . . . . . . . . . . . . . . . 6
6. Structure of LISP MIB Module . . . . . . . . . . . . . . . . . 6
6.1. Overview of Defined Notifications . . . . . . . . . . . . 6
6.2. Overview of Defined Tables . . . . . . . . . . . . . . . . 7
7. LISP MIB Definitions . . . . . . . . . . . . . . . . . . . . . 8
8. Relationship to Other MIB Modules . . . . . . . . . . . . . . 52
8.1. MIB modules required for IMPORTS . . . . . . . . . . . . . 52
9. Security Considerations . . . . . . . . . . . . . . . . . . . 52
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 52
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 53
11.1. Normative References . . . . . . . . . . . . . . . . . . . 53
11.2. Informative References . . . . . . . . . . . . . . . . . . 53
Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . . 54
Appendix B. Acknowledgments . . . . . . . . . . . . . . . . . . . 54
Schudel, et al. Expires December 24, 2012 [Page 2]
Internet-Draft LISP MIB June 2012
1. Requirements Notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
2. Introduction
This draft describes the Management Information Base (MIB) module for
use with network management protocols in the Internet community.
Specifically, the MIB for managing Locator/ID Separation Protocol
(LISP) devices is described.
LISP [LISP] 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 [LISP]. Additionally,
data plane interworking between legacy (Internet) and LISP sites is
Show full document text