From ifmib-admin@ietf.org Mon Nov 17 18:28:49 2003 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13539; Mon, 17 Nov 2003 18:28:48 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ALsnk-0001G6-00; Mon, 17 Nov 2003 18:29:00 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ALsnj-0001Fz-00; Mon, 17 Nov 2003 18:28:59 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ALsnk-0007Q7-Nu; Mon, 17 Nov 2003 18:29:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19xUR4-00069K-Td for ifmib@optimus.ietf.org; Thu, 11 Sep 2003 12:36:46 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00316; Thu, 11 Sep 2003 12:36:38 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19xUR2-00039d-00; Thu, 11 Sep 2003 12:36:44 -0400 Received: from smtpout1.bayarea.net ([209.128.95.10]) by ietf-mx with esmtp (Exim 4.12) id 19xUR1-00039S-00; Thu, 11 Sep 2003 12:36:43 -0400 Received: from shell4.bayarea.net (shell4.BAYAREA.NET [209.128.82.1]) by smtpout1.bayarea.net (8.12.8/8.12.8) with ESMTP id h8BGdUhs006450; Thu, 11 Sep 2003 09:39:31 -0700 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h8BGae207751; Thu, 11 Sep 2003 09:36:40 -0700 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Thu, 11 Sep 2003 09:36:40 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: mibs@ops.ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [ifmib] (no subject) Sender: ifmib-admin@ietf.org Errors-To: ifmib-admin@ietf.org X-BeenThere: ifmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Interfaces MIB working group mailing list. List-Post: List-Help: List-Subscribe: , [ NOTE: replies to sender, public comments to mibs@ops.ietf.org ] Colleagues -- As those of you who saw the recent announcement on the IETF-Announce list will know, instead of getting rechartered and reactivated the ifmib WG got closed down. That leaves the IF-MIB (RFC 2863) at Draft Standard and the IF-INVERTED-STACK-MIB (RFC 2864) at Proposed Standard. It occurred to me that a useful interim step would be to collect the implementation reports needed to advance RFC 2864 to Draft Standard, and I have volunteered to do just that. So, if you or your organization has implemented the IF-INVERTED-STACK-MIB, I would appreciate it if you would fill out the following template and return it to me. If you would prefer that your company's name not be made public, please so indicate and its name will be omitted from the public version of the implementation report (although it must be disclosed to the IESG in order for the data to be included). Note that the template below is intended to evaluate conformance to the ifInvCompliance compliance statement, and consequently requests information not only on the ifInvStackTable but also on the ifStackTable and ifStackLastChange, which are defined in IF-MIB. Since ifInvCompliance does not have an OBJECT clause that specifies a MIN-ACCESS of read-only for ifStackStatus, it would be of particular interest to hear of implementations that actually provide read-create access to that object. In the template below please fill in the items in angle brackets and if the information is available please attach the results of a MIB dump of ifStackStatus, ifStackTable, and ifInvStackTable (cf. RFC 2438). I will put together a summary of the information that is received and forward it to the IESG. Regards, Mike Heard ================================================================= Vendor implementation report for RFC 2864 (IF-INVERTED-STACK-MIB) Evaluation of compliance statement ifInvCompliance Legend: yes - implemented, no - not implemented, ro - implemented as read-only Vendor info as of ifInvStackGroup (this module) ifInvStackStatus ifStackGroup2 (IF-MIB) ifStackStatus ifStackLastChange _______________________________________________ ifmib mailing list ifmib@ietf.org https://www1.ietf.org/mailman/listinfo/ifmib From ifmib-admin@ietf.org Mon Nov 17 18:50:47 2003 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14360; Mon, 17 Nov 2003 18:50:46 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ALt90-0001hd-00; Mon, 17 Nov 2003 18:50:58 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ALt8z-0001ha-00; Mon, 17 Nov 2003 18:50:57 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ALt91-0000El-Oc; Mon, 17 Nov 2003 18:50:59 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABsxv-0006ld-06 for ifmib@optimus.ietf.org; Tue, 21 Oct 2003 05:38:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11297; Tue, 21 Oct 2003 05:37:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABsxr-0001Y1-00; Tue, 21 Oct 2003 05:38:07 -0400 Received: from netcore.fi ([193.94.160.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABsxp-0001XH-00; Tue, 21 Oct 2003 05:38:06 -0400 Received: from localhost (pekkas@localhost) by netcore.fi (8.11.6/8.11.6) with ESMTP id h9L9bVC26462; Tue, 21 Oct 2003 12:37:32 +0300 Date: Tue, 21 Oct 2003 12:37:31 +0300 (EEST) From: Pekka Savola To: Dave Thaler cc: ipv6@ietf.org, , In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [ifmib] Re: FW: I-D ACTION:draft-thaler-inet-tunnel-mib-00.txt Sender: ifmib-admin@ietf.org Errors-To: ifmib-admin@ietf.org X-BeenThere: ifmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Interfaces MIB working group mailing list. List-Post: List-Help: List-Subscribe: , On Wed, 15 Oct 2003, Dave Thaler wrote: > Forwarding this announcement to the most relevant WG's... > > RFC 2667, entitled "IP Tunnel MIB", only supported > point-to-point tunnels over IPv4. This draft updates > RFC 2667 to also support tunnels over IPv6, as well as > tunnels which aren't just point-to-point (e.g. 6to4). > It also clarifies the use of the ifRcvAddressTable > for all tunnels. > > It uses the InetAddress types like the other MIBs > that have been done by the IPv6MIB Design Team. Thanks Dave. Two very high-level comments. An obvious oversight (or intentional one :-) is that I see an IANA registry being created, but no guidance on how new values should be added to it (IETF Consensus, Standards Action, FCFS, etc.) Also, it was not clear which WG you intend to run this through officially. I'm assuming ifmib. (Just trying to figure out what will be the role of v6ops WG in this process..) Pekka > Title : IP Tunnel MIB > Author(s) : D. Thaler > Filename : draft-thaler-inet-tunnel-mib-00.txt > Pages : 26 > Date : 2003-10-14 > > This memo defines a Management Information Base (MIB) for use with > network management protocols in the Internet community. In > particular, it describes managed objects used for managing tunnels > of any type over IPv4 and IPv6 networks. Extension MIBs may be > designed for managing protocol-specific objects. Likewise, > extension MIBs may be designed for managing security-specific > objects. This MIB does not support tunnels over non-IP networks. > Management of such tunnels may be supported by other MIBs. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-thaler-inet-tunnel-mib-00.txt [...] -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings _______________________________________________ ifmib mailing list ifmib@ietf.org https://www1.ietf.org/mailman/listinfo/ifmib