IETF Logo Mail Archive

Re: [core] I-D Action: draft-ietf-core-resource-directory-13.txt

Christian Amsüss <christian@amsuess.com> Thu, 01 March 2018 17:58 UTC

Return-Path: <christian@amsuess.com>
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 0546612EC00 for <core@ietfa.amsl.com>; Thu, 1 Mar 2018 09:58:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01, 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 ZCD14l6-4lvQ for <core@ietfa.amsl.com>; Thu, 1 Mar 2018 09:58:15 -0800 (PST)
Received: from prometheus.amsuess.com (prometheus.amsuess.com [5.9.147.112]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E75E712EC06 for <core@ietf.org>; Thu, 1 Mar 2018 09:58:14 -0800 (PST)
Received: from poseidon-mailhub.amsuess.com (095129206250.cust.akis.net [95.129.206.250]) by prometheus.amsuess.com (Postfix) with ESMTPS id 703CF494EA for <core@ietf.org>; Thu, 1 Mar 2018 18:58:12 +0100 (CET)
Received: from poseidon-mailbox.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bf]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id 7D7FB199 for <core@ietf.org>; Thu, 1 Mar 2018 18:58:11 +0100 (CET)
Received: from hephaistos.amsuess.com (hephaistos.amsuess.com [IPv6:2a02:b18:c13b:8010::db8]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id 474D85E for <core@ietf.org>; Thu, 1 Mar 2018 18:58:11 +0100 (CET)
Received: (nullmailer pid 26262 invoked by uid 1000); Thu, 01 Mar 2018 17:58:10 -0000
Date: Thu, 01 Mar 2018 18:58:10 +0100
From: Christian Amsüss <christian@amsuess.com>
To: core@ietf.org
Message-ID: <20180301175810.GB25963@hephaistos.amsuess.com>
References: <151992555197.21668.9651600215164766636@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="8GpibOaaTibBMecb"
Content-Disposition: inline
In-Reply-To: <151992555197.21668.9651600215164766636@ietfa.amsl.com>
User-Agent: Mutt/1.9.3 (2018-01-21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/k6fDj82piiMF0LfeHiDYK8ZUDAw>
Subject: Re: [core] I-D Action: draft-ietf-core-resource-directory-13.txt
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 01 Mar 2018 17:58:17 -0000

Hello Working Group,

On Thu, Mar 01, 2018 at 09:32:31AM -0800, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Constrained RESTful Environments WG of the IETF.
> 
> [...]
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-core-resource-directory-13
> https://datatracker.ietf.org/doc/html/draft-ietf-core-resource-directory-13

Given that the document is closing its completion, the authors would
like to ask the working group for reviews on it.

Big changes since -12 are:

* Added "all resource directory" nodes MC address
* Clarified observation behavior
* Reduced the significance of domains (removed from figure 2)
* Explained how endpoints from other RDs can be members of a group
* Resolve RFC6690-vs-8288 resolution ambiguities:
  *  require registered links not to be relative when using anchor
  *  return absolute URIs in resource lookup
* Explain that multiple RDs can be found, and can have absolute
  addresses
* Refer to t2trg-rel-impl for server metadata / versioning
* Add explanatory text

Best regards,
Christian

-- 
You don't become great by trying to be great. You become great by
wanting to do something, and then doing it so hard that you become great
in the process.
  -- Marie Curie (as quoted by Randall Munroe)

v2.23.0 | Report a Bug | By Email