Re: [dnsext] we need help to make names the same, was draft-yao-dnsext-identical-resolution-02 comment

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Wed, 16 February 2011 13:22 UTC

Return-Path: <dnsext-bounces@ietf.org>
X-Original-To: namedroppers-archive-gleetwall6@lists.ietf.org
Delivered-To: ietfarch-namedroppers-archive-gleetwall6@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AFECD3A6CC6; Wed, 16 Feb 2011 05:22:30 -0800 (PST)
X-Original-To: dnsext@core3.amsl.com
Delivered-To: dnsext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 811993A6CB8 for <dnsext@core3.amsl.com>; Wed, 16 Feb 2011 05:22:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.123
X-Spam-Level:
X-Spam-Status: No, score=-0.123 tagged_above=-999 required=5 tests=[AWL=-0.033, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 5TdVm3h2DWWD for <dnsext@core3.amsl.com>; Wed, 16 Feb 2011 05:22:28 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by core3.amsl.com (Postfix) with SMTP id 798BC3A6B74 for <dnsext@ietf.org>; Wed, 16 Feb 2011 05:22:27 -0800 (PST)
Received: (qmail 47658 invoked from network); 16 Feb 2011 13:32:43 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 16 Feb 2011 13:32:43 -0000
Message-ID: <4D5BCF70.90104@necom830.hpcl.titech.ac.jp>
Date: Wed, 16 Feb 2011 22:21:52 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: dnsext@ietf.org
References: <20110216073338.7251.qmail@joyce.lan> <BE5119E0A9AF9C470D3D362A@nimrod.local> <alpine.BSF.2.00.1102152352430.11303@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1102152352430.11303@joyce.lan>
Subject: Re: [dnsext] we need help to make names the same, was draft-yao-dnsext-identical-resolution-02 comment
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dnsext-bounces@ietf.org
Errors-To: dnsext-bounces@ietf.org

John R. Levine wrote:

> I also have a general dislike of any design that requires two things to 
> be kept in sync manually, with random failures if they're not. If a set 
> of names really is all equivalent, wouldn't it be better in the long run 
> for people to configure the set once rather than once per server?

Equivalence rule must run very long, maybe forever.

Or, if the rule is not stable, we shouldn't start registration
only to cause conflicts between registered names before and
after rule changes.

With the stable rule in hand, we can expect the rule configured
in factory on all clients.

The problem, of course, is how can we have the stable rule.

						Masataka Ohta
_______________________________________________
dnsext mailing list
dnsext@ietf.org
https://www.ietf.org/mailman/listinfo/dnsext