Re: [dnsext] errata on RFC1034 for recursive aliasing and name based diffrentiation

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Sun, 06 March 2011 00:29 UTC

Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 2328E3A6A32 for <dnsext@core3.amsl.com>; Sat, 5 Mar 2011 16:29:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.095
X-Spam-Level:
X-Spam-Status: No, score=-0.095 tagged_above=-999 required=5 tests=[AWL=-0.005, 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 IaeZzLBavZD8 for <dnsext@core3.amsl.com>; Sat, 5 Mar 2011 16:29:03 -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 DEE643A6A16 for <dnsext@ietf.org>; Sat, 5 Mar 2011 16:29:02 -0800 (PST)
Received: (qmail 31151 invoked from network); 6 Mar 2011 00:45:25 -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; 6 Mar 2011 00:45:25 -0000
Message-ID: <4D72D555.4060109@necom830.hpcl.titech.ac.jp>
Date: Sun, 06 Mar 2011 09:29:09 +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.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Brian Dickson <brian.peter.dickson@gmail.com>
References: <20110227191542.6824.qmail@joyce.lan> <335963D7-3440-45E6-843C-38F419462792@cisco.com> <4D6C3FD3.7010801@ucd.ie> <302DAD77E927757D3DEA05DF@nimrod.local> <alpine.LSU.2.00.1103031107460.14985@hermes-1.csi.cam.ac.uk> <20110303114148.A360FB98E2E@drugs.dv.isc.org> <alpine.LSU.2.00.1103031148130.14985@hermes-1.csi.cam.ac.uk> <4D703A35.9080207@necom830.hpcl.titech.ac.jp> <4D705952.6000409@necom830.hpcl.titech.ac.jp> <20110304050809.E7F09BA7287@drugs.dv.isc.org> <AANLkTikBfdxasG2uUYJTveMiOtLZg4zUQYjfEL5swmgY@mail.gmail.com>
In-Reply-To: <AANLkTikBfdxasG2uUYJTveMiOtLZg4zUQYjfEL5swmgY@mail.gmail.com>
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
Cc: dnsext@ietf.org
Subject: Re: [dnsext] errata on RFC1034 for recursive aliasing and name based diffrentiation
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>
X-List-Received-Date: Sun, 06 Mar 2011 00:29:04 -0000

Brian Dickson wrote:

> Are there things that either *require*, or can *only* be
> done with, CNAMEs?

Aliasing.

> Instead of having a CNAME:

> have a *zone cut* (on both the "CNAME"-wannabe, and on the would-be

Often, administrators of a canonical name and an alias are
different.

When a user of name based virtual hosting rent hosting and DNS
service from different providers, neither the user nor the DNS
service provider can know when updates occur on the canonical
name.

					Masataka Ohta