RE: [dhcwg] WG last call on draft-ietf-dhc-server-mib-08 (2nd las t call)
"Woundy, Richard" <Richard_Woundy@cable.comcast.com> Tue, 01 July 2003 19:11 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12368; Tue, 1 Jul 2003 15:11:15 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XQVw-0002IO-Uf; Tue, 01 Jul 2003 15:10:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XQVK-0002Bt-Da for dhcwg@optimus.ietf.org; Tue, 01 Jul 2003 15:09:26 -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 PAA12058 for <dhcwg@ietf.org>; Tue, 1 Jul 2003 15:09:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XQUv-0007Cf-00 for dhcwg@ietf.org; Tue, 01 Jul 2003 15:09:01 -0400
Received: from coral.tci.com ([198.178.8.81] helo=saipal.tci.com) by ietf-mx with esmtp (Exim 4.12) id 19XQUu-0007C6-00 for dhcwg@ietf.org; Tue, 01 Jul 2003 15:09:00 -0400
Received: from entexchimc04.broadband.att.com (localhost [127.0.0.1]) by saipal.tci.com (8.12.9/8.12.9) with ESMTP id h61J78KF018331; Tue, 1 Jul 2003 13:07:08 -0600 (MDT)
Received: by entexchimc04.broadband.att.com with Internet Mail Service (5.5.2653.19) id <MM05GTD9>; Tue, 1 Jul 2003 13:07:07 -0600
Message-ID: <6732623D2548D61193C90002A5C88DCC05663C94@entmaexch02.broadband.att.com>
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: dhcwg@ietf.org
Cc: 'Ralph Droms' <rdroms@cisco.com>, "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
Subject: RE: [dhcwg] WG last call on draft-ietf-dhc-server-mib-08 (2nd las t call)
Date: Tue, 01 Jul 2003 13:07:04 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Ralph, I concur with moving the DHCPv4 MIB forward, with the following two minor comments. 1. If the editing opportunity arises, we should change the name of the sequence "ServerRangeEntry" to "Dhcpv4ServerRangeEntry", per the suggested naming conventions of Appendix E of draft-ietf-ops-mib-review-guidelines-01.txt. Here is the corresponding MIB compiler warning (which is not an error): W: f(DHCP-SERVER-MIB.mi2), (922,9) Sequence "ServerRangeEntry" and Row "dhcpv4ServerRangeEntry" should have related names 2. There are several accessible-for-notify objects that are not used in any notifications: dhcpv4ServerSharedNetReservedAddresses dhcpv4ServerSharedNetTotalAddresses dhcpv4ServerSubnetFreeAddrLowThreshold dhcpv4ServerSubnetFreeAddrHighThreshold dhcpv4ServerSubnetFreeAddresses It is a little odd to define objects like these, but not strictly an error. -- Rich -----Original Message----- From: Ralph Droms [mailto:rdroms@cisco.com] Sent: Tuesday, June 10, 2003 9:30 PM To: dhcwg@ietf.org Subject: [dhcwg] WG last call on draft-ietf-dhc-server-mib-08 (2nd last call) The last call on draft-ietf-dhc-server-mib-08 will end on Monday, July 7. -------------- - Ralph _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- RE: [dhcwg] WG last call on draft-ietf-dhc-server… Glenn Waters
- RE: [dhcwg] WG last call on draft-ietf-dhc-server… Woundy, Richard