Re: [DNSOP] Interim DNSOP WG meeting on Special Use Names: some reading material

hellekin <hellekin@gnu.org> Fri, 08 May 2015 17:50 UTC

Return-Path: <hellekin@gnu.org>
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 B9C001B2E2A for <dnsop@ietfa.amsl.com>; Fri, 8 May 2015 10:50:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 4ysPNWlK-rCf for <dnsop@ietfa.amsl.com>; Fri, 8 May 2015 10:50:34 -0700 (PDT)
Received: from fencepost.gnu.org (fencepost.gnu.org [IPv6:2001:4830:134:3::e]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AD7B1B2E27 for <dnsop@ietf.org>; Fri, 8 May 2015 10:50:34 -0700 (PDT)
Received: from ol168-138.fibertel.com.ar ([24.232.138.168]:38428 helo=raiz.hellekin.gnu) by fencepost.gnu.org with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from <hellekin@gnu.org>) id 1YqmPv-000893-Vh for dnsop@ietf.org; Fri, 08 May 2015 13:50:32 -0400
Message-ID: <554CF750.6000807@gnu.org>
Date: Fri, 08 May 2015 14:50:08 -0300
From: hellekin <hellekin@gnu.org>
Organization: https://gnu.org/consensus
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.6.0
MIME-Version: 1.0
To: dnsop@ietf.org
References: <D5D3A5AC-41B5-4872-B973-2752275D651E@gmail.com> <D170E3E4.1011F2%jason_livingood@cable.comcast.com> <20150508013042.3B9252DEAD71@rock.dv.isc.org> <EF4521EF-8D06-403E-8869-8F2D4DDE76B8@virtualized.org>
In-Reply-To: <EF4521EF-8D06-403E-8869-8F2D4DDE76B8@virtualized.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/wpcd-7Dzwz3lau7QqxgqEuKntmE>
Subject: Re: [DNSOP] Interim DNSOP WG meeting on Special Use Names: some reading material
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: Fri, 08 May 2015 17:50:39 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 05/08/2015 01:48 PM, David Conrad wrote:
> Mark,
> 
>> "home", "corp" and perhaps "mail" need special handling if we really
>> want to not cause problems for those using those tlds internally.
> 
> Why?
> 
*** Citing IETF92 slides by Lyman Chapin and Mark McFadden: [0]

these are the 3 names that were identified as posing operational
hazards by SSAC and both ICANN name collision studies.

why?
• operational and engineering reasons only
• problems related to potential delegation of previously invalid labels
that have frequently appeared as queries to the root
  • lots of evidence here
    • https://www.icann.org/en/system/files/files/sac-045-en.pdf
  • affected labels
    • home
    • corp
• name collision problem
  • lots of evidence here as well
    • https://www.icann.org/en/system/files/files/sac-062-en.pdfhttps://www.icann.org/en/about/staff/security/ssr/name-collision-mitigat
ion-26feb14-en.pdf
  • affected label
    • mail

==
hk

[0]: https://www.ietf.org/proceedings/92/slides/slides-92-dnsop-9.pdf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQJ8BAEBCgBmBQJVTPdGXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFQ0IyNkIyRTNDNzEyMTc2OUEzNEM4ODU0
ODA2QzM2M0ZDMTg5ODNEAAoJEEgGw2P8GJg9GncP/jJVKUyyAQgFJyw2R8BMeUgO
VXWxuhSrhfgYP4UpEowaCRCaHrWaN7DsOeGmpTROGKjsoR4ynIWkp15rv+22SZyI
PrjtftuFR6H4JV+3iLjUq0Mm1cas8ytLGcPQt7lQo/gZzs7h2tXLsIoL+u1IYgoT
Irok3Y/0LwPM8tB7vL5AGGPOOUZvmRirXqCcPF7ZGg8adY0odY2rwwtm5cAGOaMB
QXk/Hky6ua464O0i7kCET/hZLtjIWLbeZxpso2jw+Sk3n78p4WZFZFvE6YfTNgHk
1gGS5/By764wgPg9FEEFLjFXnxIubjyJQMUqEuOIDJccuFxp5KiA+Bx8BZ1KTmbO
xmww7fVbKs/UmwP7Kq/sTwJpJGNi+PMs4MTzCtoM1MuxzyDi8WPU/mMxOnjJ+cSh
ZGR/OFFIbt564nDveSuuElFOhxpfyEma90zTMKkiU+cl48cW4VJ9/4KaZF12DvYb
MgLBHSo8osl5uBtt7Ppc6YvfGxgszBk2J6V04t8EqC1grbS8LTFbg4lUT9VQuyuL
JzSOvjsVlxlJwnDUnNF9dKRQCSzpXp8un5xGjtxE3bkvxuCTlrQFKlnbdRNtG3/A
I0KFK+mSdbe+oi0n1DEw6osAY5YJXZf9PJaN/a65dexkS98NT8Dx9/nfpB2/Is9I
rBaEIlkanMRGvoIBnQwp
=ZgS+
-----END PGP SIGNATURE-----