Re: [core] Questions and comments against the github version

Jim Schaad <ietf@augustcellars.com> Tue, 11 December 2018 17:41 UTC

Return-Path: <ietf@augustcellars.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 14AD6130EC1; Tue, 11 Dec 2018 09:41:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 4Z10GbHZ_1WB; Tue, 11 Dec 2018 09:41:32 -0800 (PST)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1B1E130EB8; Tue, 11 Dec 2018 09:41:31 -0800 (PST)
Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 11 Dec 2018 09:36:04 -0800
From: Jim Schaad <ietf@augustcellars.com>
To: consultancy@vanderstok.org
CC: draft-ietf-core-resource-directory@ietf.org, core@ietf.org
References: <02dd01d490f8$6aea0dc0$40be2940$@augustcellars.com> <d00ab991b089fb28625cb455ab7c5bec@bbhmail.nl>
In-Reply-To: <d00ab991b089fb28625cb455ab7c5bec@bbhmail.nl>
Date: Tue, 11 Dec 2018 09:41:01 -0800
Message-ID: <035e01d49178$b08a3e60$119ebb20$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_035F_01D49135.A2688500"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQMTxjR7df64heLt4gs0blLr1Spp0AE6nRS3ovGPqpA=
Content-Language: en-us
X-Originating-IP: [73.180.8.170]
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/_T3D2BqjrSBBxaW-wBJjw0ozalQ>
Subject: Re: [core] Questions and comments against the github version
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: Tue, 11 Dec 2018 17:41:34 -0000

 

 

From: Peter van der Stok <stokcons@bbhmail.nl> 
Sent: Tuesday, December 11, 2018 12:59 AM
To: Jim Schaad <ietf@augustcellars.com>
Cc: draft-ietf-core-resource-directory@ietf.org; core@ietf.org
Subject: Re: Questions and comments against the github version

 

Hi Jim,

thanks, for the questions.
One explanation for one question.

Jim Schaad schreef op 2018-12-11 03:22:

*  In section 5.3, I don't understand why the rule exists that if the
attribute values are different then the location of the registration needs
to be changed.   It seems that this could lead to some interesting conflicts
in behavior depending on what messages are used.  For example  (content
omitted for clarity):

POST /rd?ep=e1&foo=over

Res: 2.01 Created
Location-Path: /rd/4001

POST /rd?ep=e1&foo=under

Res: 2.01 Created
Location-Path: /rd/4002

As opposed to:

POST /rd?ep=e1&foo=over

Res: 2.01 Created
Location-Path: /rd/4001

POST /rd/4001?foo=under

Res: 2.01 Changed

<pvds>
The feeling was that a first ep having done the earlier registration /rd/4001 
should not be able to manipulate the 2nd registration by a 2nd ep, by removing /rd/4001
and having a registration /rd/4002 only known to 2nd ep.
</pvds>

[JLS] The only problem with this is that the query of endpoints needs to be changed so that the endpoint locations are not returned.  Once the query is done then the location is known to a 2nd ep.