Re: [DNSOP] WGLC for draft-ietf-dnsop-sutld-ps

Ralph Droms <rdroms.ietf@gmail.com> Thu, 16 March 2017 19:59 UTC

Return-Path: <rdroms.ietf@gmail.com>
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 C0830129A4D for <dnsop@ietfa.amsl.com>; Thu, 16 Mar 2017 12:59:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XdAo59Ldx1-1 for <dnsop@ietfa.amsl.com>; Thu, 16 Mar 2017 12:59:26 -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 8BAE1129A47 for <dnsop@ietf.org>; Thu, 16 Mar 2017 12:59:26 -0700 (PDT)
Received: by mail-qk0-x234.google.com with SMTP id 1so48945669qkl.3 for <dnsop@ietf.org>; Thu, 16 Mar 2017 12:59:26 -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=0j9u4w1aK6fBUZVoUAPp0trlTiEF2BPfZR7MH+7By3I=; b=n4x11NeGs34HDqOySortZmHxyp1Xhyrp9X0ECqP+jrJKbeag8BOxgzRDNtPOy1Rltz FrgNzE9M12T4lxlqc7yPmuDsO9KjTp/w/hjr5CjHjKcSqq7aPitR8vGQW650myWCqDpu L0ObMco+SoUgQKS5MGbbTcU66rAHA+Z5g7cKP3J6+VfYFjtupJSBsIoPAJqwIsy1K8i8 MAgDrTPsOC00duA2+laT5FNtDb2rng40+WtyhaYH00BgI24f+wQyvCoMs5lkgHh1MvWN SQDSbEA6qkRd4C55Vn4PltvC4YTGai29xXNnwOe4r/A9OxFtl5LaoraXOaf7yY9gSkQE NAlg==
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=0j9u4w1aK6fBUZVoUAPp0trlTiEF2BPfZR7MH+7By3I=; b=l/Zihzo6gzf4Kkm+YNS5a2SMT+DD0j227nW7n1SFnfZTt1Ni9E5xNp18vCs5cbj3WU Z22kZBS/Dz3TMFUF37Ps1TF2YH8kCAp7Drcoz/gjzWNLS3/QtjDwqIFzxrNBsPcTYMZA OgUxcj2z4ztQ/8LpjoWz4CUq3SublsFcSFSjaRL9EX4Wmj+e1KiM/5SMbx6KC/t1MBMI UBOzKMy5lGw9KOmr+hbu4ALzFtDeP56VV056/AjKQ+2SRbfLIlhItFN/7C6WDVW+0guU BOmZFyl/NH2nAertl9/kEhWmo19FRbg6slIMQoGAHm8IDjKvQdqRHrS7gznlrb4gAf0k i60g==
X-Gm-Message-State: AFeK/H181NH/DFl/l3U61yzQbm6C3M00WKD9CTP0eXqTcDJxS65hq9kb8k7OWkxnDICd1Q==
X-Received: by 10.55.56.131 with SMTP id f125mr10471642qka.203.1489694365614; Thu, 16 Mar 2017 12:59:25 -0700 (PDT)
Received: from ?IPv6:2601:18f:801:600:49a0:15f0:48f1:9e46? ([2601:18f:801:600:49a0:15f0:48f1:9e46]) by smtp.gmail.com with ESMTPSA id v4sm4341993qtg.0.2017.03.16.12.59.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Mar 2017 12:59:25 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <44B7CA03-47B4-4F78-AA1C-9EA558818144@icann.org>
Date: Thu, 16 Mar 2017 15:59:22 -0400
Cc: dnsop <dnsop@ietf.org>, Russ Housley <housley@vigilsec.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <8CBB9AC5-9B3B-4F35-B3F3-AC239A199AE8@gmail.com>
References: <44B7CA03-47B4-4F78-AA1C-9EA558818144@icann.org>
To: Edward Lewis <edward.lewis@icann.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/OG83sHf5GyjEFpI3B8FP8BCOjDA>
Subject: Re: [DNSOP] WGLC for draft-ietf-dnsop-sutld-ps
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, 16 Mar 2017 19:59:29 -0000

> On Mar 16, 2017, at 12:08 PM, Edward Lewis <edward.lewis@icann.org> wrote:
> 
> On 3/15/17, 20:22, "DNSOP on behalf of Russ Housley" <dnsop-bounces@ietf.org on behalf of housley@vigilsec.com> wrote:
> 
>> I see that draft-ietf-dnsop-sutld-ps-03 still references I-D.lewis-domain-names, but I have not seen ant WG Last Call for that document.  What is the plan?
> 
> Just accidently saw this...I haven't been reading DNSOP much recently.
> 
> FWIW, the document ("-domain-names-") was informally attached to the IAB's Names and Identifier's Program, that program was recently scuttled by the IAB like, maybe, 2-3 weeks ago.  I had been wondering (but more tied up with this week's ICANN meeting) what happens next, and haven't gotten around to dealing with that.  In that sense "Good Question."
> 
> The domain-names draft was never considered for a DNSOP WG document as it is mostly about how this is not a DNS problem.  In 2015, I did get comments from folks on this list and then for most of 2016 the discussion was under the IAB program.  There wasn't much discussion which is the prime reason the document was in a suspended, waiting state.
> 
> The document currently has two pieces.  One is the historical narrative and written to justify clarifying domain names, with "clarifying" being an action not to be undertake without much consideration.  (Having written two clarifications, I've learned.)  The other piece is where I wanted discussion, defining domain names.
> 
> I could edit the document to include just the first piece and submit it to the Independent Stream whatever, Editor.  There's not much reason not to do that - it just hadn't happened while the IAB program was in place (potentially adopting the document).  On the other hand, I was still "discovering" some of the elements of the relevant history as late as December based on the only set of comments I'd received in months (got it in private email in September).
> 
> What are the chances that the Independent Stream Editor will bounce this document towards DNSOP?  So - as a question to the chairs - is it worth DNSOP adopting this document (covering the history) at the risk of it being out of scope for the charter, or is it better to, if the Independent Stream Editor bounces this to DNSOP, reply with a "it's not our bailiwick?"
> 
> I suppose in any case there will be an IETF-wide last call before the document stands a chance of being a vetted, published document.  I've just never thought of any other vetting (WG) to be done.
> 
> Ed

Ed - I think your document is a valuable reference and worth publishing.  The first question to ask is whether you want to continue with the publication process.  If you do, I'm sure we can find some way to publish it.

I need to re-read the document to refresh myself on the two aspects of the document that you mention.  If you really are looking for IETF discussion and consensus on the defining domain names, a third path would be an AD-sponsored submission, independent of any WG.

- Ralph

> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop