From ifmib-admin@ietf.org Tue Jun 27 20:15:46 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27426; Tue, 27 Jun 2000 20:15:46 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA06064; Tue, 27 Jun 2000 20:08:21 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA06044 for ; Tue, 27 Jun 2000 20:08:20 -0400 (EDT) Received: from foxhound.cisco.com (foxhound.cisco.com [171.69.192.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27217 for ; Tue, 27 Jun 2000 20:08:19 -0400 (EDT) Received: (from kzm@localhost) by foxhound.cisco.com (8.8.8/2.5.1/Cisco List Logging/8.8.8) id RAA10302 for ifmib@ietf.org; Tue, 27 Jun 2000 17:07:54 -0700 (PDT) From: Keith McCloghrie Message-Id: <200006280007.RAA10302@foxhound.cisco.com> To: ifmib@ietf.org Date: Tue, 27 Jun 2000 17:07:54 -0700 (PDT) X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [ifmib] RFC 2863 on The Interfaces Group MIB (fwd) Sender: ifmib-admin@ietf.org Errors-To: ifmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IETF Interfaces MIB working group mailing list. X-BeenThere: ifmib@ietf.org Content-Transfer-Encoding: 7bit FYI. Keith. ---------- Forwarded message: > From rfc-ed@ISI.EDU Tue Jun 27 17:04:27 2000 > Date: Tue, 27 Jun 2000 16:25:56 -0700 > To: IETF-Announce: ; > Subject: RFC 2863 on The Interfaces Group MIB > Cc: rfc-ed@ISI.EDU, if-mib@vnd.tek.com > > --NextPart > > > A new Request for Comments is now available in online RFC libraries. > > > RFC 2863 > > Title: The Interfaces Group MIB > Author(s): K. McCloghrie, F. Kastenholz > Status: Standards Track > Date: June 2000 > Mailbox: kzm@cisco.com, kasten@argon.com > Pages: 69 > Characters: 155014 > Obsoletes: 2233 > > I-D Tag: draft-ietf-ifmib-ifmib2-03.txt > > URL: ftp://ftp.isi.edu/in-notes/rfc2863.txt > > > This memo defines a portion of the Management Information Base (MIB) > for use with network management protocols in the Internet community. > In particular, it describes managed objects used for managing Network > Interfaces. This memo discusses the \'interfaces' group of MIB-II > [17], especially the experience gained from the definition of numerous > media-specific MIB modules for use in conjunction with the > 'interfaces' group for managing various sub-layers beneath the > internetwork-layer. It specifies clarifications to, and extensions > of, the architectural issues within the MIB-II model of the > 'interfaces' group. This memo obsoletes RFC 2233, the previous > version of the Interfaces Group MIB. > > This document is a product of the Interfaces MIB Working Group of the > IETF. > > This is now a Draft 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. > > --NextPart > Content-Type: Multipart/Alternative; Boundary="OtherAccess" > > --OtherAccess > Content-Type: Message/External-body; > access-type="mail-server"; > server="RFC-INFO@RFC-EDITOR.ORG" > > Content-Type: text/plain > Content-ID: <000627161849.RFC@RFC-EDITOR.ORG> > > RETRIEVE: rfc > DOC-ID: rfc2863 > > --OtherAccess > Content-Type: Message/External-body; > name="rfc2863.txt"; > site="ftp.isi.edu"; > access-type="anon-ftp"; > directory="in-notes" > > Content-Type: text/plain > Content-ID: <000627161849.RFC@RFC-EDITOR.ORG> > > --OtherAccess-- > --NextPart-- > > > _______________________________________________ ifmib mailing list ifmib@ietf.org http://www1.ietf.org/mailman/listinfo/ifmib From ifmib-admin@ietf.org Tue Jun 27 20:25:10 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27580; Tue, 27 Jun 2000 20:25:10 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA06145; Tue, 27 Jun 2000 20:18:08 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA06120 for ; Tue, 27 Jun 2000 20:18:06 -0400 (EDT) Received: from foxhound.cisco.com (foxhound.cisco.com [171.69.192.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27460 for ; Tue, 27 Jun 2000 20:18:05 -0400 (EDT) Received: (from kzm@localhost) by foxhound.cisco.com (8.8.8/2.5.1/Cisco List Logging/8.8.8) id RAA10518 for ifmib@ietf.org; Tue, 27 Jun 2000 17:17:40 -0700 (PDT) From: Keith McCloghrie Message-Id: <200006280017.RAA10518@foxhound.cisco.com> To: ifmib@ietf.org Date: Tue, 27 Jun 2000 17:17:40 -0700 (PDT) X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [ifmib] RFC 2864 on Inverted Stack Extension MIB (fwd) Sender: ifmib-admin@ietf.org Errors-To: ifmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IETF Interfaces MIB working group mailing list. X-BeenThere: ifmib@ietf.org Content-Transfer-Encoding: 7bit FYI. Keith. ------------ Forwarded message: > From: RFC Editor > Date: Tue, 27 Jun 2000 16:29:05 -0700 > To: IETF-Announce: ; > Subject: RFC 2864 on Inverted Stack Extension MIB > Cc: rfc-ed@ISI.EDU, if-mib@vnd.tek.com > > --NextPart > > > A new Request for Comments is now available in online RFC libraries. > > > RFC 2864 > > Title: The Inverted Stack Table Extension to the > Interfaces Group MIB > Author(s): K. McCloghrie, G. Hanson > Status: Standards Track > Date: June 2000 > Mailbox: kzm@cisco.com, gary_hanson@adc.com > Pages: 11 > Characters: 21445 > Updates/Obsoletes/SeeAlso: None > > I-D Tag: draft-ietf-ifmib-invstackmib-03.txt > > URL: ftp://ftp.isi.edu/in-notes/rfc2864.txt > > > This memo defines a portion of the Management Information Base (MIB) > for use with network management protocols in the Internet community. > In particular, it describes managed objects which provide an inverted > mapping of the interface stack table used for managing network > interfaces. > > This document is a product of the Interfaces 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@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. > > --NextPart > Content-Type: Multipart/Alternative; Boundary="OtherAccess" > > --OtherAccess > Content-Type: Message/External-body; > access-type="mail-server"; > server="RFC-INFO@RFC-EDITOR.ORG" > > Content-Type: text/plain > Content-ID: <000627162635.RFC@RFC-EDITOR.ORG> > > RETRIEVE: rfc > DOC-ID: rfc2864 > > --OtherAccess > Content-Type: Message/External-body; > name="rfc2864.txt"; > site="ftp.isi.edu"; > access-type="anon-ftp"; > directory="in-notes" > > Content-Type: text/plain > Content-ID: <000627162635.RFC@RFC-EDITOR.ORG> > > --OtherAccess-- > --NextPart-- > > > _______________________________________________ ifmib mailing list ifmib@ietf.org http://www1.ietf.org/mailman/listinfo/ifmib