Return-Path: <suzworldwide@gmail.com>
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 785FE132441
 for <dnsop@ietfa.amsl.com>; Sat, 19 Aug 2017 20:03:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
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 ([4.31.198.44])
 by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id ITNii9BkH7KE for <dnsop@ietfa.amsl.com>;
 Sat, 19 Aug 2017 20:03:45 -0700 (PDT)
Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com
 [IPv6:2607:f8b0:400d:c09::233])
 (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 5737D132436
 for <dnsop@ietf.org>; Sat, 19 Aug 2017 20:03:45 -0700 (PDT)
Received: by mail-qk0-x233.google.com with SMTP id x77so25600908qka.5
 for <dnsop@ietf.org>; Sat, 19 Aug 2017 20:03:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; 
 h=mime-version:subject:from:in-reply-to:date:cc:message-id:references
 :to; bh=8Z6padfKVmGgfNQuIF9hKW+uZ7+lODQ1E9GD4mz7EjI=;
 b=Hh+yKoiJvMM7szNUzhLUPOB1adWYUgbq1il5jRrXvoBiFoLSPQ/q884yhQPFSzkAnI
 ToJZHKwida8ZyK1yyjBl4zldVtX0A01QE2LOWL8k/G3JLZ/IezqDtfThd7zdmSmRNl9j
 bTWbFU4TI43anK2KlqoOotKm25+Rr+MRY26B5fvAC5gywZZYO3WLXLLztbw3bCSWtMXM
 ZX/JEw/P5KcVmVklNkCJTYR2JVgW9MsAghEBvwUm9Vb07qLdef6eABgoBZkMtu11YKUp
 QzRuPyHCNSNPFgs3qU5uXl03cdGQrWDvxwyaBs2SAqxdDuuBtoqJatvnVeOfebHKLu42
 9QEw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc
 :message-id:references:to;
 bh=8Z6padfKVmGgfNQuIF9hKW+uZ7+lODQ1E9GD4mz7EjI=;
 b=EhFtkZlMa+uR39u/z/bmU0gY+n5zBtaUal5N1IBwIjSGlSViXvOT+SL/I1g2qPkN4n
 yn5PeIFBtPsa//ZkkKtc4dDOOaHL4pa4LSdZ/sPfPJAAog93MBsIMIUNY6vAAasBM0qa
 ai1/LmzrRZCYvivcE4z7BbH/iOqyzIAnKxkDw8MfQuDH3U4dTA+PE4ZQr/mlR+rziAw3
 3J78US/AW+oee1rV3UrGkJfkEj+y9DmGSjGcThD52zibFuP8aIwh3AiCyjRvvmmeP6T/
 STjX2RIalAg3sYCF18kf0yYaie5UXiBERZwTaG9E/IF18jOb/27bfI8/Wron8fN+aMLZ
 aNFQ==
X-Gm-Message-State: AHYfb5gRN42G9ivkSO6n7Rz7fSdJiGZFAAcyLF5+KkiqSONDy1u72gyb
 HT6hJ4nS8oRGiXvX
X-Received: by 10.55.12.1 with SMTP id 1mr18071197qkm.319.1503198224530;
 Sat, 19 Aug 2017 20:03:44 -0700 (PDT)
Received: from [10.0.0.22] (c-24-63-89-87.hsd1.ma.comcast.net. [24.63.89.87])
 by smtp.gmail.com with ESMTPSA id
 a12sm4803245qta.66.2017.08.19.20.03.43
 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128);
 Sat, 19 Aug 2017 20:03:43 -0700 (PDT)
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_C0BD357D-E30E-43E4-B8D1-79E0066AE0B0"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <61AE518D-10D7-42BF-89BE-15FB5DC1EE75@nic.br>
Date: Sat, 19 Aug 2017 23:03:41 -0400
Cc: dnsop <dnsop@ietf.org>
Message-Id: <BEC44DF6-EB2D-4421-BAA2-B87942E320A5@gmail.com>
References: <61AE518D-10D7-42BF-89BE-15FB5DC1EE75@nic.br>
To: Rubens Kuhl <rubensk@nic.br>
X-Mailer: Apple Mail (2.1510)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Zo4sxIYziuu3nQc4g8H2e3OmbeY>
Subject: Re: [DNSOP] ICANN Name collision framework
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 20 Aug 2017 03:03:47 -0000


