IETF Logo Mail Archive

Re: [Arcing] New Version Notification for draft-stw-whatsinaname-00.txt

Suzanne Woolf <suzworldwide@gmail.com> Wed, 13 July 2016 12:21 UTC

Return-Path: <suzworldwide@gmail.com>
X-Original-To: arcing@ietfa.amsl.com
Delivered-To: arcing@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0F8812DEE2 for <arcing@ietfa.amsl.com>; Wed, 13 Jul 2016 05:21:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 7S2cBusa1cVh for <arcing@ietfa.amsl.com>; Wed, 13 Jul 2016 05:21:12 -0700 (PDT)
Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::232]) (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 C33D712DF0C for <arcing@ietf.org>; Wed, 13 Jul 2016 05:21:11 -0700 (PDT)
Received: by mail-qk0-x232.google.com with SMTP id o67so41449003qke.1 for <arcing@ietf.org>; Wed, 13 Jul 2016 05:21:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=sXqbi4fzj6WJQPj84aHmy877rJiLcnBY79QN5/2f/5c=; b=AVi1SKA5gjQcFS61hniE2Oo+rgpwdCKKoZZYQiJLAjnULD5ZSvFFNLdFT9ZgdHU2jU cR51NNotdfaJQu5bZ+0ijmW+kdgKKVvj+FBPL2Ol7lMNv5fKxgvMxBk+IF2NCF/EERF6 oUEbqdWoH1x1dRzpbclpZumAMQ2RozB1gpoJeoNXVNxdxpXLGK0JfG8V4H2UGyq2Hi37 5/qXLeSjAWxAvVt54IF1YNNYobTRbKwbS2Wcn90irbCf3i0uArh5IbcjQTLX+yV2jT4d lVfMXE31fOTbIcGC40g57hTKkDJbsUp38x9OB+EkNFORRQ8h0eSHfSSfTbvNNoaW7jEj mSlQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=sXqbi4fzj6WJQPj84aHmy877rJiLcnBY79QN5/2f/5c=; b=fGU8+zrARh6CgHeII6VzzisbGKi7lV0OHWfrW6u24930krbLxaUjmGwTx1goSAINQf 5dLH2nFVX8sN5y3S5SwykPf/rd1hbqreTBqucPTEPw82gMdccRLgASoiAHFdKHmuJw/P oB4aOvIgU4RVcyWZFPjJ21wASTOt67ck8cO5jYyM3W2w6jUSKz0O0Wrx3mVL9WcFmkau t5EM3SdsbSMN+hwXJ1r2mlmtTpVE6k1XPDXZ0nOK308nWGPq1Xrq82odtyBaUYZ4smO3 zEJQP2lFLUGAoT0nrEoW8OZadKnxoqGtIl7ZzTCY+Nk9stH6Fegf/FLgNl092E5NzpvK fgAA==
X-Gm-Message-State: ALyK8tIYQ9Awv61x0o8CZHFOh1ii5ybR/Jn7qXUSOEUwi/4zRTndWMsUsQEhbmoNwrTEbg==
X-Received: by 10.55.192.143 with SMTP id v15mr9551592qkv.23.1468412470912; Wed, 13 Jul 2016 05:21:10 -0700 (PDT)
Received: from [10.0.0.16] (c-24-63-89-87.hsd1.ma.comcast.net. [24.63.89.87]) by smtp.gmail.com with ESMTPSA id j62sm732927qtb.35.2016.07.13.05.21.08 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 13 Jul 2016 05:21:09 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <alpine.OSX.2.11.1607121911320.56082@ary.lan>
Date: Wed, 13 Jul 2016 08:23:37 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C71641D2-1195-47E2-AB6C-29BA4B0FD115@gmail.com>
References: <20160712203057.33162.qmail@ary.lan> <68618C98-DCC2-41B6-869D-F470589B1C1C@gmail.com> <alpine.OSX.2.11.1607121746330.53471@ary.lan> <19C4F7E7-606D-4CCD-B598-510A0033AEFF@gmail.com> <alpine.OSX.2.11.1607121911320.56082@ary.lan>
To: John R Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: <https://mailarchive.ietf.org/arch/msg/arcing/1hC7BV79dFPhT34BF72BJEktLDk>
Cc: arcing@ietf.org
Subject: Re: [Arcing] New Version Notification for draft-stw-whatsinaname-00.txt
X-BeenThere: arcing@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: This list will discuss different architectural approaches to signalling alternative resolution contexts for Internet names <arcing.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/arcing>, <mailto:arcing-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/arcing/>
List-Post: <mailto:arcing@ietf.org>
List-Help: <mailto:arcing-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/arcing>, <mailto:arcing-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2016 12:21:13 -0000

On Jul 12, 2016, at 7:14 PM, John R Levine <johnl@taugh.com> wrote:

>> That draft would provide no guidance at all on deciding whether you want to use a domain name, use something from the subset of domain names that are DNS names, or do something else.  ...
> 
> Hm, I take your point.
> 
>> It would also provide no guidance at all on the characteristics of an acceptable string.
> 
> Some people I know were looking for names to use within a VPN and I suggested that the ISO 3166 list permanently reserves .xa through .xz which are unlikely ever to be TLDs, so they picked something like blah.xz. I wonder if that was good advice.

I don't know. 

Would asking the questions in Sec. 4 of the whatsinaname draft have helped them/you be sure? Do other questions come to mind?



Suzanne

v2.23.0 | Report a Bug | By Email