IETF Logo Mail Archive

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

Andrew Sullivan <ajs@shinkuro.com> Wed, 02 December 2009 14:37 UTC

Return-Path: <ajs@shinkuro.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 1A8273A6864 for <behave@core3.amsl.com>; Wed, 2 Dec 2009 06:37:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.37
X-Spam-Level:
X-Spam-Status: No, score=-2.37 tagged_above=-999 required=5 tests=[AWL=0.229, 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 oAgp6IDDkISX for <behave@core3.amsl.com>; Wed, 2 Dec 2009 06:37:32 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 62A163A67FC for <behave@ietf.org>; Wed, 2 Dec 2009 06:37:32 -0800 (PST)
Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 30C722FE8CDD for <behave@ietf.org>; Wed, 2 Dec 2009 14:37:24 +0000 (UTC)
Date: Wed, 02 Dec 2009 09:37:22 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: behave@ietf.org
Message-ID: <20091202143722.GF75004@shinkuro.com>
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> <bcff0fba0912012202l5ba54ac4kb03022e91f08eab9@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <bcff0fba0912012202l5ba54ac4kb03022e91f08eab9@mail.gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
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 14:37:33 -0000

On Tue, Dec 01, 2009 at 10:02:52PM -0800, Cameron Byrne wrote:
> 
> If i understand your statement right, you do pull host from the a
> given DNS server upon failure if it is anycast DNS

Not in the anycast deployments I've been involved with, but maybe I
don't understand your remark properly.

Normally, when you anycast DNS, you have one host address in the DNS,
but you announce different routes to that host in the routing system.
You should be able to observe this with different looking glasses for
(for example) the host a0.org.afilias-nst.info.  Note that I'm no
longer involved with the operation of that network, so I am not
entirely sure it still works that way, but I'd be surprised if it
changed that much.

Maybe this isn't what you were talking about?  

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

v2.23.0 | Report a Bug | By Email