--Apple-Mail=_C0BD357D-E30E-43E4-B8D1-79E0066AE0B0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Hi,


On Aug 19, 2017, at 11:47 AM, Rubens Kuhl <rubensk@nic.br> wrote:

> (Sorry if you have received more than 1 copy of this e-mail, since =
this is being sent to technical mailing lists focusing on DNS)
>=20
> There is ongoing policy development effort within ICANN towards =
subsequent procedures of new gTLDs releases; during the last round in =
2012, one of the last pieces of the program to be defined was the name =
collision framework, detailed at =
https://www.icann.org/resources/pages/name-collision-2013-12-06-en .=20
>=20
> The current thinking is to keep most of the framework as it was in =
that round, with minor changes for low risk strings and some more detail =
for other strings. The base principle is to use research-accessible =
trusted databases such as DITL and ORDINAL to make decisions.=20

It's very good to see this outreach regarding the ICANN gTLD policy =
process, and this specific topic may well be of interest to DNSOP =
participants.

However, it's also not a core topic for this group, and is likely to be =
of interest to others as well.  Is there a dedicated mailing list, wiki, =
or other venue for people to offer their comments or continue the =
discussion?

There is a reference in the text to "the WG" ("Some of the questions =
still to be answered by the WG include=85") Could you expand the =
reference? Where can an interested DNSOP participant go to find out more =
about this WG and its work to date?


thanks,
Suzanne



--Apple-Mail=_C0BD357D-E30E-43E4-B8D1-79E0066AE0B0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Hi,<div><br></div><div><br><div><div>On Aug 19, 2017, at 11:47 AM, =
Rubens Kuhl &lt;<a href=3D"mailto:rubensk@nic.br">rubensk@nic.br</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space;" class=3D""><div =
style=3D"margin: 0px; line-height: normal;" class=3D"">(Sorry if you =
have received more than 1 copy of this e-mail, since this is being sent =
to technical mailing lists focusing on DNS)</div><div style=3D"margin: =
0px; line-height: normal; min-height: 14px;" class=3D""><br =
class=3D""></div><div style=3D"margin: 0px; line-height: normal;" =
class=3D"">There is ongoing policy development effort within ICANN =
towards subsequent procedures of new gTLDs releases; during the last =
round in 2012, one of the last pieces of the program to be defined was =
the name collision framework, detailed at <a =
href=3D"https://www.icann.org/resources/pages/name-collision-2013-12-06-en=
" =
class=3D"">https://www.icann.org/resources/pages/name-collision-2013-12-06=
-en</a> .&nbsp;</div><div style=3D"margin: 0px; line-height: normal; =
min-height: 14px;" class=3D""><br class=3D""></div><div style=3D"margin: =
0px; line-height: normal;" class=3D"">The current thinking is to keep =
most of the framework as it was in that round, with minor changes for =
low risk strings and some more detail for other strings. The base =
principle is to use research-accessible trusted databases such as DITL =
and ORDINAL to make =
decisions.&nbsp;</div></div></blockquote></div><br></div><div>It's very =
good to see this outreach regarding the ICANN gTLD policy process, and =
this specific topic may well be of interest to DNSOP =
participants.</div><div><br></div><div>However, it's also not a core =
topic for this group, and is likely to be of interest to others as well. =
&nbsp;Is there a dedicated mailing list, wiki, or other venue for people =
to offer their comments or continue the =
discussion?</div><div><br></div><div>There is a reference in the text to =
"the WG" ("Some of the questions still to be answered by the WG =
include=85") Could you expand the reference? Where can an interested =
DNSOP participant go to find out more about this WG and its work to =
date?</div><div><br></div><div><br></div><div>thanks,</div><div>Suzanne</d=
iv><div><br></div><div><br></div></body></html>=

--Apple-Mail=_C0BD357D-E30E-43E4-B8D1-79E0066AE0B0--

