[dhcwg] WGLC request on draft-ietf-dhc-dhcpv6-failover-requirements-02
Tomek Mrugalski <tomasz.mrugalski@gmail.com> Wed, 26 September 2012 13:33 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 1FA5521F86D8 for <dhcwg@ietfa.amsl.com>; Wed, 26 Sep 2012 06:33:40 -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 OG3cYdRZ1eUV for <dhcwg@ietfa.amsl.com>; Wed, 26 Sep 2012 06:33:33 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 85AA021F86D4 for <dhcwg@ietf.org>; Wed, 26 Sep 2012 06:33:33 -0700 (PDT)
Received: by bkcjc3 with SMTP id jc3so324004bkc.31 for <dhcwg@ietf.org>; Wed, 26 Sep 2012 06:33:32 -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:cc:subject :references:in-reply-to:x-tagtoolbar-keys:content-type :content-transfer-encoding; bh=0yuu8iFJ2QESu9lQJERh1L5Wkfc5vYEDCOasJfRbrrk=; b=ENr1O+RiZiU3KJTbjbqTkpWG3U8Fv/AL7tp+DfXUVmknmWWKtfQvzjO8XLkuB9OJCY wZDJHUuZtQu3vDa4vSvLoFDL0UV3P+Ih+3SJZHa2DrFAlMWcnzodvvnC9JF6Iwe79Vog o4UbvP7NBd2Qq6oSWmWeH5blg4y1kgUL73N21AJrMYg5ie6ze3daKXmADMQMoJPRDe5G EY+Cfp3NgG6GHkHK057G7bckTVp2dcnKcPrGBCZjtLhtXl6ZQ25MyrP3OCV7LT75mGGC OcvclPjqcWneH5z3iZ4doc/y9w496xcNWwhp41gU8+RXHVi8tGit1swO16qFV10B7Wt0 +5EQ==
Received: by 10.204.157.6 with SMTP id z6mr514024bkw.25.1348666412415; Wed, 26 Sep 2012 06:33:32 -0700 (PDT)
Received: from ?IPv6:2001:470:6061:1:31aa:f7e:fa88:4ff9? ([2001:470:6061:1:31aa:f7e:fa88:4ff9]) by mx.google.com with ESMTPS id c18sm2484030bkv.8.2012.09.26.06.33.30 (version=SSLv3 cipher=OTHER); Wed, 26 Sep 2012 06:33:31 -0700 (PDT)
Message-ID: <50630427.2020100@gmail.com>
Date: Wed, 26 Sep 2012 15:33:27 +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>
References: <504A1D13.8090003@gmail.com>
In-Reply-To: <504A1D13.8090003@gmail.com>
X-TagToolbar-Keys: D20120926153327609
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: Ted Lemon <Ted.Lemon@nominum.com>
Subject: [dhcwg] WGLC request on draft-ietf-dhc-dhcpv6-failover-requirements-02
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: Wed, 26 Sep 2012 13:33:40 -0000
Hi, Authors of DHCPv6 Failover Requirements draft believe that it is ready for a last call. Therefore I would like to ask chairs to announce WGLC on draft-ietf-dhc-dhcpv6-failover-requirements-02. Thanks, Tomek On 07.09.2012 18:13, Tomek Mrugalski wrote: > 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