Document Action: 'Multicast Source Discovery protocol MIB' to Experimental RFC

The IESG <iesg-secretary@ietf.org> Tue, 04 April 2006 00:03 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FQZ1C-0008Fy-D9; Mon, 03 Apr 2006 20:03:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FQZ1A-0008Fq-V2; Mon, 03 Apr 2006 20:03:32 -0400
Received: from willow.neustar.com ([209.173.53.84]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FQZ19-0005Qg-Mp; Mon, 03 Apr 2006 20:03:32 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by willow.neustar.com (8.12.8/8.12.8) with ESMTP id k3403U9W010850 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 4 Apr 2006 00:03:30 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1FQZ18-0002X4-Qm; Mon, 03 Apr 2006 20:03:30 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1FQZ18-0002X4-Qm@stiedprstage1.ietf.org>
Date: Mon, 03 Apr 2006 20:03:30 -0400
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Cc: mboned mailing list <mboned@lists.uoregon.edu>, Internet Architecture Board <iab@iab.org>, mboned chair <ohta.hiroshi@lab.ntt.co.jp>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: Document Action: 'Multicast Source Discovery protocol MIB' to Experimental RFC
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org
Status: O

The IESG has approved the following document:

- 'Multicast Source Discovery protocol MIB '
   <draft-ietf-mboned-msdp-mib-01.txt> as an Experimental RFC

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

The IESG contact persons are Dan Romascanu and David Kessens.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mboned-msdp-mib-01.txt

Technical Summary
 
 This memo defines an experimental 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 Multicast Source Discovery Protocol (MSDP) (RFC 3618) speakers.
 
Working Group Summary
 
 The WG has consensus to publish this document as an Experimental RFC.
 There are existing implementations of this MIB module, which date back 
 several years, and so usage of IpAddress SYNTAX and DisplayString
 in this (experimental) MIB module is a conscious decision and acceptable 
 at experimental level. The implementations are specific for IPv4 and so
 is the MIB module.
 
Protocol Quality
 
 Quick check with MIB doctors list for this experiment was done.
 Bert Wijnen reviewed this document for the IESG.

Note to RFC Editor

- page 6, Section 3:

OLD: 
    the Source-Active Cache Table, containing the SA cache entries; and
NEW: 
    the Source-Active (SA) Cache Table, containing the SA cache entries; and
 
- bottom of page 6, change module name:

 OLD:
     DRAFT-MSDP-MIB DEFINITIONS ::= BEGIN
 NEW:
     MSDP-MIB DEFINITIONS ::= BEGIN

- on page 8, in the DESCRIPTION clause of msdpCacheLifetime

 OLD: 
            This object does not measure time per se; instead, it is the
            delta from the time at which an SA message is received at
            which it should be expired if not refreshed.  (i.e., it is
            the value of msdpSACacheExpiryTime immediately after
            receiving an SA message applying to that row.)  As such,
            TimeInterval would be a more appropriate SYNTAX; it remains
            TimeTicks for backwards compatability."

 NEW:
            This object does not measure time per se; instead, it is the
            delta from the time at which an SA message is received at
            which it should be expired if not refreshed.  (i.e., it is
            the value of msdpSACacheExpiryTime immediately after
            receiving an SA message applying to that row.)  As such,
            TimeInterval would be a more appropriate SYNTAX; it remains
            TimeTicks for backwards compatibility."

- on page 9, DESCRIPTION clause of msdpRPAddress

OLD: 
            The RP address used when sourcing MSDP SA messages.  May be
            0.0.0.0 on non-RP's.

NEW: 
            The Rendezvous Point (RP) address used when sourcing MSDP SA 
            messages.  May be 0.0.0.0 on non-RP's.

- On page 10 at the bootom, replace:

  OLD:
   msdpRequestsStatus OBJECT-TYPE
       SYNTAX     RowStatus
       MAX-ACCESS read-create
  NEW:
   msdpRequestsStatus OBJECT-TYPE
       SYNTAX     RowStatus { active(1), destroy(6) }
       MAX-ACCESS read-create

- on page 32 at the top, replace:

OLD: 
SNMPv1 by itself is not a secure environment.  Even if the network
itself is secure (for example by using IPSec), even then, there is no
control as to who on the secure network is allowed to access and GET/SET
(read/change/create/delete) the objects in this MIB.
NEW:
SNMPv1 by itself is not a secure environment.  Even if the network
itself is secure (for example by using IPsec), even then, there is no
control as to who on the secure network is allowed to access and GET/SET
(read/change/create/delete) the objects in this MIB.

IANA Note

Since this MIB is for an experimental protocol, it uses an experimental
OID.

Decimal   Name          Description                     References
-------   ----          -----------                     ----------
     92   MSDP-MIB     Multicast Source Discovery MIB     [Fenner]

The IANA is requested to change the Reference for this entry to point to
this document.


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce