Definitions of Managed Objects for Network Address Translators (NATs)
RFC 7659
| Document | Type |
RFC - Proposed Standard
(October 2015; No errata)
Was draft-perrault-behave-natv2-mib (individual in tsv area)
|
|
|---|---|---|---|
| Last updated | 2015-10-27 | ||
| Replaces | draft-ietf-behave-nat-mib | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | (None) | |
| Document shepherd | Spencer Dawkins | ||
| Shepherd write-up | Show (last changed 2015-05-24) | ||
| IESG | IESG state | RFC 7659 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Spencer Dawkins | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) S. Perreault
Request for Comments: 7659 Jive Communications
Category: Standards Track T. Tsou
ISSN: 2070-1721 Huawei Technologies
S. Sivakumar
Cisco Systems
T. Taylor
PT Taylor Consulting
October 2015
Definitions of Managed Objects for Network Address Translators (NATs)
Abstract
This memo defines a portion of the Management Information Base (MIB)
for devices implementing the Network Address Translator (NAT)
function. The new MIB module defined in this document, NATV2-MIB, is
intended to replace module NAT-MIB (RFC 4008). NATV2-MIB is not
backwards compatible with NAT-MIB, for reasons given in the text of
this document. A companion document deprecates all objects in NAT-
MIB. NATV2-MIB can be used for the monitoring of NAT instances on a
device capable of NAT function. Compliance levels are defined for
three application scenarios: basic NAT, pooled NAT, and
carrier-grade NAT (CGN).
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 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/rfc7659.
Perreault, et al. Standards Track [Page 1]
RFC 7659 NAT MIB October 2015
Copyright Notice
Copyright (c) 2015 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. The Internet-Standard Management Framework . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. Content Provided by the NATV2-MIB Module . . . . . . . . 5
3.1.1. Configuration Data . . . . . . . . . . . . . . . . . 5
3.1.2. Notifications . . . . . . . . . . . . . . . . . . . . 6
3.1.3. State Information . . . . . . . . . . . . . . . . . . 9
3.1.4. Statistics . . . . . . . . . . . . . . . . . . . . . 9
3.2. Outline of MIB Module Organization . . . . . . . . . . . 12
3.3. Detailed MIB Module Walk-Through . . . . . . . . . . . . 13
3.3.1. Textual Conventions . . . . . . . . . . . . . . . . . 13
3.3.2. Notifications . . . . . . . . . . . . . . . . . . . . 14
3.3.3. The Subscriber Table: natv2SubscriberTable . . . . . 14
3.3.4. The Instance Table: natv2InstanceTable . . . . . . . 15
3.3.5. The Protocol Table: natv2ProtocolTable . . . . . . . 15
3.3.6. The Address Pool Table: natv2PoolTable . . . . . . . 16
3.3.7. The Address Pool Address Range Table:
natv2PoolRangeTable . . . . . . . . . . . . . . . . . 17
3.3.8. The Address Map Table: natv2AddressMapTable . . . . . 17
3.3.9. The Port Map Table: natv2PortMapTable . . . . . . . . 17
3.4. Conformance: Three Application Scenarios . . . . . . . . 18
4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 19
5. Operational and Management Considerations . . . . . . . . . . 74
5.1. Configuration Requirements . . . . . . . . . . . . . . . 74
5.2. Transition from and Coexistence with NAT-MIB (RFC 4008) . 76
6. Security Considerations . . . . . . . . . . . . . . . . . . . 78
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 81
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 81
Show full document text