[DNSOP] moving forward on special use names

Suzanne Woolf <suzworldwide@gmail.com> Mon, 12 September 2016 20:19 UTC

Return-Path: <suzworldwide@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 6B2AC12B107 for <dnsop@ietfa.amsl.com>; Mon, 12 Sep 2016 13:19:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Status: No, score=-2.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, 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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id SqGlnUijPg3V for <dnsop@ietfa.amsl.com>; Mon, 12 Sep 2016 13:19:10 -0700 (PDT)
Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com [IPv6:2607:f8b0:400d:c09::230]) (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 04EC212B103 for <dnsop@ietf.org>; Mon, 12 Sep 2016 13:19:10 -0700 (PDT)
Received: by mail-qk0-x230.google.com with SMTP id t7so51863288qkh.2 for <dnsop@ietf.org>; Mon, 12 Sep 2016 13:19:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:subject:message-id:date:to:mime-version; bh=Mw1qo+aVZWz1fwr5LBabUHBNkkc36mFBRPRPgJk/g1g=; b=aoDZut9ZAEu69kpLQ51BJlUnt0P0DPDl7apBXtdY8EhOhjePNC2rPyd6ODfFWc3waH DkSIlXCwzNwq4fpniMQlUXUB66ZKBGXP/uXMWmPDwJ+O/WGXcM/nJ03oHw1zLuFGFn3x 5KRocZaBa+uicN4z2T2pIyE0MqQsqRtOGHDMRjaATIjqtFmTQWiWWvlLuZcoWRTPdwRG JzoZKYmatPdOWLXGzv0sBmkmLhh4L3Zdb8S8sfS3g2iE9Xdk6H0IsLRSFBjRIzSJsf+c cln9YfGMriEHemCDSG+BnDwSphztpuAjUhrRZ4EOWbyFGNjIon4DFdWg0th1N4/VHFFA oirQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:subject:message-id:date:to:mime-version; bh=Mw1qo+aVZWz1fwr5LBabUHBNkkc36mFBRPRPgJk/g1g=; b=DxPmQI4++MXUdSWdiHZwUl2WSH9FRr9P3rq/cI/IKe/RqU2XOz+UiSvehCQavFaaGa aDCFEnqQ6DvVAL4lfIQ3vmNc4sTioEja0IULsdYIb9zcreHJhNswFZHSNqAjAli/ZqwD OjHx2AhXGJcBxqHgdOunfAsIfjNYWsuqRXFsxn0T0k+g4VdgUqwPNshPUO+HlXqJURh6 FB7XLHgmhvm5KUWWVsJcI36uJykD4eQmtCDp5LK6AninB3zeT30GLw6J610rOBs2pOZq LLPKv+PG1nl4/pQyGX5R0aGRGQPQEPCzaJJqcF1+E5qipZZfeguHybZXKlVPW2CHZwFo eRKA==
X-Gm-Message-State: AE9vXwN0pr380ccuK/jWvO4K3T6dUaEJ8jsqWGzhl1S7ThIDW6y0AJr7BqyVgcpvVEdc1Q==
X-Received: by with SMTP id l73mr23275744qki.257.1473711548660; Mon, 12 Sep 2016 13:19:08 -0700 (PDT)
Received: from [] ([]) by smtp.gmail.com with ESMTPSA id g16sm11521194qke.23.2016. for <dnsop@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 12 Sep 2016 13:19:07 -0700 (PDT)
From: Suzanne Woolf <suzworldwide@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_DA4BA6CA-D602-485F-A9D3-17B009A55AEF"
Message-Id: <D60BBDEF-3C13-44CB-A0D9-DEA98F5297F5@gmail.com>
Date: Mon, 12 Sep 2016 16:19:06 -0400
To: dnsop WG <dnsop@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/r-F17Cruc6sXMNdCvzFZ42byXTQ>
Subject: [DNSOP] moving forward on special use names
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 12 Sep 2016 20:19:12 -0000

Dear Colleagues,

As we discussed in Berlin, we need to move forward with adopting a problem statement draft for further work on special use domain names. 

Issues of usage around the domain name space are part of our charter, and the IESG has expressed interest more than once in having a clear basis for dealing with future cases such as the request for .onion in the special use domain names registry or the needs of the HNCP protocol. The Chairs determined that the WG should have a problem statement before attempting to specify changes to RFC 6761 or other possible solutions. 

The problem statement needs to be a WG document, with a WG commitment to get to consensus on it.

We have two internet-drafts that have been submitted for discussion as problem statements. They’re both individual submissions and the work of their named authors. They cover many common features of the landscape but they’re also written from slightly different viewpoints. It seems unlikely that they can be combined, so we simply have to ask the WG to choose.

Both drafts have been revised in the last few days. 

The drafts are:
	https://datatracker.ietf.org/doc/draft-tldr-sutld-ps/ <https://datatracker.ietf.org/doc/draft-tldr-sutld-ps/>
	https://datatracker.ietf.org/doc/draft-adpkja-dnsop-special-names-problem/ <https://datatracker.ietf.org/doc/draft-adpkja-dnsop-special-names-problem/>
We’re opening a 2-week discussion period for the WG, to end on Sept. 26. At the end of that time we’ll adopt one of these drafts for further work by the WG. 

Shortly thereafter we will also be soliciting views on how the IETF might address the problems we’ve identified with special use domain names.

Please read these drafts and tell us which you think the WG can adopt as a problem statement, from the IETF perspective, about the various issues we’ve discussed on special use names. We need your comments on the record— being able to demonstrate the WG’s decision process is important— so please write to the list.

Assuming some level of agreement on a problem statement, we’re tentatively scheduling an interim WG meeting for next steps, in mid-October.

thanks all,
Tim & Suzanne