Re: [Softwires] [dhcwg] Is tunnelling DHCP multicast messages in 6rd unicast tunnel to BR acceptable for DHCP redundancy?//re: About draft-guo-softwire-6rd-ipv6-config-00

Rémi Després <remi.despres@free.fr> Thu, 09 September 2010 07:32 UTC

Return-Path: <remi.despres@free.fr>
X-Original-To: softwires@core3.amsl.com
Delivered-To: softwires@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ED1353A67D1; Thu, 9 Sep 2010 00:32:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.371
X-Spam-Level:
X-Spam-Status: No, score=-1.371 tagged_above=-999 required=5 tests=[AWL=0.578, BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dGAsRPEu4rjH; Thu, 9 Sep 2010 00:32:35 -0700 (PDT)
Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) by core3.amsl.com (Postfix) with ESMTP id 63B883A696D; Thu, 9 Sep 2010 00:32:29 -0700 (PDT)
Received: from [192.168.0.20] (unknown [88.166.221.144]) by smtp6-g21.free.fr (Postfix) with ESMTP id 15F46822E6; Thu, 9 Sep 2010 09:32:49 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="iso-8859-1"
From: Rémi Després <remi.despres@free.fr>
In-Reply-To: <4C886A21.8060704@cisco.com>
Date: Thu, 09 Sep 2010 09:32:48 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <5BD9499C-CD7E-4972-8147-4FA2F3E6E03F@free.fr>
References: <003701cb3ce2$7d58acf0$26626e0a@china.huawei.com> <4C886A21.8060704@cisco.com>
To: Softwires <softwires@ietf.org>, DHC WG <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1081)
Subject: Re: [Softwires] [dhcwg] Is tunnelling DHCP multicast messages in 6rd unicast tunnel to BR acceptable for DHCP redundancy?//re: About draft-guo-softwire-6rd-ipv6-config-00
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 07:32:40 -0000

Le 9 sept. 2010 à 07:01, Mark Townsley a écrit :

> On 8/16/10 3:29 AM, Xu Xiaohu wrote:

>> ...
>> However, the BR itself (no matter as a relay agent or a DHCP server) is a
>> single point of failure, especially in the case where the DHCP service on
>> the BR is unavailable while the route for it (anycast address) is still OK. 
> 
> ...
> We're talking about stateless
> DHCP operation here, so *all* the BRs in the SP network could run this
> (indeed, all would have to if addressed via the anycast address that 6rd
> uses to reach the BRs since you don't know in advance which one you
> would reach). As long as all participating BRs have the server or relay
> function, I see no single point of failure problem.

+1


> 
> - Mark
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires