IETF Logo Mail Archive

Re: [core] Benjamin Kaduk's No Objection on draft-ietf-core-resource-directory-26: (with COMMENT)

Benjamin Kaduk <kaduk@mit.edu> Sat, 27 February 2021 21:38 UTC

Return-Path: <kaduk@mit.edu>
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 5FE843A14C6; Sat, 27 Feb 2021 13:38:13 -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_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 gPw2EHh9HCHk; Sat, 27 Feb 2021 13:38:12 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1A163A14C5; Sat, 27 Feb 2021 13:38:11 -0800 (PST)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 11RLbxgA005383 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 27 Feb 2021 16:38:04 -0500
Date: Sat, 27 Feb 2021 13:37:59 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: Carsten Bormann <cabo@tzi.org>
Cc: Christian Amsüss <christian@amsuess.com>, Jaime Jiménez <jaime.jimenez@ericsson.com>, core-chairs@ietf.org, draft-ietf-core-resource-directory@ietf.org, The IESG <iesg@ietf.org>, core@ietf.org
Message-ID: <20210227213759.GN21@kduck.mit.edu>
References: <161301561820.4693.9535939287401361803@ietfa.amsl.com> <YDkUiTAo0YlEOMfw@hephaistos.amsuess.com> <20210227205638.GJ21@kduck.mit.edu> <16D35A91-1919-44A7-97AB-16BF80CD85B9@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <16D35A91-1919-44A7-97AB-16BF80CD85B9@tzi.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/3Gayhsv22doJxks2b72YA3r0s0A>
Subject: Re: [core] Benjamin Kaduk's No Objection on draft-ietf-core-resource-directory-26: (with COMMENT)
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: Sat, 27 Feb 2021 21:38:14 -0000

On Sat, Feb 27, 2021 at 10:01:35PM +0100, Carsten Bormann wrote:
> On 2021-02-27, at 21:56, Benjamin Kaduk <kaduk@mit.edu> wrote:
> > 
> > use "authoritative" instead of
> > "authorized" in the couple places I indicated
> 
> Authoritative sounds like it is an intrinsic property of the source.
> Authorized means that the specific policies that apply to the consumer authorize use of the source for the purpose at hand.
> So I think this substitution should not occur lightly.

When the data in question is "what resources are available at this host", I
think authoritative is pretty intrinsically a property of the host itself :)

Now, if the question was "what resources are supposed to be at this host
that I'm allowed to use?", your considerations become quite relevant.

-Ben

v2.23.0 | Report a Bug | By Email