RFC 3019 on MIB for MLD
RFC Editor <rfc-ed@ISI.EDU> Thu, 01 February 2001 17:54 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04571; Thu, 1 Feb 2001 12:54:19 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id MAA28622 for ietf-123-outbound.10@ietf.org; Thu, 1 Feb 2001 12:45:01 -0500 (EST)
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 MAA28575 for <all-ietf@loki.ietf.org>; Thu, 1 Feb 2001 12:40:02 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA04043 for <all-ietf@ietf.org>; Thu, 1 Feb 2001 12:40:02 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id JAA13847; Thu, 1 Feb 2001 09:40:02 -0800 (PST)
Message-Id: <200102011740.JAA13847@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 3019 on MIB for MLD
Cc: rfc-ed@ISI.EDU, ipng@sunroof.eng.sum.com.cnri.reston.va
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 01 Feb 2001 09:40:02 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 3019 Title: IP Version 6 Management Information Base for The Multicast Listener Discovery Protocol Author(s): B. Haberman, R. Worzella Status: Standards Track Date: January 2001 Mailbox: haberman@nortelnetworks.com, worzella@us.ibm.com Pages: 15 Characters: 28293 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ipngwg-mld-mib-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3019.txt This document defines a portion of the Management Information Base (MIB) for use with network management protocols in Internet Protocol Version 6 internets. Specifically, this document is the MIB module that defines managed objects for implementations of the Multicast Listener Discovery Protocol. This document is a product of the IPNG 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.
- RFC 3019 on MIB for MLD RFC Editor