Definitions of Managed Objects for Network Address Translators (NAT)
RFC 4008
Document | Type |
RFC - Proposed Standard
(March 2005; No errata)
Obsoleted by RFC 7658
Was draft-ietf-nat-natmib (nat WG)
|
|
---|---|---|---|
Authors | Pyda Srisuresh , R Rohit , Rajiv Raghunarayan , Nalinaksh Pai , Cliff Wang | ||
Last updated | 2015-10-14 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Stream | WG state | WG Document | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 4008 (Proposed Standard) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Allison Mankin | ||
Send notices to | (None) |
Network Working Group R. Rohit Request for Comments: 4008 Mascon Global Limited Category: Standards Track P. Srisuresh Caymas Systems, Inc. R. Raghunarayan N. Pai Cisco Systems, Inc. C. Wang Bank One Corp March 2005 Definitions of Managed Objects for Network Address Translators (NAT) Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2005). Abstract This memo defines a portion of the Management Information Base (MIB) for devices implementing Network Address Translator (NAT) function. This MIB module may be used for configuration as well as monitoring of a device capable of NAT function. Rohit, et al. Standards Track [Page 1] RFC 4008 NAT MIB March 2005 Table of Contents 1. Introduction ................................................. 2 2. The Internet-Standard Management Framework ................... 2 3. Terminology .................................................. 3 4. Overview ..................................................... 4 4.1. natInterfaceTable....................................... 4 4.2. natAddrMapTable......................................... 5 4.3. Default Timeouts, Protocol Table, and Other Scalars..... 6 4.4. natAddrBindTable and natAddrPortBindTable............... 6 4.5. natSessionTable......................................... 6 4.6. RFC 3489 NAPT Variations, NAT Session and Bind Tables... 7 4.7. Notifications........................................... 7 4.8. Relation Among Tables................................... 8 4.9. Configuration via the MIB............................... 8 4.10. Relationship to Interface MIB........................... 9 5. Definitions .................................................. 9 6. Acknowledgements ............................................. 59 7. Security Considerations ...................................... 59 8. References ................................................... 60 Authors' Addresses ............................................... 62 Full Copyright Statement.......................................... 64 1. Introduction This memo defines a portion of the Management Information Base (MIB) for devices implementing NAT function. This MIB module may be used for configuration and monitoring of a device capable of NAT function. NAT types and their characteristics are defined in[RFC2663]. Traditional NAT function, in particular is defined in [RFC3022]. This MIB does not address the firewall functions and must not be used for configuring or monitoring these. Section 2 provides references to the SNMP management framework, which was used as the basis for the MIB module definition. Section 3 describes the terms used throughout the document. Section 4 provides an overview of the key objects, their inter-relationship, and how the MIB module may be used to configure and monitor a NAT device. Lastly, section 5 has the complete NAT MIB definition. 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. 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]. Rohit, et al. Standards Track [Page 2] RFC 4008 NAT MIB March 2005 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,Show full document text