Re: [DNSOP] draft-adpkja-dnsop-special-names-problem-01

"Paul Hoffman" <paul.hoffman@vpnc.org> Wed, 30 March 2016 12:44 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8382B12E268 for <dnsop@ietfa.amsl.com>; Wed, 30 Mar 2016 05:44:05 -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 xOzcBlAjO7S3 for <dnsop@ietfa.amsl.com>; Wed, 30 Mar 2016 05:43:59 -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 A5BB612E1F2 for <dnsop@ietf.org>; Wed, 30 Mar 2016 05:33:15 -0700 (PDT)
Received: from [10.32.60.70] ([200.54.58.234]) (authenticated bits=0) by mail.proper.com (8.15.2/8.14.9) with ESMTPSA id u2UCXBwc099051 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <dnsop@ietf.org>; Wed, 30 Mar 2016 05:33:13 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host [200.54.58.234] claimed to be [10.32.60.70]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: dnsop@ietf.org
Date: Wed, 30 Mar 2016 09:33:10 -0300
Message-ID: <CC857311-DFE7-4385-8509-266352312400@vpnc.org>
In-Reply-To: <20160329215722.GB22553@mx2.yitter.info>
References: <20160328183306.GB20143@mx2.yitter.info> <963B0824-CDC7-4918-A8FF-A0825ACC20C0@virtualized.org> <20160328192233.GD20143@mx2.yitter.info> <CDABA57F-F977-4D98-8DB8-2F36E9168AB6@icann.org> <BCCF3038-B256-442D-B94F-390EE3A3F6ED@gmail.com> <B85BE572-732F-4F55-ADE3-D221A814C6E4@icann.org> <20160329020511.GF20143@mx2.yitter.info> <17F8172E-ED13-4E50-B0D3-0E3B03038954@icann.org> <20160329033629.GG20143@mx2.yitter.info> <B21BF4D9-3552-4F5E-8A2A-D34FDE5C110F@virtualized.org> <20160329215722.GB22553@mx2.yitter.info>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/k5zcQlWOtyjAm15_HnXKVB3NBnA>
Subject: Re: [DNSOP] draft-adpkja-dnsop-special-names-problem-01
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: Wed, 30 Mar 2016 12:44:05 -0000

On 29 Mar 2016, at 18:57, Andrew Sullivan wrote:

> To that claim I
> respond that we'd need evidence that we have such a problem.

draft-grothoff-iesg-special-use-p2p-names claimed BIT and ZKEY, both of 
which are trademarked. The fact that we pretty much told developers to 
not bother us with name applications while with consider 6761bis should 
not be used as a tool to suggest non-existence of problems.

But I also fundamentally disagree that "trademarks" are the only naming 
problem we have. Even untrademarked names can have control issues. 
During the run-up to the current work, this WG heard claims that there 
were different digital cash systems that would want names. Does the 
first of them to get an RFC get "CASH"? During the technical 
considerations for that first application, if a second system also uses 
"CASH" as a switch and rapidly becomes bigger than the first, does the 
IETF consensus process need to take that into account? It is implausible 
that a IETF consensus review of a name application could *not* consider 
topics such as term squatting.

Maybe 6761bis will have prohibitions on any consideration of term 
squatting and trademarks during the technical review, but we have not 
seen any evidence of such wording.

--Paul Hoffman