Protocol Action: 'IP Multicast MIB' to Proposed Standard

The IESG <> Tue, 25 September 2007 00:18 UTC

Return-path: <>
Received: from [] ( by with esmtp (Exim 4.43) id 1IZy8G-0001Gy-LO; Mon, 24 Sep 2007 20:18:32 -0400
Received: from [] ( by with esmtp (Exim 4.43) id 1IZy8D-00017T-Ub; Mon, 24 Sep 2007 20:18:30 -0400
Received: from ([]) by with esmtp (Exim 4.43) id 1IZy8D-0004c5-9v; Mon, 24 Sep 2007 20:18:29 -0400
Received: from ( []) by (Postfix) with ESMTP id 25F452AC81; Tue, 25 Sep 2007 00:17:59 +0000 (GMT)
Received: from ietf by with local (Exim 4.43) id 1IZy7i-0000z5-FX; Mon, 24 Sep 2007 20:17:58 -0400
X-test-idtracker: no
From: The IESG <>
To: IETF-Announce <>
Message-Id: <>
Date: Mon, 24 Sep 2007 20:17:58 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: mboned mailing list <>, mboned chair <>, Internet Architecture Board <>, RFC Editor <>
Subject: Protocol Action: 'IP Multicast MIB' to Proposed Standard
X-Mailman-Version: 2.1.5
Precedence: list
List-Unsubscribe: <>, <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>

The IESG has approved the following document:

- 'IP Multicast MIB '
   <draft-ietf-mboned-ip-mcast-mib-07.txt> as a Proposed Standard

This document is the product of the MBONE Deployment Working Group. 

The IESG contact persons are Dan Romascanu and Ron Bonica.

A URL of this Internet-Draft is:

Technical Summary
   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 objects used for managing multicast
   function, independent of the specific multicast protocol(s) in use.
   This document obsoletes RFC 2932.
Working Group Summary
   There was strong support in the MBONED WG for the adoption of this
   document. There was a general consensus that this MIB addition was
Protocol Quality
   This document is largely based on RFC2932 and will make it obsolete. 

   There are many implementations of RFC2932 and there are 
   implementations of earlier versions of this draft. Cisco Systems has  
   implemented an earlier version of this draft and Data Connection Ltd 
   has implemented a version of this draft. 

   The document has been reviewed by MIB Doctors Keith McCloghrie and 
Bert Wijnen and by Area Director Dan Romascanu.

Note to RFC Editor
1. In the compliance statements of the MIB module in Section 6, please 
   delete the lines that say 
        MIN-ACCESS read-only
   for the following objects:
        ipMcastRouteUpstreamNeighborType - page 46
        ipMcastRouteUpstreamNeighbor - page 46
        ipMcastRouteRtAddressType - page 46
        ipMcastRouteRtAddress - page 46
        ipMcastZoneScopeAddressType - page 51
        ipMcastZoneScopeAddress - page 52

2. page 56, Section 7.2, please delete ipMcastScopeNameTable from the 
   list of read-write and read-create objects.

IETF-Announce mailing list