IETF Logo Mail Archive

Re: [core] AD review of draft-ietf-core-resource-directory-23

Jaime Jiménez <jaime@iki.fi> Wed, 20 November 2019 01:37 UTC

Return-Path: <jaime@iki.fi>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01AFE12092A for <core@ietfa.amsl.com>; Tue, 19 Nov 2019 17:37:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.82
X-Spam-Level:
X-Spam-Status: No, score=-1.82 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.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 e8cMneroPK8k for <core@ietfa.amsl.com>; Tue, 19 Nov 2019 17:37:16 -0800 (PST)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2447C120925 for <core@ietf.org>; Tue, 19 Nov 2019 17:37:16 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 5D3A53CA; Tue, 19 Nov 2019 20:37:15 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Tue, 19 Nov 2019 20:37:15 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=9a2+H86HPOaNeXrmxjhcJxL8DsGAs1wzElHzS6nuO Ug=; b=XWxsN7vaQa2xA9C4/4TKKcrH2KplaQEa11pNMqR9UNO+sKel8gcpGOLRq P2G8jCM3f5tRqlAKLlMI1ogk2H+xxgKZ7QufL7/I/w0MjIEM6LDEKjHl01Ari3ZY pEs/41nBukz9ZcpzHAxeigV7rECsvugI42ARnV/XBYanhysDGwgoNojGVZAFxhPG vrL2vbMztWRNkykkKNnEpE83fxBWhDT28iUT5fdThsBkkZ+VxYVdIDfm4F477BJm CgVa8qvcqvv+xjNmHH50Xk4fTOeWC4wmQGuD3KbU/RWusNxJTpOkqBdnU+5GEaD+ Q8+GLyOR2iSr7vV+z4se2ZpfVM8jA==
X-ME-Sender: <xms:ypjUXaa1dyiDvtfya7XpenfUeO_rsXJRKuXbHMAw_XzxJB6GCIqROw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudegledgfeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtugfgjgesthekredttddtudenucfhrhhomheplfgrihhm vgculfhimhornhgviicuoehjrghimhgvsehikhhirdhfiheqnecuffhomhgrihhnpehivg htfhdrohhrghenucfkphepfedurddufeefrddufeegrdduhedtnecurfgrrhgrmhepmhgr ihhlfhhrohhmpehjrghimhgvsehikhhirdhfihenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:ypjUXZto3vKDEVCx4eTUtfzHKS2Y2ve0DqlzZDTar8AkdK-ly2FA3A> <xmx:ypjUXXvVkCIE6VnOcaL-2p-SiZ0kHdRpbBA2Ak8lLn6Qhge0WtgyPg> <xmx:ypjUXecGbydR65G3zkC5DtxS-wjKubv-pZksu7sDIue0nPPUnxp8SA> <xmx:y5jUXRPFomV4uA2igpWU9w31cEwTeqKBpPP-NGvRiHQJIGq_hHNJsg>
Received: from EMB-918HFH01 (dhcp-8696.meeting.ietf.org [31.133.134.150]) by mail.messagingengine.com (Postfix) with ESMTPA id D844A80059; Tue, 19 Nov 2019 20:37:12 -0500 (EST)
Date: Wed, 20 Nov 2019 09:37:10 +0800
From: Jaime Jiménez <jaime@iki.fi>
To: Christian Amsüss <christian@amsuess.com>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, "core@ietf.org" <core@ietf.org>
Message-ID: <20191120013710.tnrm54ygjurehjna@EMB-918HFH01>
References: <481f9820-bcea-af6a-d5c4-d713be24d43d@isode.com> <20191119125733.GA8007@hephaistos.amsuess.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20191119125733.GA8007@hephaistos.amsuess.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/tRkDs7fU_mr08k8KjaYXZ9nr7eA>
Subject: Re: [core] AD review of draft-ietf-core-resource-directory-23
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Nov 2019 01:37:18 -0000

Hi,

of those comments that are to be discussed by the group, or that have to do 
with the shepherding, here are my quick thoughts before the core session. 

> > At the end of section 9.3:
> >    It is expected that the registry will receive between 5 and 50
> > registrations in total over the next years.
> > 
> > This will not age well! Maybe remove this text from the document and add it
> > to the spherding write-up?
> 
> Doesn't this need to be in the requesting document, per BCP26's "It is
> also a good idea to include, when possible, a sense of whether many
> registrations are expected over time, or if the registry is expected to
> be updated infrequently or in exceptional circumstances only."?
> 
> But if not, I'll remove the paragraph and alert Jaime as the shepherd.

Sounds good to me.


> 
> > I think the following reference is Normative the way it is used in the
> > document:
> > 
> >    [I-D.ietf-core-rd-dns-sd] Stok, P., Koster, M., and C. Amsuess, "CoRE
> > Resource Directory: DNS-SD mapping", draft-ietf-core-rd-dns-sd-05 (work in
> > progress), July 2019.
> 
> <personal>Oh please not</personal>.
> 
> I suppose this is due to "The use of DNS facilities is described in
> [rd-dns-sd]" being listed as a recommended way, or are there more
> aspects to it?
> 
> The DNS-SD component has been holding RD back quite a bit, so if it's that
> recommendation, I assume the group might want to reconsider recommending
> that mechanism for discovering the RD.
> 

RD-DNS-SD would benefit a lot from a review by Kerry Lynn. At this point
of time I am not sure about who has deployed this component as I am not
familiar with all SDOs. If we place a normative reference we
might delay RD much further. So I agree with Christian on bringing this
to the group, explaining the implications. 


> 
> Kind regards
> Christian
> 
> -- 
> Yesterday is history, tomorrow is a mystery, and today is a gift. That
> is why it is called the present.
>   -- ancient saying



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

v2.23.0 | Report a Bug | By Email