[dnsext] New Version Notification for draft-barton-clone-dns-labels-fun-profit-00

Doug Barton <dougb@dougbarton.us> Mon, 07 March 2011 13:55 UTC

Return-Path: <dougb@dougbarton.us>
X-Original-To: dnsext@core3.amsl.com
Delivered-To: dnsext@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id C66133A6967 for <dnsext@core3.amsl.com>; Mon, 7 Mar 2011 05:55:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.564
X-Spam-Status: No, score=-2.564 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id M6P+AaZK7TgK for <dnsext@core3.amsl.com>; Mon, 7 Mar 2011 05:55:17 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com []) by core3.amsl.com (Postfix) with ESMTP id 346B63A67B4 for <dnsext@ietf.org>; Mon, 7 Mar 2011 05:55:17 -0800 (PST)
Received: (qmail 21089 invoked by uid 399); 7 Mar 2011 13:56:26 -0000
Received: from router.ka9q.net (HELO doug-optiplex.ka9q.net) (dougb@dougbarton.us@ by mail2.fluidhosting.com with ESMTPAM; 7 Mar 2011 13:56:26 -0000
X-Sender: dougb@dougbarton.us
Message-ID: <4D74E409.1060409@dougbarton.us>
Date: Mon, 07 Mar 2011 05:56:25 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv: Gecko/20110304 Thunderbird/3.1.9
MIME-Version: 1.0
To: dnsext@ietf.org
X-Enigmail-Version: 1.1.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [dnsext] New Version Notification for draft-barton-clone-dns-labels-fun-profit-00
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: Mon, 07 Mar 2011 13:55:18 -0000

Hash: SHA256

As promised I've managed to squeak this draft in under the wire. As I
say in the Foreword I expect that it will need some polishing, and if
the group chooses to adopt the document I look forward to getting lots
of help with that. :)



- -------- Original Message --------
Subject: New Version Notification for
Date: Mon,  7 Mar 2011 05:47:21 -0800 (PST)
From: IETF I-D Submission Tool <idsubmission@ietf.org>
To: dougb@dougbarton.us

A new version of I-D, draft-barton-clone-dns-labels-fun-profit-00.txt
has been successfully submitted by Douglas Barton and posted to the IETF

Filename:	 draft-barton-clone-dns-labels-fun-profit
Revision:	 00
Title:		 Cloning Domain Name System (DNS) Labels for Fun and Profit
Creation_date:	 2011-03-07
WG ID:		 Independent Submission
Number_of_pages: 11

This document describes a method for making one or more Domain Name
System (DNS) labels behave in the DNS "as if" they were actually an
entirely different label.  E.g., the delegee for the example.org zone
could define bar.example.org to be a CLONE of foo.example.org.  This
method is designed to meet the needs of those managing
Internationalized Domain Name (IDN) zones that have been determined
to be semantically similar, and therefore should be treated "as if"
they were identical.  This method can also be used more generally to
handle situations where currently either CNAME or DNAME Resource
Records are being used.

A key design goal for the CLONE method is that except for DNSSEC
support all of the semantic benefits are available by updating the
authoritative servers for the zone.  Therefore unless DNSSEC support
for the CLONEd zones is required there is no dependency on end users
being behind a CLONE-Aware resolving name server.


[RFC Editor, please remove this Section at publication time.

This is my first draft, please be gentle. :) I'm definitely open to
the possibility that there are better ways to accomplish the concepts
presented herein.  I'm sure that there are a non-zero number of
errors in the formatting, references, etc.  Also Sections 2 and 3 may
be under-specified, unclear, or unworkable.  So please don't be
afraid to offer (constructive) criticism.


Update/add/improve references?

Add/improve examples?

Revision History:
1.  -00 Initial version

The IETF Secretariat.

Version: GnuPG v2.0.17 (FreeBSD)