RFC 2417 on Multicast MIB

RFC Editor <rfc-ed@ISI.EDU> Wed, 09 September 1998 17:55 UTC

Message-Id: <199809091745.KAA27680@tnt.isi.edu>
To: IETF-Announce:;
Subject: RFC 2417 on Multicast MIB
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 09 Sep 1998 10:43:46 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

A new Request for Comments is now available in online RFC libraries.


        RFC 2417:

        Title:      Definitions of Managed Objects for
                    Multicast over UNI 3.0/3.1 based ATM Networks
	Author(s):  C. Chung, M. Greene
	Status:     Proposed Standard
	Date:       September 1998
        Mailbox:    chihschung@aol.com, maria@xedia.com
        Characters: 134862
        Obsoletes:  2366

        URL:        ftp://ftp.isi.edu/in-notes/rfc2417.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 for IP hosts and routers
that use a Multicast Address Resolution Server (MARS) to support IP
multicast over ATM, as described in 'Support for Multicast over UNI
3.0/3.1 based ATM Networks'.  This memo specifies a MIB module in a
manner that is both compliant to the SNMPv2 SMI, and semantically
identical to the peer SNMPv1 definitions.

This document 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 Alegre Ramos
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.

ftp://ftp.isi.edu/in-notes/rfc2417.txt"><ftp://ftp.isi.edu/in-notes/rfc2417.txt>

RFC 2417 on Multicast MIB RFC Editor