RFC 2666 on Ethernet Chipset MIB
RFC Editor <rfc-ed@ISI.EDU> Thu, 02 September 1999 18:19 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25903; Thu, 2 Sep 1999 14:19:41 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id OAA28284 for ietf-123-outbound.10@ietf.org; Thu, 2 Sep 1999 14:15:03 -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 OAA28199 for <all-ietf@loki.ietf.org>; Thu, 2 Sep 1999 14:07:01 -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 OAA25300 for <all-ietf@ietf.org>; Thu, 2 Sep 1999 14:06:58 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id LAA12090; Thu, 2 Sep 1999 11:06:59 -0700 (PDT)
Message-Id: <199909021806.LAA12090@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2666 on Ethernet Chipset MIB
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 02 Sep 1999 11:06:58 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries.
RFC 2666:
Title: Definitions of Object Identifiers for
Identifying Ethernet Chip Sets
Author(s): J. Flick
Status: Informational
Date: August 1999
Mailbox: johnf@rose.hp.com
Pages: 18
Characters: 37699
Updates:
I-D Tag: draft-ietf-hubmib-ether-chipsets-02.txt
URL: ftp://ftp.isi.edu/in-notes/rfc2666.txt
This memo defines OBJECT IDENTIFIER values for use with network
management protocols in the Internet community. In particular, it
contains registered OID values for use with the dot3StatsEtherChipSet
object in the EtherLike-MIB [16].
This document is a product of the Ethernet Interfaces and Hub MIB
Working Group of the IETF.
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. 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.
- RFC 2666 on Ethernet Chipset MIB RFC Editor