RFC 2851 on TCs for Internet Network Addresses
RFC Editor <rfc-ed@ISI.EDU> Thu, 15 June 2000 22:14 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15832; Thu, 15 Jun 2000 18:14:20 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id SAA07662 for ietf-123-outbound.10@ietf.org; Thu, 15 Jun 2000 18:05:00 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id RAA07632 for <all-ietf@loki.ietf.org>; Thu, 15 Jun 2000 17:55:41 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15406 for <all-ietf@ietf.org>; Thu, 15 Jun 2000 17:55:37 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id OAA19472; Thu, 15 Jun 2000 14:55:39 -0700 (PDT)
Message-Id: <200006152155.OAA19472@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2851 on TCs for Internet Network Addresses
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 15 Jun 2000 14:55:39 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2851 Title: Textual Conventions for Internet Network Addresses Author(s): M. Daniele, B. Haberman, S. Routhier, J. Schoenwaelder Status: Standards Track Date: June 2000 Mailbox: daniele@zk3.dec.com, haberman@nortelnetworks.com, sar@epilogue.com, schoenw@ibr.cs.tu-bs.de Pages: 16 Characters: 32587 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ops-endpoint-mib-08.txt URL: ftp://ftp.isi.edu/in-notes/rfc2851.txt 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. This work is output from the Operations and Management Area "IPv6MIB" design team. 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 IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG 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 RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. 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.