[dhcwg] Stephen Farrell's No Objection on draft-ietf-dhc-dhcpv6-failover-protocol-04: (with COMMENT)
"Stephen Farrell" <stephen.farrell@cs.tcd.ie> Thu, 02 February 2017 01:33 UTC
Return-Path: <stephen.farrell@cs.tcd.ie>
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 0F062129588; Wed, 1 Feb 2017 17:33:47 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148599922705.18700.14648245113952484559.idtracker@ietfa.amsl.com>
Date: Wed, 01 Feb 2017 17:33:47 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/uKx2Q1K7cNRmRZzMyeea48G-Jm8>
Cc: dhc-chairs@ietf.org, volz@cisco.com, draft-ietf-dhc-dhcpv6-failover-protocol@ietf.org, dhcwg@ietf.org
Subject: [dhcwg] Stephen Farrell'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: Thu, 02 Feb 2017 01:33:47 -0000
Stephen Farrell 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 support Ben's discuss about "secure mode" - a few more details are needed, in particular how a pair decide to use/not-use TLS - are there different ports or a STARTTLS equivalent - I can't see that defined here. (Is it inherited from RFC7653? If so, maybe you need to say?) - For the DNS update stuff - is there no need to use TSIG secrets? If there is, how is that sync'd between the pair of DHCP servers? If it is sync'd then don't you need to say that TLS is a MUST for such connections? If there is no support for TSIG, is that likely to work?
- [dhcwg] Stephen Farrell's No Objection on draft-i… Stephen Farrell
- Re: [dhcwg] Stephen Farrell's No Objection on dra… kkinnear
- Re: [dhcwg] Stephen Farrell's No Objection on dra… Stephen Farrell
- [dhcwg] Comments on draft-ietf-dhc-dhcpv6-failove… kkinnear
- Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-fai… kkinnear