VG Interface MIB RFC published

[John Flick <[e-mail]>]

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 [e-mail] 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: <[e-mail]>
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: <[e-mail]>
To: IETF-Announce:;@ietf.org
Subject: RFC 2020 on IEEE 802.12 Interface MIB
Cc: [e-mail]
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Thu, 17 Oct 96 15:47:59 PDT
Sender: [e-mail]
From: RFC Editor <[e-mail]>


- --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:    [e-mail]
        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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should be sent
to [e-mail].

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

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  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="[e-mail]"

Content-Type: text/plain
Content-ID: <[e-mail]>

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: <[e-mail]>

- --OtherAccess--
- --NextPart--


------- End of Forwarded Message