[dhcwg] Initial DHCPv6 Failover Requirements draft published
Tomasz Mrugalski <tomasz.mrugalski@gmail.com> Sun, 26 June 2011 18:47 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 5E9801F0C52 for <dhcwg@ietfa.amsl.com>; Sun, 26 Jun 2011 11:47:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level:
X-Spam-Status: No, score=-1 tagged_above=-999 required=5 tests=[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 mIMY2LZfIwIc for <dhcwg@ietfa.amsl.com>; Sun, 26 Jun 2011 11:47:24 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7C1D11F0C53 for <dhcwg@ietf.org>; Sun, 26 Jun 2011 11:47:21 -0700 (PDT)
Received: by eye13 with SMTP id 13so1615272eye.31 for <dhcwg@ietf.org>; Sun, 26 Jun 2011 11:47:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:x-tagtoolbar-keys:content-type:content-transfer-encoding; bh=dyjp+pgVbnoOJhqMfgucgr21Al4r8l+/Wkl5T7/QJII=; b=u0OSRrg+Lguxxc6Pc6QqpDKS2imTrFlDul/HU7+yD0iF9ObAZAX58HhiEcAwPPHZ+l EkQcJMG9x7/RdnLxsmrbb5DWTaUeX3svhtlHfCDLfF1sC4EgmnbDLPSeYVZyXTwhsSJK eEC/p5ACQ59mS2BJAqXl801PMHPDAovW/OUs8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :x-tagtoolbar-keys:content-type:content-transfer-encoding; b=Xocu2foZ+77nu8nxvkOYs4OWINOUZ4OnlZCJ4Cd1uiaNDl71cgyPOCxxcZW9VjhMol NGiL3O0KZSoDunXduftidYPKyczMBwV21dZX9ZPW1qt0DNiBCY2Gz7hyBWv0I16ghPrT FjGujFvtbg1+qxGt3FtKwkt9IiLJE8JXyFaI0=
Received: by 10.14.39.206 with SMTP id d54mr3543696eeb.129.1309114040273; Sun, 26 Jun 2011 11:47:20 -0700 (PDT)
Received: from [10.0.0.100] (host-109-107-11-157.ip.jarsat.pl [109.107.11.157]) by mx.google.com with ESMTPS id y6sm3593590eem.4.2011.06.26.11.47.18 (version=SSLv3 cipher=OTHER); Sun, 26 Jun 2011 11:47:18 -0700 (PDT)
Message-ID: <4E077EB6.7030702@gmail.com>
Date: Sun, 26 Jun 2011 20:47:18 +0200
From: Tomasz Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110516 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: dhcwg@ietf.org
X-TagToolbar-Keys: D20110626204718438
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] Initial DHCPv6 Failover Requirements draft published
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: Sun, 26 Jun 2011 18:47:25 -0000
Dear group, Thanks to contributions and comments of 10 people and participation of many more, we were able to write this draft is relatively short time. Initial version is available here: http://datatracker.ietf.org/doc/draft-mrugalski-dhc-dhcpv6-failover-requirements/ Comments and suggestions are more than welcome. Now that the draft is published we will try to keep all discussions on list, not just meeting minutes. A reminder: There are weekly audio meetings taking place every Monday, dedicated to v6 failover. The next DHCPv6 failover meeting will take place tomorrow: 2011-06-27 10:00am PDT (19:00 CEST) Due to privacy concerns, the audio bridge number is not going to be announced on mailing list. I will send bridge numbers to anyone who asks, though. Bridge details and draft was sent to 18 interested folks so far. This is the first failover-related draft - a requirements document. It will be followed by design document (work on this draft is expected to begin tomorrow). There is no clear consensus if interoperability between different vendors is really feasible, but if there is enough interest, a third document will also be specified - a protocol spec document. We are trying to keep things simple. It is much easier to succeed with 3 smaller drafts, that one large. Also, we are trying to push as many non-essential features into extensions, so there may be additional extension documents that will cover failover-related areas (e.g. load balancing). We would like to present this draft during Quebec meeting. It probably also makes sense to have v6 failover meeting in Quebec, preferably before DHC meeting. Tomek -------- Original Message -------- Subject: New Version Notification for draft-mrugalski-dhc-dhcpv6-failover-requirements-00.txt Date: Sun, 26 Jun 2011 10:52:58 -0700 From: internet-drafts@ietf.org To: tomasz.mrugalski@gmail.com CC: tomasz.mrugalski@gmail.com, kkinear@cisco.com A new version of I-D, draft-mrugalski-dhc-dhcpv6-failover-requirements-00.txt has been successfully submitted by Tomasz Mrugalski and posted to the IETF repository. Filename: draft-mrugalski-dhc-dhcpv6-failover-requirements Revision: 00 Title: DHCPv6 Failover Requirements Creation date: 2011-06-26 WG ID: Individual Submission Number of pages: 19 Abstract: The DHCPv6 protocol, defined in [RFC3315] allows for multiple servers to operate on a single network, however it does not define any way to decide which server responds to which client queries. Some sites are interested in running multiple servers in such a way as to provide increased availability in case of server failure. In order for this to work reliably, the cooperating primary and secondary servers must maintain a consistent database of the lease information. [RFC3315] allows for but does not define any redundancy or failover mechanisms. This document outlines requirements for DHCPv6 failover, enumerates related problems, and discusses the proposed scope of work to be conducted. This document does not define a DHCPv6 failover protocol. The IETF Secretariat
- [dhcwg] Initial DHCPv6 Failover Requirements draf… Tomasz Mrugalski