[Bundled-domain-names] Solutions in draft-yao-bundled-name-problem-statement-02.txt

"Paul Hoffman" <paul.hoffman@vpnc.org> Tue, 25 October 2016 23:47 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: bundled-domain-names@ietfa.amsl.com
Delivered-To: bundled-domain-names@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3BC7129997 for <bundled-domain-names@ietfa.amsl.com>; Tue, 25 Oct 2016 16:47:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4m8ALSqKyEwQ for <bundled-domain-names@ietfa.amsl.com>; Tue, 25 Oct 2016 16:47:09 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE9ED129978 for <bundled-domain-names@ietf.org>; Tue, 25 Oct 2016 16:47:09 -0700 (PDT)
Received: from [10.32.60.89] (50-1-99-230.dsl.dynamic.fusionbroadband.com [50.1.99.230]) (authenticated bits=0) by mail.proper.com (8.15.2/8.14.9) with ESMTPSA id u9PNl6Hh010649 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <bundled-domain-names@ietf.org>; Tue, 25 Oct 2016 16:47:07 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 50-1-99-230.dsl.dynamic.fusionbroadband.com [50.1.99.230] claimed to be [10.32.60.89]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: bundled-domain-names@ietf.org
Date: Tue, 25 Oct 2016 16:47:06 -0700
Message-ID: <EBD2B71C-725D-4419-9B70-CEDCEB2CEED4@vpnc.org>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
X-Mailer: MailMate (1.9.5r5263)
Archived-At: <https://mailarchive.ietf.org/arch/msg/bundled-domain-names/KelsyimiMdeNefbh77yLXe4CsQM>
Subject: [Bundled-domain-names] Solutions in draft-yao-bundled-name-problem-statement-02.txt
X-BeenThere: bundled-domain-names@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussion of \"bundled domain names\"" <bundled-domain-names.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bundled-domain-names>, <mailto:bundled-domain-names-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bundled-domain-names/>
List-Post: <mailto:bundled-domain-names@ietf.org>
List-Help: <mailto:bundled-domain-names-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bundled-domain-names>, <mailto:bundled-domain-names-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Oct 2016 23:47:11 -0000

Greetings. Section 3 of this document quickly moves away from being a 
problem statement into being a history of solutions. Sections 3.3 and 
3.4 seem like descriptions of earlier work, not problem statements. 
Proposed rewording:

3.3.  Mapping a name and and its descendants

    The bundle of variant domain names requires mapping of a whole tree
    of the domain space to another domain.  The current DNS protocols do
    not support this function.

3.4.  Cloning a zone

    A mechanism for processing master files or their equivalent in a DNS 
server
    could direct that server
    to exactly replicate the content of a DNS zone into one or more 
other
    DNS zones so that the content is reachable by multiple names at
    different zone apexes.  A problem for this method is that
    it cannot deal with child names that are delegated.


--Paul Hoffman