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

Terry Manderson <terry.manderson@icann.org> Wed, 29 March 2017 15:41 UTC

Return-Path: <terry.manderson@icann.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 A70EE126557; Wed, 29 Mar 2017 08:41:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 PTu2Jrn0nSkK; Wed, 29 Mar 2017 08:41:41 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-1.pexch112.icann.org [64.78.40.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DCBE1297C3; Wed, 29 Mar 2017 08:41:39 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Wed, 29 Mar 2017 08:41:37 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1178.000; Wed, 29 Mar 2017 08:41:37 -0700
From: Terry Manderson <terry.manderson@icann.org>
To: Michael Richardson <mcr+ietf@sandelman.ca>
CC: HOMENET <homenet@ietf.org>, "dnsop@ietf.org" <dnsop@ietf.org>
Thread-Topic: [DNSOP] [homenet] My assessment of .homenet as described during the WG session yesterday.
Thread-Index: AQHSp+lHBXnknGGzd0m0I5wpP+R/Q6GsYgKAgACxDQA=
Date: Wed, 29 Mar 2017 15:41:36 +0000
Message-ID: <ECBE5CBD-06B4-45C5-9C15-EE899F7403FF@icann.org>
References: <DAC83E33-A206-4EAA-BC96-E26ACCC013A6@icann.org> <29150.1490800075@obiwan.sandelman.ca>
In-Reply-To: <29150.1490800075@obiwan.sandelman.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.20.0.170309
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3573682896_1803442087"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Yga7sp7ncvX7tOfsq7EiR_8bNQA>
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:41:44 -0000

Hi Michael,

There is no policy or technical barrier to proceeding with SOMETHING.arpa. Procedurally that, of course, would necessitate some WG discussion and consensus.

Cheers
Terry

On 30/03/2017, 1:07 AM, "DNSOP on behalf of Michael Richardson" <dnsop-bounces@ietf.org on behalf of mcr+ietf@sandelman.ca> wrote:

    
    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>ca>, Sandelman Software Works
     -= IPv6 IoT consulting =-