[DNSOP] draft-ietf-homenet-dot review limits Re: .arpa

Suzanne Woolf <suzworldwide@gmail.com> Thu, 23 March 2017 14:37 UTC

Return-Path: <suzworldwide@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 3FB13129484 for <dnsop@ietfa.amsl.com>; Thu, 23 Mar 2017 07:37:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id dGu6Z0OmJpvX for <dnsop@ietfa.amsl.com>; Thu, 23 Mar 2017 07:36:58 -0700 (PDT)
Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::234]) (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 0D201126CE8 for <dnsop@ietf.org>; Thu, 23 Mar 2017 07:36:58 -0700 (PDT)
Received: by mail-qk0-x234.google.com with SMTP id p22so41938778qka.3 for <dnsop@ietf.org>; Thu, 23 Mar 2017 07:36:58 -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 :content-transfer-encoding:message-id:references:to; bh=Lp1ZlQ/6NngV20AmiExY2+GUhQnw8rlihbTlODQOK50=; b=JB6mxGsKYkoH+jqEM/6B0ObfSfN+kHj78iN5xMJdsA8z/hBQLlZer6cFOOGkKI4YGn QrFKtwvAci1qlKdzW/xwOExBVt+F8J4Wp0iDV2pABT+e/OQ+l6te7opiUDEDvVJvWfbP qS0guQamGGXbvGzPSOcTKtVLv93hVKEGrnFM5JHaqk9BliP5Z6SJe9rELfFN/Zddqz+L 6OAN4np3/cq1HXXwpjaX0UhEwkQbxtiFHbD2ztb7ARp+xaaq+qxY0FIkGuH0ncPuwWBm mURLPmw38Ay3mtKibKQo956cnkfYGsNSz4G1qCEZL/s7V9LBtjRLMu+O/i7GbWfwsa1M Q2tQ==
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 :content-transfer-encoding:message-id:references:to; bh=Lp1ZlQ/6NngV20AmiExY2+GUhQnw8rlihbTlODQOK50=; b=CYHaqgV+qnZ4rPfcEucU6LSsqVlJVhv5/rp1vL3ThzTRGRBcOVKprrKQZQ9dxnrJbg dw1vjxbMaEHXIZzJUPmp/MKysF/tqqz8m5lQsiUkJwkmAqUJeWTiQ1MPPfVGkHYyzqd2 CtsS0WK24jMpcKCeWGfHYE5ohdkHUC7TETsh4+M3SpWrNJASK1MGNFZHae+YG6lTYrpH /7kdJIfBkYedKNSpuItad5Z4pP2H2EQflsE+XEu2YXLNle5kdHLt2S80epwgSBOkpofo MFDU+bnhtA0RRXJXVEnG2+VSFYuNwDofN2+bHacJxhZK92AR5vrFDPMRTGHmw6+NfwSC rZ0g==
X-Gm-Message-State: AFeK/H2B0eCwxeUf/Vw0T/8g0Z4hCV8QpWkcCrfgCDjmNN4Aphdn65mNAZ+K4MDWVbmZLA==
X-Received: by with SMTP id a6mr2422492qkg.53.1490279817222; Thu, 23 Mar 2017 07:36:57 -0700 (PDT)
Received: from ?IPv6:2601:181:c381:c20:34f0:26ef:ac7c:2eed? ([2601:181:c381:c20:34f0:26ef:ac7c:2eed]) by smtp.gmail.com with ESMTPSA id t47sm3343626qte.45.2017. (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 23 Mar 2017 07:36:56 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <alpine.OSX.2.20.1703230956550.53811@ary.qy>
Date: Thu, 23 Mar 2017 10:36:54 -0400
Cc: IETF dnsop Working Group <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B0E51517-8C43-472E-A584-3369CE664CB6@gmail.com>
References: <20170323042741.79108.qmail@ary.lan> <2C6B4EB6-D0F0-44A8-95E4-68DF32244639@fugue.com> <alpine.OSX.2.20.1703230956550.53811@ary.qy>
To: John R Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Ix4z4VEYfqqP9ZvELskE3qG8TXM>
Subject: [DNSOP] draft-ietf-homenet-dot review limits Re: .arpa
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: Thu, 23 Mar 2017 14:37:00 -0000

Hi all, and not picking on John….

I think this subthread on process and policy has gone as far as we reasonably can in a DNSOP review of draft-ietf-homenet-dot. We’ve established that different constraints and expectations apply to policy for different portions of the namespace, and that the HOMENET WG believes those differences have been taken into account, and that not everyone in DNSOP agrees.

Please share any new thoughts on how the specified protocol in the draft interoperates with the global public DNS, particularly with regards to DNSSEC or possibly incompatible uses of the namespace, which seem to be within our chartered scope.

I believe the process and policy concerns we’ve raised here can be revisited in an additional request for review or an IETF Last Call, if needed.


> On Mar 23, 2017, at 10:00 AM, John R Levine <johnl@taugh.com> wrote:
>> The working group is aware of the "wait many years" part of this approach, and is willing to try and see.  If the working group sees no progress over the course of the next few years, we may shift to the latter approach.
> Just out of curiosity, is there anyone in the homenet WG who regularly engages with ICANN, through AC's or SO's or the like?
> R's,
> John
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop