Re: [dhcwg] Last Call: draft-ietf-dhc-dhcpv6-bulk-leasequery (DHCPv6 Bulk Leasequery) to Proposed Standard

Jari Arkko <jari.arkko@piuha.net> Wed, 10 December 2008 16:01 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A70F63A6BCC; Wed, 10 Dec 2008 08:01:13 -0800 (PST)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A96633A6BC8; Wed, 10 Dec 2008 08:01:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.337
X-Spam-Level:
X-Spam-Status: No, score=-2.337 tagged_above=-999 required=5 tests=[AWL=0.262, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oMgHYb4MHQoB; Wed, 10 Dec 2008 08:01:10 -0800 (PST)
Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id BE81B3A6929; Wed, 10 Dec 2008 08:01:10 -0800 (PST)
Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id D8502198782; Wed, 10 Dec 2008 18:01:03 +0200 (EET)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id 6850B1986EF; Wed, 10 Dec 2008 18:01:03 +0200 (EET)
Message-ID: <493FE7A7.30607@piuha.net>
Date: Wed, 10 Dec 2008 18:00:39 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.18 (X11/20081125)
MIME-Version: 1.0
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Last Call: draft-ietf-dhc-dhcpv6-bulk-leasequery (DHCPv6 Bulk Leasequery) to Proposed Standard
References: <20081020123425.2DA143A69B5@core3.amsl.com> <alpine.LRH.2.00.0810210900430.31133@netcore.fi>
In-Reply-To: <alpine.LRH.2.00.0810210900430.31133@netcore.fi>
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

I wanted to send a message about my conclusion of this thread, as the 
draft is now progressing to IESG review.

I sympathize with the desire to pull as much data as possible with a 
simple request and no prior knowledge of what sessions exist. I think it 
is obvious that with a better understanding of how to use SNMP, we can 
avoid the silliest approach to pulling data -- I hope there is a way to 
provide better education on how to use SNMP for something like this. But 
I'm not expert enough to say whether you can reach exactly an equivalent 
model as this draft has. Maybe.

Nevertheless, it is clear to me that there is consensus in the WG to do 
this. They are chartered to do infrastructure improvements (such as this 
one) to DHCP. There are customers who need to do this. The last call 
discussion has raised alternative ways to implement this but no specific 
problems in the current approach. I believe that in this case we need to 
let the WG use the approach they have chosen. More generally, I believe 
that if there are specific data access needs in applications for large 
volume, bulk, etc -- the WGs in charge of those applications can choose 
the approach they want to use for the access to the data. While most of 
our management needs are fulfilled by MIBs, I do not think we can 
preclude other solutions for specialized situations, such as recovering 
DHCP session data.

Jari

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf