Re: [DNSOP] About reserving .corp, .home, and .mail

Warren Kumari <warren@kumari.net> Wed, 02 December 2015 21:48 UTC

Return-Path: <warren@kumari.net>
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 877081B2DC3 for <dnsop@ietfa.amsl.com>; Wed, 2 Dec 2015 13:48:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=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 hnQaU7LyU64G for <dnsop@ietfa.amsl.com>; Wed, 2 Dec 2015 13:48:50 -0800 (PST)
Received: from mail-yk0-x232.google.com (mail-yk0-x232.google.com [IPv6:2607:f8b0:4002:c07::232]) (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 BD7591B2DC1 for <dnsop@ietf.org>; Wed, 2 Dec 2015 13:48:50 -0800 (PST)
Received: by ykfs79 with SMTP id s79so64242523ykf.1 for <dnsop@ietf.org>; Wed, 02 Dec 2015 13:48:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-type; bh=1RuwsSlDuBHG1+kh7yZQ3VKJhC8a4eoH4NQI5ZzdvRo=; b=GmFzw45L9g/DNBtaYSzIMz8PXVLIHnY7vyC5bkZmo9Mr9/W3T2CxSOuwafgLfi1oSv t4Zbvvhnrt3Y09m6S5fqwO4OH0tFq26f//cMoQSDooeqj3CqsKTDpUL1os+srrISk0YF +fYgjnCqKM38TXANQqbK3WuQIqRWcaS3SvmmlcBhxmGN4kXMCTmfxWFpfGFkjjtrGvp2 BpGCuIv+xIzjBj0yeg3WqiowATO5o0Y06YEqu9bBxvBtYaMueKaFu+WLgZzbTWFIqknL 1wDsAErqklD/uH+M+MAjfusc0skheNS9l7AYTLKVosj2wkxO4ZlQNareNBuL0MI7Rz74 x7XA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-type; bh=1RuwsSlDuBHG1+kh7yZQ3VKJhC8a4eoH4NQI5ZzdvRo=; b=FmLoRWc/JQU0/h1H0zq5ymVtpPFtmI+YEW2OsXELuyzx3qA2hd15kf8/KjCO22ITpe 7xZOP3zbtln0QhTzbKPosgIHBDWBHwD7CIQ79+04z4p6oHl7yqwL4AA4ezNLM5/iwpHG /VpRL8ZAm//hObDracgZySZiCwsz4uPEiHOCn2NGc6wF1dc27PZXv/ykUyBpvdxz9ZvU vaarAo4aahS3GNAwjRDwHCmvNXzyh7WblQzDtfazqO7yCL754kuPPkXkoUFLb6e+9QG5 pkF+rBm3IrZoPs2R509GrCynNG0fShG2Ha2/nz6V9A3wqEy24sY8S4xQ2qD1Hw0Qjuis Xbrw==
X-Gm-Message-State: ALoCoQlB4QmuXtYtKTwZkdOzyvAgDmHQk1AJykwYy0bFTutg1p+MNHzm2ysWW+KKQdwLyj3ope95
X-Received: by 10.13.194.193 with SMTP id e184mr3921154ywd.203.1449092929994; Wed, 02 Dec 2015 13:48:49 -0800 (PST)
MIME-Version: 1.0
References: <20151202161603.22931.qmail@ary.lan>
In-Reply-To: <20151202161603.22931.qmail@ary.lan>
From: Warren Kumari <warren@kumari.net>
Date: Wed, 02 Dec 2015 21:48:40 +0000
Message-ID: <CAHw9_i+KCKzZRxHOBRtEro00zF=V5c=Ya6Ab2xuuirqG-vus8Q@mail.gmail.com>
To: John Levine <johnl@taugh.com>, dnsop@ietf.org
Content-Type: multipart/alternative; boundary="001a114edb3056f42e0525f13d60"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/QHmSc9k94ojWYPHuAatwWN031zs>
Subject: Re: [DNSOP] About reserving .corp, .home, and .mail
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: <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, 02 Dec 2015 21:48:52 -0000

Yup. This is very similar to what the earlier JAS report (
https://www.icann.org/en/system/files/files/name-collision-mitigation-26feb14-en.pdf)
said:
RECOMMENDATION 1: The TLDs .corp, .home, and .mail be permanently
reserved for internal use and receive RFC 1918-like protection/treatment,
potentially via RFC 6761.

The slidedeck presented at the NameCollisions workshop said:
"The TLDs .corp, .home and .mail should be permanently reserved"

Their new recommendation is almost exactly the same:
RECOMMENDATION 1: The TLDs .corp, .home, and .mail be referred to the
 Internet Engineering Task Force (IETF) for potential RFC 1918-like
 protection/treatment.

So, yay for consistency.

However, draft-chapin-additional-reserved-tlds (
http://tools.ietf.org/html/draft-chapin-additional-reserved-tlds-02) tried
to do exactly this.
>From the Abstract:
"This document reserves three domain name labels for special use in
accordance with the criteria and procedures of [RFC6761]: home, corp,
and mail."

On July 14th, 2015 DNSOP decided not to adopt this document -
https://www.ietf.org/mail-archive/web/dnsop/current/msg14887.html

This is all part of the larger discussions on the IETF handling of RFC6761
/ Special Use Names (a topic which will make me start frothing at the
mouth, and run my dinner), so I'm going to jsut leave it at that...

W

On Wed, Dec 2, 2015 at 11:16 AM John Levine <johnl@taugh.com> wrote:

> ICANN's published the final version of JAS' namespace collision report.
> The
> first version came out a year ago but parts of it were redacted because
> they
> stumbled across a horrible bug in some Microsoft software and wanted to
> give
> MS time to fix it.  The final version isn't very different other than
> fleshing
> out some interesting details.
>
> It says that for the most part namespace collsions aren't a big
> problem, but there are significant exceptions.  It has a list of
> recommendations, starting with this one:
>
>  RECOMMENDATION 1: The TLDs .corp, .home, and .mail be referred to the
>  Internet Engineering Task Force (IETF) for potential RFC 1918-like
>  protection/treatment.
>
> Here's the URL of the announcement with the link to the report.  The
> interesting bit of the report is section 5.7 on pages 38-39:
>
> https://www.icann.org/news/announcement-2-2015-11-30-en
>
> R's,
> John
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>