[dhcwg] draft-ietf-dhc-dhcpv6-failover-design-04.txt
Kim Kinnear <kkinnear@cisco.com> Fri, 13 September 2013 21:12 UTC
Return-Path: <kkinnear@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 8593611E817D for <dhcwg@ietfa.amsl.com>; Fri, 13 Sep 2013 14:12:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 xOS6alXO1sq1 for <dhcwg@ietfa.amsl.com>; Fri, 13 Sep 2013 14:12:33 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 4C3CA11E80D2 for <dhcwg@ietf.org>; Fri, 13 Sep 2013 14:12:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2906; q=dns/txt; s=iport; t=1379106753; x=1380316353; h=from:content-transfer-encoding:subject:date:message-id: cc:to:mime-version; bh=jJZLGo50R5bjNQb7jNeI9vtSN3/ZnROp/O6Mm3KRleg=; b=m9GXJq2VhjvAhFXdFt/awNTufae28teBZgcCfGB7mUIIVKqwj495Ukwr ku8TLzdZIsCcGdkExbPg3VpNTQUeJyyfA02cT5RvvrBDBEiaPn5T4HEcq b7FE4U8OOnbhIs0ECjUts3Wk9vt/HR7OWBgKubOGqpeY5Hzb+e1p6oXBI A=;
X-IronPort-AV: E=Sophos;i="4.90,900,1371081600"; d="scan'208";a="259537083"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-8.cisco.com with ESMTP; 13 Sep 2013 21:12:33 +0000
Received: from che-vpn-cluster-1-204.cisco.com (che-vpn-cluster-1-204.cisco.com [10.86.240.204]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r8DLCWOa028055; Fri, 13 Sep 2013 21:12:32 GMT
From: Kim Kinnear <kkinnear@cisco.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Date: Fri, 13 Sep 2013 17:12:39 -0400
Message-Id: <3ADDE687-5B24-4CC0-93DA-97A76F3EEAC8@cisco.com>
To: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
Cc: Kim Kinnear <kkinnear@cisco.com>
Subject: [dhcwg] draft-ietf-dhc-dhcpv6-failover-design-04.txt
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: Fri, 13 Sep 2013 21:12:38 -0000
Folks, I have just posted a new version of the DHCPv6 Failover design draft: draft-ietf-dhc-dhcpv6-failover-design-04.txt There were a large number of spelling and wording errors pointed out to us by Bernie Volz in his review, which I have fixed. Tomek added some contributors to the acknowledgments section as well. In addition, Bernie found several more or less substantive issues that we needed to address -- in some cases clarifying the original intent of the draft, in other cases making slight changes to the draft. I have listed these more substantive changes below. Regards -- Kim --------------------- 1. Section 2: Added "DDNS" and "Lease" to the Glossary. 2. Section 2: Included temporary (IA_TA) addresses in the resources that are handled by failover. 3. Section 5.1: Made attempting to connect to failover partner a MUST instead of a SHOULD, for both primary and secondary servers. 4. Section 6.1: Removed ordering requirement for POOLRESP message to be sent prior to BNDUPD triggered by POOLREQ. Also removed implicit requirement (largely in figures) that POOLRESP contain number of resources allocated to partner. 5. Section 6.3: Removed MUST requirement for proportional algorithm support, and deferred algorithm assignment to resource allocation domain to subsequent documents. 6. Section 8.2: Removed entire section on Time Expression. This will be addressed in any subsequent protocol document(s) produced. 7. Old Section 8.7 (new 8.6): Removed requirement for every server to be able to support multiple binding update transactions in a single message. Instead such use is now negotiated during connection establishment with the CONNECT and CONNECTACK message exchange. 8. Old Section 8.7 (new 8.6): Removed requirement to send the valid life time requested by DHCPv6 client in every BNDUPD. 9. Old Section 8.7 (new 8.6): Removed requirement to reject BNDUPD messages that contain (or do not contain) specific values. Kept MUST directives for what must go into the BNDUPD, but allowed receiving code to do the best it can and not be required to reject any particular packet. 10. Old Section 8.7 (new 8.6): Removed explicit requirement for the following data items: o Remote-ID, defined in [RFC4649]; o Relay-ID, defined in [RFC5460], section 5.4.1; o Link-layer address [RFC6939]; and replaced it with a reference to the Relay Data option defined in RFC 5007 (the DHCPv6 Leasequery draft). Along with this, moved RFC 5007 from the Informative to the Normative Bibliography section. 11. Section 9.7.1: Restricted ability of server to process messages in RECOVER-DONE state to RENEW message with no new resource allocations allowed even for RENEW message. 12. Section 9.11: Clarified reasoning for RESOLUTION-INTERRUPTED state, to avoid confusion. [end of changes to -04.txt draft]
- [dhcwg] draft-ietf-dhc-dhcpv6-failover-design-04.… Kim Kinnear
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-failover-design… Bernie Volz (volz)
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-failover-design… Bernie Volz (volz)