Definitions of Managed Objects for Mapping of Address and Port with Encapsulation (MAP-E)
RFC 8389
Internet Engineering Task Force (IETF) Y. Fu
Request for Comments: 8389 CNNIC
Category: Standards Track S. Jiang
ISSN: 2070-1721 B. Liu
Huawei Technologies Co., Ltd
J. Dong
Y. Chen
Tsinghua University
December 2018
Definitions of Managed Objects for
Mapping of Address and Port with Encapsulation (MAP-E)
Abstract
This memo defines a portion of the Management Information Base (MIB)
for Mapping of Address and Port with Encapsulation (MAP-E) for use
with network management protocols.
Status of This Memo
This is an Internet Standards Track document.
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). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8389.
Copyright Notice
Copyright (c) 2018 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
(https://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.
Fu, et al. Standards Track [Page 1]
RFC 8389 MAP-E MIB December 2018
Table of Contents
1. Introduction ....................................................2
2. The Internet-Standard Management Framework ......................2
3. Terminology .....................................................3
4. Structure of the MIB Module .....................................3
4.1. The mapMIBObjects ..........................................3
4.1.1. The mapRule Subtree .................................3
4.1.2. The mapSecurityCheck Subtree ........................3
4.2. The mapMIBConformance Subtree ..............................4
5. Definitions .....................................................4
6. IANA Considerations ............................................12
7. Security Considerations ........................................12
8. References .....................................................13
8.1. Normative References ......................................13
8.2. Informative References ....................................14
Acknowledgements ..................................................15
Authors' Addresses ................................................16
1. Introduction
Mapping of Address and Port with Encapsulation (MAP-E) [RFC7597] is a
stateless, automatic tunneling mechanism for providing an IPv4
connectivity service to end users over a service provider's IPv6
network.
This document defines a portion of the Management Information Base
(MIB) for use with monitoring MAP-E devices.
2. 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).
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].
Fu, et al. Standards Track [Page 2]
RFC 8389 MAP-E MIB December 2018
3. Terminology
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
Show full document text