Re: [homenet] The HOMENET WG has placed draft-tldm-simple-homenet-naming in state "Call For Adoption By WG Issued"

Ted Lemon <mellon@fugue.com> Mon, 31 July 2017 09:53 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00C04131FFE for <homenet@ietfa.amsl.com>; Mon, 31 Jul 2017 02:53:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=fugue-com.20150623.gappssmtp.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 w04H-S2uOahR for <homenet@ietfa.amsl.com>; Mon, 31 Jul 2017 02:53:10 -0700 (PDT)
Received: from mail-qt0-x234.google.com (mail-qt0-x234.google.com [IPv6:2607:f8b0:400d:c0d::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 314A3131FFD for <homenet@ietf.org>; Mon, 31 Jul 2017 02:53:10 -0700 (PDT)
Received: by mail-qt0-x234.google.com with SMTP id a18so86728592qta.0 for <homenet@ietf.org>; Mon, 31 Jul 2017 02:53:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=5rpaMnvcGbhvUJtuI8oHG09vlsx8MlUfMgNJzDYkfes=; b=RpCKqqKjnlw2IcFRdVrEFny+eW6XqK8tGdGgHmNEmP+95oyfT1tP/3JsPZscpjzRqM 7TsQ35FkWRqYvEEwCnRxghqwgkEPf/Fetly4j/wr1kLejIIdRf2Iv7kM70E8weJC7nMv 1hoRb0KLUpW5QIecmbff3GtRNZX4tjDRtEdYZx3ADOhZwgx3OzWLXkCmcZLQuxOh29lv QCwZ2q9UJMuipAQGCRCuWhAGdY8eFqgrv8l1bqIbT6iuqzXosStQrPHyJg2wB3NegiUq c3h8PFPNJDaxrLbFDv9/VCYjy725AIN6YFQaYKqSO+YnhErUjzWXKsteh96GuLx/DiNB S/TA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=5rpaMnvcGbhvUJtuI8oHG09vlsx8MlUfMgNJzDYkfes=; b=NJZylYV5Cf4jCht0Hiswld33g2bOECRUhEHKsjJrf+dZTiwcRXwdc+06SKuZDzjc+k i1LhQAQS9NWASpbxTecRB2n7UeXhhRcVDOAlWhBD7oho8IlY9I7grGuFjba0CrHcvkUe snlm02X9pYAUh2wYGs5vHaPN7xuiCY46qkWoTOXROq5KzzybW+X22xB2HFINezcBdQS0 FojYkTHClA5ArgXsUZq+yaQh9nr7VeK9t1wZjjZ4TiSzLCnd7dQBanVdSC6k+fU/SJb+ eW3q3fXUAevDzoZc/tWiUtsldBWTevpIAlZBHzxPl3keoVCmEar8uokKyzsDy2lFPoKI 1iQA==
X-Gm-Message-State: AIVw110J3qIPODBu3/3RIVQIed01brYvH4J5gRNn//zvV4Ql0eEUsi7Q ctzEYxhkBiCDCVeQgAcaXg==
X-Received: by 10.200.8.20 with SMTP id u20mr20079555qth.4.1501494789235; Mon, 31 Jul 2017 02:53:09 -0700 (PDT)
Received: from [10.0.30.153] (c-73-167-64-188.hsd1.ma.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id z192sm19362176qka.46.2017.07.31.02.53.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 31 Jul 2017 02:53:08 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <AF836D5F-3322-4A81-9B7B-77CEADC6AF0C@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_FA097AAA-1F5F-48DD-8875-9C1BDBAA69AF"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Mon, 31 Jul 2017 05:53:07 -0400
In-Reply-To: <6265.1501464056@obiwan.sandelman.ca>
Cc: "homenet@ietf.org" <homenet@ietf.org>
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <150124709279.25258.15094387920433065465.idtracker@ietfa.amsl.com> <2D09D61DDFA73D4C884805CC7865E6114DBE0147@GAALPA1MSGUSRBF.ITServices.sbc.com> <12743.1501435181@obiwan.sandelman.ca> <F9E968C3-1EA7-4518-A582-4E5DE923A33E@jisc.ac.uk> <6265.1501464056@obiwan.sandelman.ca>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/seepg4VtuY8mxXACftHYk0tejVw>
Subject: Re: [homenet] The HOMENET WG has placed draft-tldm-simple-homenet-naming in state "Call For Adoption By WG Issued"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 09:53:12 -0000

On Jul 30, 2017, at 9:20 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
>> and then there is draft-ietf-mif-mpvd-ndp-support as a normative reference.
> 
> concerns me most.  Unless it's in RFC-editor queue (it's not, it's expired!),
> I'm pretty sure it's a very much normative reference.  So Homenet needs an
> answer as to how to deal with this dependancy.  It seems that we'd need to
> adopt it, copy and paste the text into this document, or reboot MIF...

There was widespread agreement in INTAREA to adopt this:

https://tools.ietf.org/html/draft-bruneau-intarea-provisioning-domains-02 <https://tools.ietf.org/html/draft-bruneau-intarea-provisioning-domains-02>

I actually intended to reference this—I just got my wires crossed because google gave me the link to the other one, which as you say is dead.

The current rev of the homenet naming architecture is pretty thin—I put a lot of work into the dnssd stuff, because I wanted to have it pretty solid before referencing it in the MPVD architecture document.   If you weren't in homenet, it might indeed be worth reviewing my presentation in the meetecho.   Stuart's presentation in dnssd might also be worth reviewing.

Anyway, a consequence of the emphasis on the dnssd work is that I had about an hour to update the naming architecture document before the submission deadline, and the update is minimal, to be as charitable as possible.

Daniel wanted to do another update, but we needed to sync up first, and I don't know where he is at with that now, but I think it would be reasonable to put the CFA on hold pending that update.   There have been some good comments already, though; in particular, I think Juliusz' point that it would be nice to actually try some of this in practice is good, and is what I'm working on now.   I think having that done before the document is adopted is a pretty high bar, but I don't really care either way.

That said, what I said in the working group is that we've been spinning our wheels on this for several years, and I wanted to know if the scope of this is reasonable and is what the working group wants to take on.   If it's not, then I don't actually know how to proceed.

(BTW, Juliusz, yes, HNCP is where the domain name is agreed upon.)