[dhcwg] Kathleen Moriarty's No Objection on draft-ietf-dhc-dhcpv6-failover-protocol-04: (with COMMENT)

"Kathleen Moriarty" <Kathleen.Moriarty.ietf@gmail.com> Tue, 31 January 2017 19:14 UTC

Return-Path: <Kathleen.Moriarty.ietf@gmail.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 9395512954B; Tue, 31 Jan 2017 11:14:06 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Kathleen Moriarty" <Kathleen.Moriarty.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.41.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148589004659.5913.10170408064364078877.idtracker@ietfa.amsl.com>
Date: Tue, 31 Jan 2017 11:14:06 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/n9M3EAgiQ864EDgXncPDncaTk10>
Cc: dhc-chairs@ietf.org, volz@cisco.com, draft-ietf-dhc-dhcpv6-failover-protocol@ietf.org, dhcwg@ietf.org
Subject: [dhcwg] Kathleen Moriarty's No Objection on draft-ietf-dhc-dhcpv6-failover-protocol-04: (with COMMENT)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 31 Jan 2017 19:14:06 -0000

Kathleen Moriarty has entered the following ballot position for
draft-ietf-dhc-dhcpv6-failover-protocol-04: 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-dhcpv6-failover-protocol/



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

I have 2 questions that I would like to chat about and should be easy
enough to resolve.

1. I know we've discussed in the past why there is no MUST for TLS and it
having to do with DHCPv6 use on private networks or isolated.  Is there
text in one of the more recent RFCs that covers this explanation that can
be cited?  I'd like to make sure that's enough too.

2. The Security Considerations section says not to use Authentication
from RFC3316.  SHould authentication instead be done within TLS or how
will the session be authenticated.  Did I miss something?  I'm not
finding the term authentication elsewhere in the draft and can infer
things, but wanted to make sure since nothing is stated explicitly.