[dhcwg] Ben Campbell's No Objection on draft-ietf-dhc-relay-port-08: (with COMMENT)

Ben Campbell <ben@nostrum.com> Thu, 30 November 2017 02:26 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: dhcwg@ietf.org
Delivered-To: dhcwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F2E24124BFA; Wed, 29 Nov 2017 18:26:54 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Ben Campbell <ben@nostrum.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-dhc-relay-port@ietf.org, Tomek Mrugalski <tomasz.mrugalski@gmail.com>, dhc-chairs@ietf.org, tomasz.mrugalski@gmail.com, dhcwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.66.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151200881498.4910.12635544118258754868.idtracker@ietfa.amsl.com>
Date: Wed, 29 Nov 2017 18:26:54 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/FUzXwM08kboCuOjBcqoIsaee4Pg>
Subject: [dhcwg] Ben Campbell's No Objection on draft-ietf-dhc-relay-port-08: (with COMMENT)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 30 Nov 2017 02:26:55 -0000

Ben Campbell has entered the following ballot position for
draft-ietf-dhc-relay-port-08: 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-relay-port/



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

Discussion seems to be moving in the right direction, so I have cleared my
response. I've added it back as a comment for now:

<former-discuss>
(I want to "discuss" the following  DISCUSS point. If the answer is that this
is by design, and the working group thinks that the operational aspects are
reasonable, then I will clear.)

This extension places normative requirements on any upstream server or relay,
which may or may not implement this spec.  It further appears that if you try
to use this extension without that support, things will break. That seems to
require at least an update to the DCHP and DCHPv6 RFCs[1], and some method of
discovery or fallback would be helpful. Section 5.4 discusses this a little
bit, but I think it needs to talk about what to do when things fail. "Turn off
the feature if you don't get DHCP responses" doesn't seem satisfying.

[1] I see 3.1 and 3.2 make changes to 2131 and 3315, so it seems an "UPDATES...
" tag is needed one way or another.

</former-discuss>

-1, last paragraph: It seems like the 2119 keywords here would be better placed
in the later sections about relay and server behavior. I suggest moving them
there, and making the introductory language non-normative.

- 3.1 and 3.2: I am surprised not to see 2119 keywords in the language added to
2131 and 3315:

-8: This spec adds the ability to direct dhcp responses to non-standard ports.
If the working group believes that does not affect the security considerations,
please describe the rational. (I'm not saying that I think there's a problem,
but I think the burden is on the working group to explain why they think there
is not.)