VG Interface MIB RFC published
John Flick <johnf@hprnljf.rose.hp.com> Fri, 18 October 1996 00:16 UTC
Received: from cnri by ietf.org id aa11759; 17 Oct 96 20:16 EDT
Received: from hp.com by CNRI.Reston.VA.US id aa26428; 17 Oct 96 20:16 EDT
Received: from hprnd.rose.hp.com by hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA270147515; Thu, 17 Oct 1996 17:11:56 -0700
Received: from hprnljf.rose.hp.com by hprnd.rose.hp.com with ESMTP (1.37.109.18/15.5+ECS 3.3) id AA259077492; Thu, 17 Oct 1996 17:11:33 -0700
Received: from localhost by hprnljf.rose.hp.com with SMTP (1.37.109.18/15.5+ECS 3.4 ) id AA170478115; Thu, 17 Oct 1996 17:21:55 -0700
Message-Id: <199610180021.AA170478115@hprnljf.rose.hp.com>
To: vgmib@hprnd.rose.hp.com
Subject: VG Interface MIB RFC published
Date: Thu, 17 Oct 1996 17:21:55 -0700
From: John Flick <johnf@hprnljf.rose.hp.com>
For those not on the IETF announce list, the first RFC from this WG has now been published as RFC 2020. Our remaining charter item is the VG Repeater MIB. I believe the current draft (02) is finished. Speak up if you don't agree. Thanks, John ------- Forwarded Message From rfc-ed@isi.edu Thu Oct 17 17:04 PDT 1996 Received: from hpflash.rose.hp.com by hprnljf.rose.hp.com with SMTP (1.37.109.18/15.5+ECS 3.4 ) id AA169556668; Thu, 17 Oct 1996 16:57:48 -0700 Return-Path: <ietf-announce-request@ietf.org> Received: from hprnd.rose.hp.com by hpflash.rose.hp.com with SMTP (1.38.193.5/15.5+ECS 3.4 Openmail) id AA09041; Thu, 17 Oct 1996 16:46:04 -0700 Received: from hp.com by hprnd.rose.hp.com with ESMTP (1.37.109.18/15.5+ECS 3.3) id AA256446043; Thu, 17 Oct 1996 16:47:23 -0700 Received: from ietf.org by hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA240346042; Thu, 17 Oct 1996 16:47:22 -0700 Received: from ietf.org by ietf.org id aa06996; 17 Oct 96 18:49 EDT Received: from zephyr.isi.edu by ietf.org id aa06955; 17 Oct 96 18:48 EDT Received: from zephyr.isi.edu by zephyr.isi.edu (5.65c/5.61+local-23) id <AA17808>; Thu, 17 Oct 1996 15:48:00 -0700 Message-Id: <199610172248.AA17808@zephyr.isi.edu> To: IETF-Announce:;@ietf.org Subject: RFC 2020 on IEEE 802.12 Interface MIB Cc: rfc-ed@isi.edu Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 17 Oct 96 15:47:59 PDT Sender: ietf-announce-request@ietf.org From: RFC Editor <rfc-ed@isi.edu> - --NextPart A new Request for Comments is now available in online RFC libraries. RFC 2020: Title: IEEE 802.12 Interface MIB Author: J. Flick Date: October 1996 Mailbox: johnf@hprnd.rose.hp.com Pages: 31 Characters: 72,135 Updates/Obsoletes: None URL: ftp://ds.internic.net/rfc/rfc2020.txt This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing network interfaces based on IEEE 802.12. This RFC is a product of the 100VG-AnyLAN MIB Working Group of the IETF. 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@CNRI.RESTON.VA.US. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@ISI.EDU. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@ISI.EDU with the message body help: ways_to_get_rfcs. For example: To: rfc-info@ISI.EDU 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 admin@DS.INTERNIC.NET. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@ISI.EDU. Please consult RFC 1543, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Mary Kennedy 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. - --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" - --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ds.internic.net" Content-Type: text/plain Content-ID: <961017154151.RFC@ISI.EDU> SEND /rfc/rfc2020.txt - --OtherAccess Content-Type: Message/External-body; name="rfc2020.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="rfc" Content-Type: text/plain Content-ID: <961017154151.RFC@ISI.EDU> - --OtherAccess-- - --NextPart-- ------- End of Forwarded Message
- VG Interface MIB RFC published John Flick