Re: [DNSOP] RFC 6761 discussion (“special names”)

Suzanne Woolf <suzworldwide@gmail.com> Tue, 17 March 2015 23:14 UTC

Return-Path: <suzworldwide@gmail.com>
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 CEF031A1EF7 for <dnsop@ietfa.amsl.com>; Tue, 17 Mar 2015 16:14:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 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, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 VUHL7aVbtoDc for <dnsop@ietfa.amsl.com>; Tue, 17 Mar 2015 16:14:50 -0700 (PDT)
Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com [IPv6:2607:f8b0:400d:c04::22c]) (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 63B5F1A1B9C for <dnsop@ietf.org>; Tue, 17 Mar 2015 16:14:50 -0700 (PDT)
Received: by qgf3 with SMTP id 3so23121031qgf.3 for <dnsop@ietf.org>; Tue, 17 Mar 2015 16:14:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=N46yoaI1DV0G4xoZBX19S7AzJmN7g778Q1H0BlNJv7k=; b=bhh1BX5TY9To8vjhZydjkgGo+aPdL3czbcw/3Y+M46jjoT+C19CslgqzRXwsuqZKwj IyazYa071wAwGQTDwXxdg065/3bxid+IQlyS9LICO2/YhnF6gnJrx3Eb2LB1+XYwOWfS 6lwy4J6b/MnDHRZXK/0HvefUKw63eQnFwlvTfkd/vhzcpLdMxszm7BdOaaRdwjH7p5jR Pqqg7QJIRhP+8/xFDno03lApdP4QxMIAVS9QbtBZhSO5xkYF2ouL01itqJLtN6p4EG4E L6xb0wq51kaxPkugkXKgkWx4DH9vrrEbgjihgIZmMc+eEVL9G514LmRS3SweKPYAzIZ+ 5Umw==
X-Received: by 10.55.55.141 with SMTP id e135mr88837732qka.78.1426634089650; Tue, 17 Mar 2015 16:14:49 -0700 (PDT)
Received: from ?IPv6:2601:6:3a80:77e:d106:7434:e56d:4031? ([2601:6:3a80:77e:d106:7434:e56d:4031]) by mx.google.com with ESMTPSA id t75sm10681519qgd.42.2015.03.17.16.14.48 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 17 Mar 2015 16:14:48 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_D2611291-7C36-40A3-9CFB-2BAA386E7357"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <5508A1FA.6050108@gnu.org>
Date: Tue, 17 Mar 2015 19:14:46 -0400
Message-Id: <DF8C73AD-70F6-4412-A3F4-D7938CB54108@gmail.com>
References: <55089F07.5020200@gmail.com> <5508A1FA.6050108@gnu.org>
To: hellekin <hellekin@gnu.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/M3E2nS0_WxkRgFN9l1-iyr8u1rg>
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] RFC 6761 discussion (“special names”)
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: Tue, 17 Mar 2015 23:14:52 -0000

On Mar 17, 2015, at 5:51 PM, hellekin <hellekin@gnu.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> On 03/17/15 18:39, Tim Wicinski wrote:
>> 
>> the implications of widening use of RFC 6761.
>> 
> *** You certainly mean: the implications of using RFC 6761, given that
> so far, it's only been used by its creator, Apple Inc. in RFC 6762 (if
> 6761 itself is not counted).

Sorry if this wasn't clear, perhaps a result of trying to get the idea of the interim meeting out without enough wordsmithing.

Actually we meant the increasing numbers of drafts submitted as requests under RFC 6761, in under a year since we revised our charter to include them, and the number of strings included.

Currently, there are six drafts, most appearing in the last few weeks. They request reservations of a total of about 40 strings, if I'm doing the arithmetic in draft-lewis-user-assigned-tlds correctly. Some (such as yours) are clearly intended to support new functionality, in accordance with the purpose indicated in RFC 6761; some others are less clear as to their purpose.

It seems appropriate to ask what implications, if any, might follow.

> "widening use of RFC 6761" sounds to me like its use should be reserved
> to some entities over others.  It does not seem fair, and implies that
> RFC 6761 cannot be used like any other RFCs.  Did I read something wrong?

It was not anyone's intention that RFC 6761 should "be reserved to some entities over others." It, and we, are silent as to the entities who might be asking for special names. Like most RFCs, however, RFC 6761 does distinguish among requests on other attributes.

Scalability of the process in RFC 6761 and the criteria for special names seems like an appropriate concern for DNSOP and the IETF to us.

Do you have feedback on the idea of an interim meeting for DNSOP to address these drafts in more depth than we will be able to offer at the IETF meeting in Dallas?


much thanks,
Suzanne & Tim