IETF Logo Mail Archive

Re: [DNSOP] [homenet] My assessment of .homenet as described during the WG session yesterday.

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 29 March 2017 15:07 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 8056D127599; Wed, 29 Mar 2017 08:07:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 wIlGeVozT-OI; Wed, 29 Mar 2017 08:07:55 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE8051293FB; Wed, 29 Mar 2017 08:07:55 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id DFF75200A3; Wed, 29 Mar 2017 11:31:49 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 0D772636E0; Wed, 29 Mar 2017 11:07:55 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Terry Manderson <terry.manderson@icann.org>
cc: HOMENET <homenet@ietf.org>, "dnsop@ietf.org" <dnsop@ietf.org>
In-Reply-To: <DAC83E33-A206-4EAA-BC96-E26ACCC013A6@icann.org>
References: <DAC83E33-A206-4EAA-BC96-E26ACCC013A6@icann.org>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Wed, 29 Mar 2017 11:07:55 -0400
Message-ID: <29150.1490800075@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/aSWODzZVfX1ecJge-gXcaTssewg>
Subject: Re: [DNSOP] [homenet] My assessment of .homenet as described during the WG session yesterday.
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: Wed, 29 Mar 2017 15:07:57 -0000

Terry Manderson <terry.manderson@icann.org> wrote:
    > B) seek a .homenet special use domain WITHOUT the delegation request
    > AND ask the IETF/IESG/IAB to commence the discussion with the ICANN
    > community to achieve an insecure delegation

    > c) seek a <SOMETHING>.arpa insecure special use delegation

    > d) go for "B" and if that doesn't work shift to "C"

Is there some reason we can not proceed with "C", concurrently with (B).
This might cause stub resolvers to have to have two cases
(SOMETHING.arpa, and .homenet) eventually, but at least we could deploy
and attempt interop with SOMETHING.arpa NOW, and it would more clearly
permit "home." to be removed from code.

    > Again, this situation is fluid and as discussions evolve I will provide
    > more information when it is appropriate. In the mean-time I would very
    > much like everyone to take a calming breath and understand that I am
    > taking a very pragmatic view of this concern.

Thank you!

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email