Re: [dhcwg] Ben Campbell's No Objection on draft-ietf-dhc-dhcpv6-active-leasequery-03: (with COMMENT)

"Ben Campbell" <ben@nostrum.com> Fri, 10 July 2015 22:22 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 303A01A0022; Fri, 10 Jul 2015 15:22:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zP1Lw3QwK2Lz; Fri, 10 Jul 2015 15:22:32 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 981B01A00C8; Fri, 10 Jul 2015 15:20:04 -0700 (PDT)
Received: from [10.0.1.23] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id t6AMJKpw090589 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 10 Jul 2015 17:19:30 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.23]
From: Ben Campbell <ben@nostrum.com>
To: Kim Kinnear <kkinnear@cisco.com>
Date: Fri, 10 Jul 2015 17:19:20 -0500
Message-ID: <EC658923-A12A-47F9-8224-7821288CF746@nostrum.com>
In-Reply-To: <55D32D35-C674-49AD-ADA9-1818F6BCFB16@cisco.com>
References: <20150707230048.2247.54542.idtracker@ietfa.amsl.com> <55D32D35-C674-49AD-ADA9-1818F6BCFB16@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
X-Mailer: MailMate (1.9.1r5084)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/bIocPDpE7yK5QWPvrcsQCLM8LUE>
Cc: dhc-chairs@ietf.org, draft-ietf-dhc-dhcpv6-active-leasequery@ietf.org, The IESG <iesg@ietf.org>, dhcwg@ietf.org
Subject: Re: [dhcwg] Ben Campbell's No Objection on draft-ietf-dhc-dhcpv6-active-leasequery-03: (with COMMENT)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jul 2015 22:22:34 -0000

On 9 Jul 2015, at 15:49, Kim Kinnear wrote:

>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>> -- general:
>> I understand this to be a way for a third party to "actively" monitor
>> client DHCPv6 bindings.  Does that warrant some privacy 
>> considerations?
>
> 	Typically this isn't a "third party", but rather another
> 	element of a service providers OSS ensemble.  We expect that
> 	TLS certificates will allow the server to ensure that it is
> 	only talking to requestors with which it is configured to
> 	exchange information.  Additionally, in response to Stephen
> 	Farrell's review, we will be adding text to indicate that an
> 	administrator SHOULD be able to configure which data elements
> 	can be returned to a requestor.   So, yes, we have multiple
> 	levels of controls that can be used to limit the allowed
> 	requestors and the data exchanged with an allowed requestor.

The main point of my comment was that I think this draft needs privacy 
considerations. I see you've already agreed to add that in response to 
Stephen's DISCUSS position. If that addresses Stephen's concerns, it 
will almost certainly address mine, Therefore I will defer to the 
results of that conversation.

Thanks!

Ben.

[...]