RFC 4008: Definitions of Managed Objects for Network Address Translators (NAT)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7658.
Current version: RFC 7658 — Deprecation of MIB Module NAT-MIB: Managed Objects for Network Address Translators (NATs)
In plain English — editorial summary, not part of the RFC
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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4008
- Published
- March 2005
- Authors
- R. Rohit; P. Srisuresh; R. Raghunarayan; N. Pai; C. Wang
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 64
- Also known as
- —
- Obsoleted by:
- RFC 7658
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3816Definitions of Managed Objects for RObust Header Compression (ROHC)Current
June 2004
- RFC 4369Definitions of Managed Objects for Internet Fibre Channel Protocol (iFCP)Obsoleted
January 2006
- RFC 4404Definitions of Managed Objects for Fibre Channel Over TCP/IP (FCIP)Current
February 2006
- RFC 4455Definition of Managed Objects for Small Computer System Interface (SCSI) EntitiesCurrent
April 2006
- RFC 3559Multicast Address Allocation MIBCurrent
June 2003
- RFC 4545Definitions of Managed Objects for IP Storage User Identity AuthorizationCurrent
May 2006
- RFC 3289Management Information Base for the Differentiated Services ArchitectureCurrent
June 2002
- RFC 4939Definitions of Managed Objects for iSNS (Internet Storage Name Service)Current
July 2007
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?