Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-failover-design-03 - Respond by August 9, 2013!

"Bernie Volz (volz)" <volz@cisco.com> Sat, 17 August 2013 02:31 UTC

Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A50D511E81FF for <dhcwg@ietfa.amsl.com>; Fri, 16 Aug 2013 19:31:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qE2EUccXCj39 for <dhcwg@ietfa.amsl.com>; Fri, 16 Aug 2013 19:31:51 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 9C48B11E81F2 for <dhcwg@ietf.org>; Fri, 16 Aug 2013 19:31:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15421; q=dns/txt; s=iport; t=1376706711; x=1377916311; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=rP7zKLSfcaXXuXq6n2OApnlUJOHdPe5amNTcYmvbGPI=; b=nLG/0GEdBtsOTLZ74I+BKF8TStV+SiEZ0PeLORBuaPM4xzx2vE1XEM+1 fJsBqY3NEBpGW8jVH/jtwMR3lze2PkVl5eYs8gcMyjnwP0SC0mW/EW7BC UwiZigEsRqgkOr5YIvWep32TpZzsSWerQp/7+OEiFaOozTegOpbU0FgBB g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYGAIjfDlKtJXG9/2dsb2JhbABbgkJENVG2XohGgSkWbQeCJAEBAQQtRBgCAQgRBAEBCx0HMhQJCAEBBBMIiAgMuTSPA4EcNwGDG3cDmRGQKIFhgTuBaAcCFyI
X-IronPort-AV: E=Sophos; i="4.89,899,1367971200"; d="scan'208,217"; a="248470302"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-4.cisco.com with ESMTP; 17 Aug 2013 02:31:51 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r7H2VoqV025333 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Sat, 17 Aug 2013 02:31:50 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.180]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.02.0318.004; Fri, 16 Aug 2013 21:31:49 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-failover-design-03 - Respond by August 9, 2013!
Thread-Index: Ac6Eh+GxcVMnIa4YTCqgEkgg655xbgWZzzNQ
Date: Sat, 17 Aug 2013 02:31:49 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1867159F@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E185ECB4B@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E185ECB4B@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.82.214.99]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1867159Fxmbrcdx04ciscoc_"
MIME-Version: 1.0
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-failover-design-03 - Respond by August 9, 2013!
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 17 Aug 2013 02:31:56 -0000

I finally had some time to carefully review this document (though it is late). But it turned out that Kim (co-author) was away this past week and so likely not much would have happened with the document anyway (see below). And, a few indicated they would prefer to have a bit more time (given the IETF meeting and vacations).

I do support this document moving forward.

However, the 03 version does have a bunch of mostly nits. And, I have a marked up paper version which I will review with Kim (hopefully over the next few days, but he may be busy catching up after having been away). I'd rather not have to list all of these nits in an email (spelling corrections, wording changes, minor errors). There are several TODOs in the document and a reference (TODO) to a non-existent section (on automatic transition of a server to partner-down after a configured time interval). I'd also suggest dropping some text, such as 8.2 Time Expression, as that belongs in a protocol document, not the design (there's no other text dependent on it). These must be cleaned up before sending the document on.

Reviewing my marked up document with Kim and having him update the document will likely be the best way to go (though of course there is no list to send out). But again, there's no significant flaws or issue that I found. Just a lot of fairly minor cleanup to do.

I hope to discuss the WGLC status with Tomek early next week (8/19) and then we will communicate the results.

If anyone else has any comments in support (or not) of the WGLC on this document, please let us know (by 8/19).


-          Bernie

From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Friday, July 19, 2013 9:59 AM
To: dhcwg@ietf.org
Subject: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-failover-design-03 - Respond by August 9, 2013!


Folks, the authors of draft-ietf-dhc-dhcpv6-failover-design-03 (http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-failover-design) believe it is ready for working group last call. Please review this draft and indicate whether or not you feel it is ready to be published. Your input is important!



This document is the 2nd series of documents related to DHCPv6 failover - the first is http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-failover-requirements which is currently being reviewed by the IESG for publication approval.



At the time of this writing, there is no IPR reported against this draft.



As Tomek is a co-author, I will primarily evaluate consensus after 2013-08-09 (August 9th). This is a 3 week last call because of the Berlin IETF meeting and also because of summer-time vacations (at least for those of us in the northern hemisphere).



Thanks,


-          Bernie