RFC 2934 on Protocol Independent Multicast MIB for IPv4
RFC Editor <rfc-ed@ISI.EDU> Fri, 06 October 2000 23:57 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15059; Fri, 6 Oct 2000 19:57:44 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id TAA23234 for ietf-123-outbound.10@ietf.org; Fri, 6 Oct 2000 19:55:02 -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 TAA23005 for <all-ietf@loki.ietf.org>; Fri, 6 Oct 2000 19:12: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 SMTP id TAA14554 for <all-ietf@ietf.org>; Fri, 6 Oct 2000 19:12:40 -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 QAA25532; Fri, 6 Oct 2000 16:12:39 -0700 (PDT)
Message-Id: <200010062312.QAA25532@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2934 on Protocol Independent Multicast MIB for IPv4
Cc: rfc-ed@ISI.EDU, idmf@CS.UCL.AC.UK
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 06 Oct 2000 16:12:39 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries.
RFC 2934
Title: Protocol Independent Multicast MIB for IPv4
Author(s): K. McCloghrie, D. Farinacci, D. Thaler, B. Fenner
Status: Experimental
Date: October 2000
Mailbox: kzm@cisco.com, dino@procket.com,
dthaler@microsoft.com, fenner@research.att.com
Pages: 26
Characters: 48379
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-idmr-pim-mib-11.txt
URL: ftp://ftp.isi.edu/in-notes/rfc2934.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 the
Protocol Independent Multicast (PIM) protocol for IPv4.
This document is a product of the Inter-Domain Multicast Routing
Working Group of the IETF.
This memo defines an Experimental Protocol for the Internet community.
It does not specify an Internet standard of any kind. Discussion and
suggestions for improvement are requested. 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.