[dhcwg] Alissa Cooper's No Objection on draft-ietf-dhc-dhcpv4-active-leasequery-06: (with COMMENT)

"Alissa Cooper" <alissa@cooperw.in> Wed, 30 September 2015 22:56 UTC

Return-Path: <alissa@cooperw.in>
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 752DC1AC3E8; Wed, 30 Sep 2015 15:56:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.1
X-Spam-Level:
X-Spam-Status: No, score=-1.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8] autolearn=no
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 VfprJPIAgr_7; Wed, 30 Sep 2015 15:56:00 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 90AA21AC3CB; Wed, 30 Sep 2015 15:56:00 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper <alissa@cooperw.in>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.4.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150930225600.1742.48032.idtracker@ietfa.amsl.com>
Date: Wed, 30 Sep 2015 15:56:00 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/VYEwO_ONLh-sM1h6V_GzgLM31kg>
Cc: dhcwg@ietf.org
Subject: [dhcwg] Alissa Cooper's No Objection on draft-ietf-dhc-dhcpv4-active-leasequery-06: (with COMMENT)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 30 Sep 2015 22:56:01 -0000

Alissa Cooper has entered the following ballot position for
draft-ietf-dhc-dhcpv4-active-leasequery-06: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv4-active-leasequery/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I think it would help to explain the rationale for having both secure and
insecure modes supported.

In sections 7.2, 8.1, and 9, this is a bit of a strange layering of
normative requirements:

The recommendations in [RFC7525] SHOULD be followed when negotiating
   this connection.

If you were going to use normative language here I think this would more
appropriately be a MUST, but I would actually recommend something along
the lines of "The recommendations in [RFC7525] apply" since the
recommendations contained therein vary in their normative strength.
Perhaps the security ADs have a preferred formulation, I'm not sure.