IETF Logo Mail Archive

Re: [Gen-art] Gen-ART review of draft-ietf-dhc-dhcpv6-failover-protocol-04

kkinnear <kkinnear@cisco.com> Wed, 01 February 2017 23:07 UTC

Return-Path: <kkinnear@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE681129545 for <gen-art@ietfa.amsl.com>; Wed, 1 Feb 2017 15:07:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.72
X-Spam-Level:
X-Spam-Status: No, score=-17.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 UQGhSHiS8yTi for <gen-art@ietfa.amsl.com>; Wed, 1 Feb 2017 15:07:01 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E6CA129411 for <gen-art@ietf.org>; Wed, 1 Feb 2017 15:07:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2342; q=dns/txt; s=iport; t=1485990421; x=1487200021; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=RSiyJPzfsjc4ZqK/8hl8Pzfgqji3I7XaVV60ObH4VqE=; b=ec1qAov5X2GzMXtN4KyjCKK2xoIWOm5HJOKjDgP4LLM1ORCUq/jNrx6Z 1p9EXhJExbi5grHHnGt5B7xAJawlUkgxQkA2/Kvp+LQjXmEfF+j1/9uXv +C+WMrPChvfy8UHRFFTOXf9SO5zzZ2yESfAz7HOgJ/CSWS4Xk4850XcRL g=;
X-IronPort-AV: E=Sophos;i="5.33,322,1477958400"; d="scan'208";a="203452558"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Feb 2017 23:07:00 +0000
Received: from bxb-kkinnear-8814.cisco.com (bxb-kkinnear-8814.cisco.com [10.98.10.245]) (authenticated bits=0) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id v11N6xkf007617 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Feb 2017 23:07:00 GMT
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: kkinnear <kkinnear@cisco.com>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BFD921A@ESESSMB209.ericsson.se>
Date: Wed, 01 Feb 2017 18:06:58 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <49C6D51E-A1C4-44BB-BC73-0752195D8F41@cisco.com>
References: <7594FB04B1934943A5C02806D1A2204B4BFD8F92@ESESSMB209.ericsson.se> <F5C2B9B7-F35D-4E92-829E-05100DDFBDA5@cisco.com> <7594FB04B1934943A5C02806D1A2204B4BFD921A@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3124)
X-Authenticated-User: kkinnear@cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/zRcgBcM65sOMN82zT-_LHq_NZt4>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-dhc-dhcpv6-failover-protocol.all@tools.ietf.org" <draft-ietf-dhc-dhcpv6-failover-protocol.all@tools.ietf.org>, Kim Kinnear <kkinnear@cisco.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dhc-dhcpv6-failover-protocol-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 23:07:03 -0000

Christer,

I have deleted the issues not under discussion.

More comments, indented, below...

> On Feb 1, 2017, at 5:57 PM, Christer Holmberg <christer.holmberg@ericsson.com> wrote:
> 
> Hi,
> 
>> 
>>> Q3:        In the Introduction, I suggest adding a reference to the first occurrences of “DHCP service” and “DHCP server”.
>> 
>> 	While I'm more than happy to do this, I don't actually know
>> 	what you would like me to reference?  We haven't defined
>> 	either "DHCP service" or "DHCP server" in the glossary since
>> 	we felt they were reasonably apparent from the context of this
>> 	document.  Are you thinking that we should reference RFC3315
>> 	on the first occurrence of "DHCP service" and "DHCP server"?
> 
> Yes.

	Ok, I will do so in the next update.
> 
>>> SECTION 4:
>>> 
>>> Q5:        In the Abstract and Introduction it is said that DHCPv6 does not provide server redundancy. Then section 4 talks about failover concepts and mechanism.
>>> 
>>> Are those concepts something used for DHCPv6 today, but for some reason do not fulfil the failover protocol requirements?
>>> 
>>> OR, are these general concepts that will be supported by implementing the failover protocol?
>>> 
>>> I think it would be good to have an introduction statement clarifying that.
>> 
>> 	The concepts and mechanisms discussed in Section 4 relate to
>> 	the failover protocol, they aren't present in the regular
>> 	RFC3315(et. al.) DHCPv6 protocol.  I will add the following to
>> 	Section 4 to clarify that:
>> 
>> 	"4.  Failover Concepts and Mechanisms
>> 
>> 	The following concepts and mechanisms are necessary to the operation
>> 	of the failover protocol, and they are not currently employed by
>> 	the DHCPv6 protocol [RFC3315].
> 
> That's better. But, will the failover protocol provide support for those concepts? If so, please indicate it.
> 

	How about this:

	"4.  Failover Concepts and Mechanisms

	The following concepts and mechanisms are necessary to the operation
	of the failover protocol, and they are not currently employed by
	the DHCPv6 protocol [RFC3315].  The failover protocol provides
        support for all of these concepts and mechanisms.

	..."

Thanks -- Kim

v2.23.0 | Report a Bug | By Email