IETF Logo Mail Archive

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

Klaus Hartke <hartke@projectcool.de> Mon, 04 November 2019 17:25 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 DF15012012A for <core@ietfa.amsl.com>; Mon, 4 Nov 2019 09:25:14 -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_HELO_NONE=0.001, SPF_PASS=-0.001, 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 lqUWlH_zAXd6 for <core@ietfa.amsl.com>; Mon, 4 Nov 2019 09:25:10 -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 691611200FE for <core@ietf.org>; Mon, 4 Nov 2019 09:25:10 -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 1iRg6E-0002m2-Dg; Mon, 04 Nov 2019 18:25:06 +0100
Received: by mail-qk1-f182.google.com with SMTP id d13so18395820qko.3 for <core@ietf.org>; Mon, 04 Nov 2019 09:25:06 -0800 (PST)
X-Gm-Message-State: APjAAAXh4rQ/rNBHGy4mtXDjvPKrN62hAM+BZ2f2unkAoFJ4nHirLTNy 8pUD+tx5e4SYFaXBYUNswto+63y3DS+ei52Y+Hs=
X-Google-Smtp-Source: APXvYqzbwqtZ2SgHo49R18jIAeUbpWEmlajzXxDZBwfO5w6sCrcVO69GP7rTejMjOQ0khPiBiCa3sjMqRjSpEK7djyE=
X-Received: by 2002:a05:620a:11a7:: with SMTP id c7mr2491797qkk.448.1572888305091; Mon, 04 Nov 2019 09:25:05 -0800 (PST)
MIME-Version: 1.0
References: <481f9820-bcea-af6a-d5c4-d713be24d43d@isode.com>
In-Reply-To: <481f9820-bcea-af6a-d5c4-d713be24d43d@isode.com>
From: Klaus Hartke <hartke@projectcool.de>
Date: Mon, 04 Nov 2019 18:24:29 +0100
X-Gmail-Original-Message-ID: <CAAzbHvZcNJ=hFAvHebcj8QOuf=DzRNQ3hhtXqBj9miTAhEOUJw@mail.gmail.com>
Message-ID: <CAAzbHvZcNJ=hFAvHebcj8QOuf=DzRNQ3hhtXqBj9miTAhEOUJw@mail.gmail.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: "core@ietf.org" <core@ietf.org>
Content-Type: text/plain; charset="UTF-8"
X-bounce-key: webpack.hosteurope.de; hartke@projectcool.de; 1572888310; 6be18a96;
X-HE-SMSGID: 1iRg6E-0002m2-Dg
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/tmbFZANErOcdmcKZQAAHP-DBbuU>
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: Mon, 04 Nov 2019 17:25:15 -0000

Alexey Melnikov wrote:
> In 4.3, 6th para:
>
>     Clients of the RD
>     SHOULD therefore accept URIs of all schemes they support, both as
>     URIs and relative references,
>
> Did you mean to say "absolute URIs"? Relative URIs are still URIs

After studying RFC 3986 for over a decade, my moment has come! I can
point out that someone is wrong on the Internet [1] ;-)

A relative URI reference is not a URI. Both URIs and relative
references are URI references [2]. And an absolute URI is a URI
without a fragment identifier [3].

Klaus

[1] https://xkcd.com/386/
[2] https://tools.ietf.org/html/rfc3986#section-4.1
[3] https://tools.ietf.org/html/rfc3986#section-4.3

v2.23.0 | Report a Bug | By Email