[ipcdn] Fwd: I-D ACTION:draft-ietf-ops-rfc2851-update-00.txt

Rich Woundy <rwoundy@cisco.com> Tue, 27 February 2001 21:45 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA01259; Tue, 27 Feb 2001 16:45:57 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA02799; Tue, 27 Feb 2001 16:23:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA02774 for <ipcdn@ns.ietf.org>; Tue, 27 Feb 2001 16:23:24 -0500 (EST)
Received: from funnel.cisco.com (funnel.cisco.com [161.44.131.24]) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA00462 for <ipcdn@ietf.org>; Tue, 27 Feb 2001 16:23:21 -0500 (EST)
Received: from rwoundy-w2k.cisco.com (ch2-dhcp133-73.cisco.com [161.44.133.73]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id QAA02207 for <ipcdn@ietf.org>; Tue, 27 Feb 2001 16:22:51 -0500 (EST)
Message-Id: <4.3.2.7.2.20010227160238.01988fc8@funnel.cisco.com>
X-Sender: rwoundy@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 27 Feb 2001 16:23:34 -0500
To: ipcdn@ietf.org
From: Rich Woundy <rwoundy@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Subject: [ipcdn] Fwd: I-D ACTION:draft-ietf-ops-rfc2851-update-00.txt
Sender: ipcdn-admin@ietf.org
Errors-To: ipcdn-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
X-BeenThere: ipcdn@ietf.org

Folks,

Several MIB writers in our WG are updating documents to use the 
IPv6-friendly InetAddressType and InetAddress SYNTAXes from RFC 2851 -- 
this includes the updates to RFC 2669 and 2670, the Euromodem NIU MIB, the 
Subscriber Management MIB, and others.

Note that RFC 2851 is being revised. I understand that it is not a 
requirement to use this revision, but some folks might find it interesting 
to read.

-- Rich

>To: IETF-Announce:;
>From: Internet-Drafts@ietf.org
>Reply-to: Internet-Drafts@ietf.org
>Subject: I-D ACTION:draft-ietf-ops-rfc2851-update-00.txt
>Date: Fri, 23 Feb 2001 06:45:48 -0500
>Sender: nsyracus@cnri.reston.va.us
>
>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
>This draft is a work item of the Operations & Management Open Area Working 
>Group of the IETF.
>
>         Title           : Textual Conventions for Internet Network Addresses
>         Author(s)       : M. Daniele et al.
>         Filename        : draft-ietf-ops-rfc2851-update-00.txt
>         Pages           : 19
>         Date            : 22-Feb-01
>
>This MIB module defines textual conventions to represent commonly
>used Internet network layer addressing information. The intent is
>that these definitions will be imported and used in MIBs that would
>otherwise define their own representations.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-ops-rfc2851-update-00.txt
>
>Internet-Drafts are also available by anonymous FTP. Login with the username
>"anonymous" and a password of your e-mail address. After logging in,
>type "cd internet-drafts" and then
>         "get draft-ietf-ops-rfc2851-update-00.txt".
>
>A list of Internet-Drafts directories can be found in
>http://www.ietf.org/shadow.html
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>Internet-Drafts can also be obtained by e-mail.
>
>Send a message to:
>         mailserv@ietf.org.
>In the body type:
>         "FILE /internet-drafts/draft-ietf-ops-rfc2851-update-00.txt".
>
>NOTE:   The mail server at ietf.org can return the document in
>         MIME-encoded form by using the "mpack" utility.  To use this
>         feature, insert the command "ENCODING mime" before the "FILE"
>         command.  To decode the response(s), you will need "munpack" or
>         a MIME-compliant mail reader.  Different MIME-compliant mail readers
>         exhibit different behavior, especially when dealing with
>         "multipart" MIME messages (i.e. documents which have been split
>         up into multiple messages), so check your local documentation on
>         how to manipulate these messages.
>
>
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version of the
>Internet-Draft.
>Content-Type: text/plain
>Content-ID:     <20010222135549.I-D@ietf.org>
>
>ENCODING mime
>FILE /internet-drafts/draft-ietf-ops-rfc2851-update-00.txt
>
><ftp://ftp.ietf.org/internet-drafts/draft-ietf-ops-rfc2851-update-00.txt>



_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
http://www1.ietf.org/mailman/listinfo/ipcdn