IETF Logo Mail Archive

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

Simon Perreault <simon.perreault@viagenie.ca> Tue, 01 December 2009 10:42 UTC

Return-Path: <simon.perreault@viagenie.ca>
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 1B0EC3A684F for <behave@core3.amsl.com>; Tue, 1 Dec 2009 02:42:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.469
X-Spam-Level:
X-Spam-Status: No, score=-2.469 tagged_above=-999 required=5 tests=[AWL=0.130, 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 DQcue0Z1+wNy for <behave@core3.amsl.com>; Tue, 1 Dec 2009 02:42:54 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by core3.amsl.com (Postfix) with ESMTP id 215253A6824 for <behave@ietf.org>; Tue, 1 Dec 2009 02:42:54 -0800 (PST)
Received: from balaise.nomis80.org (modemcable245.152-21-96.mc.videotron.ca [96.21.152.245]) by jazz.viagenie.ca (Postfix) with ESMTPSA id AE8B720DF9 for <behave@ietf.org>; Tue, 1 Dec 2009 05:42:46 -0500 (EST)
Message-ID: <4B14F326.40009@viagenie.ca>
Date: Tue, 01 Dec 2009 05:42:46 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.4pre) Gecko/20090922 Fedora/3.0-3.9.b4.fc12 Thunderbird/3.0b4
MIME-Version: 1.0
To: behave@ietf.org
References: <002f01ca7265$b6ededb0$d40c6f0a@china.huawei.com>
In-Reply-To: <002f01ca7265$b6ededb0$d40c6f0a@china.huawei.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Tue, 01 Dec 2009 10:42:55 -0000

On 12/01/2009 04:07 AM, Xu Xiaohu wrote:
> In order to use the correct prefix64 in synthesizing AAAA records, the DNS64 should be able to determine which prefix64 is available by some means, e.g., exchanging messages with NAT64, or sending probe packets to a given IPv4 host within the IPv4 Internet by using different prefix64s.
>
> BTW, once the NAT box for a given prefix fails, would the communications using that prefix be interrupted till the corresponding AAAA records in the DNS caches of IPv6 hosts expire?

This is exactly why each "box" is in fact many boxes whose state is 
synchronized.

Handling the complete failure of a set of such boxes is really up to the 
operator and doesn't need to be standardized, in my opinion. Many custom 
actions would need to be taken in such a case.

Simon
-- 
DNS64 open-source   --> http://ecdysis.viagenie.ca
STUN/TURN server    --> http://numb.viagenie.ca
vCard 4.0           --> http://www.vcarddav.org

v2.23.0 | Report a Bug | By Email