RFC 4008 on Definitions of Managed Objects for Network Address Translators (NAT) (fwd)

It finally made it to an RFC and the MIDCOM protocol evaluation should
follow soon.

  Martin

------------ Forwarded Message ------------
Date: Dienstag, 22. März 2005 16:28 Uhr -0800
From: [email protected]
To: [email protected]
Cc: [email protected]
Subject: RFC 4008 on Definitions of Managed Objects for Network Address 
Translators (NAT)


A new Request for Comments is now available in online RFC libraries.


        RFC 4008

        Title:      Definitions of Managed Objects for
                    Network Address Translators (NAT)
        Author(s):  R. Rohit, P. Srisuresh, R. Raghunarayan, N. Pai,
                    C. Wang
        Status:     Standards Track
        Date:       March 2005
        Mailbox:    [email protected], [email protected],
                    [email protected], [email protected],
                    [email protected]
        Pages:      64
        Characters: 125696
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-nat-natmib-09.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4008.txt


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.

This is now a Proposed Standard Protocol.

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.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to [email protected].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [email protected].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [email protected] with the message body
help: ways_to_get_rfcs.  For example:

        To: [email protected]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[email protected].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.

---------- End Forwarded Message ----------

_______________________________________________
midcom mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/midcom