Re: [DNSOP] draft-wkumari-dnsop-alt-tld-04

George Michaelson <ggm@algebras.org> Fri, 13 February 2015 06:23 UTC

Return-Path: <ggm@algebras.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 345741A0AF1 for <dnsop@ietfa.amsl.com>; Thu, 12 Feb 2015 22:23:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 Wwthmh9jAq8o for <dnsop@ietfa.amsl.com>; Thu, 12 Feb 2015 22:23:40 -0800 (PST)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56D0A1A03A2 for <dnsop@ietf.org>; Thu, 12 Feb 2015 22:23:40 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id kq14so16806067pab.3 for <dnsop@ietf.org>; Thu, 12 Feb 2015 22:23:40 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=vgV75s9kWBYgFpjU7HrZP0Bq06s+vnEPgSsiSzbidjE=; b=dgdLtgYE2TG9VuYmVsVIU+vD4s2nDrXRWO9C38AQg+v/wmu2+yL3WHQPWU2d5cmG3W pRLXUzJ/ruh/dZEd4xc6ognwrTuFWcBEPBCFT6p6ztoIBatei+d/CWqcSwxOUqie7LMq PPZAyBFBHtz854Ua7LqOpIT0CWHbrHYjaNKr6zjLyiVVAzbAuPkNZT59WZQ7+604NyEs VwlQFnFRMCx3uytskuYcduKENuTr6cAmyj5HHTPIFds7o7gEDsvaBxz3pRh7tSZvj/HU r1XVLY9pObQz0V5jCUaN/hipBb7nNyVs8uymDg4/ph/R93xcxcFE+O/3QpUzgXl+WQcs oZEQ==
X-Gm-Message-State: ALoCoQnVgWTiJnN6Dbc2KTzIe8DbVXKnPaLGPekaVVF3oo6TfvHyOFuKYT/HPH3tpiwCqzAN9Jji
MIME-Version: 1.0
X-Received: by 10.68.200.201 with SMTP id ju9mr12393869pbc.157.1423808619995; Thu, 12 Feb 2015 22:23:39 -0800 (PST)
Received: by 10.70.67.226 with HTTP; Thu, 12 Feb 2015 22:23:39 -0800 (PST)
X-Originating-IP: [2001:dc0:a000:4:ed48:f9bc:7f93:44a5]
In-Reply-To: <54DD8F8F.7030506@redbarn.org>
References: <20150212063638.GD6950@mx1.yitter.info> <CAKr6gn302PSFdqVwH2m=drEZ02_kw+3ioQ4Wz++LnVyK6Z_PDA@mail.gmail.com> <6899C83F-BC3E-493D-ABC8-121B1BA72785@virtualized.org> <54DD8F8F.7030506@redbarn.org>
Date: Fri, 13 Feb 2015 16:23:39 +1000
Message-ID: <CAKr6gn0XRsv-bWvgRQYMOhHyukCDGLEG19sj31cwH8--VjcmFQ@mail.gmail.com>
From: George Michaelson <ggm@algebras.org>
To: Paul Vixie <paul@redbarn.org>
Content-Type: multipart/related; boundary="047d7b15ae3106184e050ef24734"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/AyKUT3uhl-mZgtBWgUIzI7Fyg00>
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] draft-wkumari-dnsop-alt-tld-04
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Feb 2015 06:23:43 -0000

how about if the rules of sub-delegation under ALT are that 1) you only get
an OID 2) the OID has to be registered with IANA in the normal way 3) the
OID registry identifies the external namespace, which is being bound into
the system.

Then, it becomes clear this is a mapping space for functions like
gethostbyname() to have as a context specific search string, and are
significantly less likely to collide with GTLD since they are simply digit
strings.

On Fri, Feb 13, 2015 at 3:45 PM, Paul Vixie <paul@redbarn.org> wrote:

>
>
>   David Conrad <drc@virtualized.org>
>  Thursday, February 12, 2015 5:38 PM
>
> George,
>
>
> The politics response is really simple: "this idea is doomed." -I wish I felt otherwise, but I think given the context of the debate over ICANN, who 'owns' names, $180,000 application fees, IAB directions to IANA, NTIA role, this is mired.  I don't want to be a prophet of doom, but this is my honest perspecive.
>
> As with most "really simple" answers, the reality is a bit more complicated.  My impression of this draft is that it creates a space that would avoid some of the risks associated with RFC 6761. Politically, I suspect this is desirable, even to all the parties you mention. As for the fee, ICANN already defers to the IETF in protocol-related matters, so I don't see why a new gTLD fee would be applicable.  With my ICANN hat on, I'll look into this and report what I hear back.
>
>
> can we sit back and ponder what it will mean if .ALT becomes an implicit
> extra search list for many end users, and then xyzzy.alt is created, and
> later, .xyzzy is created. i expect this eventuality to spur considerable
> interest from icann, perhaps coming in the form of "since we can't control
> what the ietf does with implicit search list behaviour, we're skittish
> about allowing something like .ALT to come into existence that would, when
> combined with implicit search lists, lead to complete and utter chaos."
>
> this is not in other words simply a protocol-related matter.
>
> --
> Paul Vixie
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
>