Re: [core] Links, hosts, and resource directories

Klaus Hartke <hartke@projectcool.de> Sun, 04 November 2018 15:07 UTC

Return-Path: <hartke@projectcool.de>
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 DC7E6130E13 for <core@ietfa.amsl.com>; Sun, 4 Nov 2018 07:07:48 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_FAIL=0.001] autolearn=no 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 4DVKScMimPtE for <core@ietfa.amsl.com>; Sun, 4 Nov 2018 07:07:47 -0800 (PST)
Received: from wp382.webpack.hosteurope.de (wp382.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8597::]) (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 B3783130E17 for <core@ietf.org>; Sun, 4 Nov 2018 07:07:47 -0800 (PST)
Received: from mail-qk1-f182.google.com ([209.85.222.182]); authenticated by wp382.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1gJK0A-0002BV-7v; Sun, 04 Nov 2018 16:07:46 +0100
Received: by mail-qk1-f182.google.com with SMTP id y16so9521822qki.7 for <core@ietf.org>; Sun, 04 Nov 2018 07:07:46 -0800 (PST)
X-Gm-Message-State: AGRZ1gJbPn4Gyjj837Iq1AQ62Nm7F/zkBinHO5pFeyyp3I5sjaOz4BbR EX0fzBW3uXzFndp/cvf6vilpPdV+ohcFIDpeyk4=
X-Google-Smtp-Source: AJdET5fp5IdtEUwhjbJom60ECn8cepboPDq7us2dbvStP1mBjDBQg959IhZ5gKUy+Apy1wiG+3sG9eqOj04oOpc4iec=
X-Received: by 2002:a37:a84b:: with SMTP id r72mr18054519qke.2.1541344065279; Sun, 04 Nov 2018 07:07:45 -0800 (PST)
MIME-Version: 1.0
References: <CAAzbHvZP-XfjFSn0p++9ECY8LAFaVaBrYhmnyNKW1SQOnR6cOw@mail.gmail.com> <20181031065938.GA6605@hephaistos.amsuess.com> <360fce5cf526718475f9d1fffa66ca4c@bbhmail.nl>
In-Reply-To: <360fce5cf526718475f9d1fffa66ca4c@bbhmail.nl>
From: Klaus Hartke <hartke@projectcool.de>
Date: Sun, 4 Nov 2018 16:07:13 +0100
X-Gmail-Original-Message-ID: <CAAzbHvYJys12YT8CAxAem8XXN1si4++95AKLCaPNkc+_2AXa8g@mail.gmail.com>
Message-ID: <CAAzbHvYJys12YT8CAxAem8XXN1si4++95AKLCaPNkc+_2AXa8g@mail.gmail.com>
To: peter van der Stok <consultancy@vanderstok.org>
Cc: =?UTF-8?Q?Christian_M=2E_Ams=C3=BCss?= <christian@amsuess.com>, "core@ietf.org WG" <core@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-bounce-key: webpack.hosteurope.de; hartke@projectcool.de; 1541344067; 60f96f39;
X-HE-SMSGID: 1gJK0A-0002BV-7v
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/CmRHadSXjjjUENBf2o25MOF7-8g>
Subject: Re: [core] Links, hosts, and resource directories
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: Sun, 04 Nov 2018 15:07:49 -0000

Peter van der Stok schrieb:
> Christian Amsüss schreef:
>> Klaus Hartke wrote:
>>>   [A Resource Directory (RD)] hosts registrations of
>>>   resources held on other servers, allowing lookups
>>>   to be performed for those resources.
>>>
>>> Is this a lie?
>>
>> Without more context, yes it is, and we should ensure that the wording
>> does not lead to the conclusion that resources (and not links) would be
>> stored.
>
> Sorry to react to this, but
> I cannot imagine how "registrations of resources" can be equated with "resources".
>
> But if it creates confusion it needs to be adapted.

Don't get too hung up on this particular sentence. The issue is more
the overall impression I got after skimming the current draft version
combined with the interop spec, which felt inconsistent. Maybe the
introduction is fine and just some legacy examples need fixing. I'll
make suggestions when I can pinpoint exactly what trips me up. Let me
ask a few more dumb questions first to make sure I get things right.

Klaus