IETF Logo Mail Archive

Re: [BEHAVE] proprietary implementation v.s standardisedprotocols//re: draft-xu-behave-nat-state-sync-00

Cameron Byrne <cb.list6@gmail.com> Wed, 02 December 2009 06:03 UTC

Return-Path: <cb.list6@gmail.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8D7593A6805 for <behave@core3.amsl.com>; Tue, 1 Dec 2009 22:03:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.582
X-Spam-Level:
X-Spam-Status: No, score=-2.582 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599]
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 dmsSJ8hyU7qK for <behave@core3.amsl.com>; Tue, 1 Dec 2009 22:03:05 -0800 (PST)
Received: from mail-gx0-f228.google.com (mail-gx0-f228.google.com [209.85.217.228]) by core3.amsl.com (Postfix) with ESMTP id 80E4D3A67F5 for <behave@ietf.org>; Tue, 1 Dec 2009 22:03:05 -0800 (PST)
Received: by gxk28 with SMTP id 28so3076134gxk.9 for <behave@ietf.org>; Tue, 01 Dec 2009 22:02:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=I4HzhGDH9r92y+hUkqFFWKF0miOxtxAAR3U936sXJ6g=; b=AIkGV+LrzRrWU8AvCbLXuH0jvCM1pFv8iuhOns6Cb74FAD9KwApdn8WKGDvfGw3MxK hAJsbBl3NaGXVys14YO+h/At9Iq1P9bN1j1Y+4x7SJuE77Kx0QgvYrw90/qNti1YSaFF ufJGkZaHJ4cMoAxfz1BXH0a/OUW0dIgxKMm2I=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=UEmuOSWvQgtYq+7t//dxKbiI3jRmbDn/HytEwd3NtQBvJkr/BaJhKklx+rKPHUFNMt X3MaijWhR68RV+74arYf+jBfGUSyTKoqKQ/4m4iEmX8dMnFoLCpANzdlkljn6NHk5aoZ p69Xc75EOQsoxIKVO8DHsmkGSJDri56jc1E1o=
MIME-Version: 1.0
Received: by 10.150.28.27 with SMTP id b27mr11647336ybb.59.1259733773038; Tue, 01 Dec 2009 22:02:53 -0800 (PST)
In-Reply-To: <200912020549.nB25n8Yu058184@drugs.dv.isc.org>
References: <bcff0fba0912011405x56975fe7t442f60ab8f9a1284@mail.gmail.com> <003501ca72f2$e6021a30$d40c6f0a@china.huawei.com> <000801ca72f8$c3fa5820$c3f0200a@cisco.com> <200912020254.nB22sIvO028323@drugs.dv.isc.org> <002301ca7301$9ef3f4b0$c3f0200a@cisco.com> <200912020549.nB25n8Yu058184@drugs.dv.isc.org>
Date: Tue, 01 Dec 2009 22:02:52 -0800
Message-ID: <bcff0fba0912012202l5ba54ac4kb03022e91f08eab9@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: Mark Andrews <marka@isc.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: behave@ietf.org, Xu Xiaohu <xuxh@huawei.com>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] proprietary implementation v.s standardisedprotocols//re: draft-xu-behave-nat-state-sync-00
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Dec 2009 06:03:06 -0000

On Tue, Dec 1, 2009 at 9:49 PM, Mark Andrews <marka@isc.org> wrote:
>
> In message <002301ca7301$9ef3f4b0$c3f0200a@cisco.com>, "Dan Wing" writes:
>>
>>
>> > -----Original Message-----
>> > From: marka@isc.org [mailto:marka@isc.org]
>> > Sent: Tuesday, December 01, 2009 6:54 PM
>> > To: Dan Wing
>> > Cc: 'Xu Xiaohu'; 'Cameron Byrne'; 'Simon Perreault'; behave@ietf.org
>> > Subject: Re: [BEHAVE] proprietary implementation v.s
>> > standardisedprotocols//re: draft-xu-behave-nat-state-sync-00
>> >
>> >
>> > In message <000801ca72f8$c3fa5820$c3f0200a@cisco.com>, "Dan
>> > Wing" writes:
>> > > ...
>> > > > > 100% agree.  Members in a cluster failing can locally
>> > be resolved
>> > > > > without bouncing the Pref64.  If entire cluster fails,
>> > this is very
>> > > > > unlikely but catastrophic, i just want a fail safe that can work
>> > > > > *mostly*, and if the networks really broke, asking a
>> > user to reboot
>> > > >
>> > > > Ask a user or ask a huge amount of users?
>> > >
>> > > All the affected users.
>> > >
>> > > > By the way, if one uses one of those mechanisms defined in
>> > > > draft-wing-behave-learn-prefix, other than DNS64, to
>> > > > synthesize IPv6 addresses, does that mean the DNS server or
>> > > > the DHCP server should also dynamically detect the
>> > > > availability of each prefix64?
>> > >
>> > > Whatever hands out the prefix (DNS, IPv6 router advertisements,
>> > > DHCPv6) should hand out a functioning prefix.  Providing a
>> > > non-functioning prefix is harmful.
>> >
>> > Actually it shouldn't be.  If a prefix doesn't work it it like a
>> > router being down.  The machines are just not reachable.
>>
>> Not being reachable is what I would define as 'harmful'.
>
> You don't, in general, pull hosts from the DNS because a router is
> down.

If i understand your statement right, you do pull host from the a
given DNS server upon failure if it is anycast DNS

>
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
>

v2.23.0 | Report a Bug | By Email