[dhcwg] DHCPv6 failover update
Tomek Mrugalski <tomasz.mrugalski@gmail.com> Fri, 07 September 2012 16:13 UTC
Return-Path: <tomasz.mrugalski@gmail.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 B44FC21F871A for <dhcwg@ietfa.amsl.com>; Fri, 7 Sep 2012 09:13:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fsmed94Z646a for <dhcwg@ietfa.amsl.com>; Fri, 7 Sep 2012 09:13:12 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id B6B4F21F8713 for <dhcwg@ietf.org>; Fri, 7 Sep 2012 09:13:11 -0700 (PDT)
Received: by eekb45 with SMTP id b45so1350109eek.31 for <dhcwg@ietf.org>; Fri, 07 Sep 2012 09:13:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=bRlXdQFZEqdvlgiHj99V1jxU+ZQUhkbjnrRD8vHcuKM=; b=zqEEGJxhi/YwvEJyrwoOxyfPBw1/hVONIpddva1CY+HzEV9rwr0ZR9Bghw4UqNk9K6 5sE0e/N9BNrAWybXoH45NaVAp9y7l5gb3iY0HGpYozwcsMEUF19Ix4d+XhEHPU6G3wtg q7cy/xcr9gz0a/z9RcyNIKgRz8E/jEp0STXHrzOuO0lOSIR/moK858F37fGtJlWNrU1D hizBgOIhk4HG7J5+H5BJyh9JEGgSbqfAsfV/fQCJoBnRmY4bUcve2CTMj13g1Zz1aapD 8I/aX7ZmoHha/m62hydGqs2eBBMCxkF64HbIK7GJ2UBNreC/xO2+agbT0AayG8gH69TQ UNrA==
Received: by 10.14.173.131 with SMTP id v3mr3267073eel.15.1347034390968; Fri, 07 Sep 2012 09:13:10 -0700 (PDT)
Received: from ?IPv6:2001:470:6061:1:e086:e8e7:836c:20ad? ([2001:470:6061:1:e086:e8e7:836c:20ad]) by mx.google.com with ESMTPS id i8sm15906456eeo.16.2012.09.07.09.13.09 (version=SSLv3 cipher=OTHER); Fri, 07 Sep 2012 09:13:10 -0700 (PDT)
Message-ID: <504A1D13.8090003@gmail.com>
Date: Fri, 07 Sep 2012 18:13:07 +0200
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0
MIME-Version: 1.0
To: dhcwg <dhcwg@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] DHCPv6 failover update
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, 07 Sep 2012 16:13:12 -0000
Hi, You may have noticed some recent movements in the failover area. It may be a bit confusing, so I wanted to explain what has happened recently. Step 0: DHCPv6 Redundancy Considerations draft-ietf-dhc-dhcpv6-redundancy-consider-03 This draft is in IESG review now. A kind of soft discuss was raised, so authors worked on an updated version that hopefully addresses all concerns. It already completed WGLC, so no extra actions are requested at this time. Of course, you are welcome to (re)read and review it, but if your time is limited, there are better things to do to help with failover (see steps 1 and 2 below). Step 1: DHCPv6 Failover Requirements draft-ietf-dhc-dhcpv6-failover-requirements-02 This is a first in a series of 3 drafts planned. It lays out requirements for DHCPv6 failover. Authors believe that work on this document is more or less done and would like to ask for WGLC. If you have only short time for failover related things, please review this. Step 2: DHCPv6 Failover Design draft-ietf-dhc-dhcpv6-failover-design-01 This is the actual design. There is a significant progress from the -00 version, but this work is not complete yet. Although failover endpoints state machine and lease lifecycle descriptions are more or less complete, there are still missing bits and pieces. See several TODO tags in the txt version or issues marked in XML version. It would be great to hear your comments and suggestions about this draft, or even better, contributed text for missing pieces. There is a step 3 planned - the actual on-wire spec for the design laid out in failover-design draft. This work hasn't started yet. If you are interested in the failover work, you are more then welcome to join the effort. We have a public GIT repo for intermediate versions, with a simple list of issues, historical v4 failover drafts etc. It is available here: https://github.com/tomaszmrugalski/ietf-dhcpv6-fo Cheers, Tomek
- [dhcwg] DHCPv6 failover update Tomek Mrugalski
- [dhcwg] WGLC request on draft-ietf-dhc-dhcpv6-faiā¦ Tomek Mrugalski