Re: [core-parameters] NEW RESOURCE TYPES - oic.r.* and oic.d.*

Jaime Jiménez <jaime@iki.fi> Tue, 06 October 2020 14:42 UTC

Return-Path: <jaime@iki.fi>
X-Original-To: core-parameters@ietfa.amsl.com
Delivered-To: core-parameters@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 747393A0A6F for <core-parameters@ietfa.amsl.com>; Tue, 6 Oct 2020 07:42:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.12
X-Spam-Level:
X-Spam-Status: No, score=-1.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
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 RsJyNKJEnVml for <core-parameters@ietfa.amsl.com>; Tue, 6 Oct 2020 07:42:12 -0700 (PDT)
Received: from wforward4-smtp.messagingengine.com (wforward4-smtp.messagingengine.com [64.147.123.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 320523A0A68 for <core-parameters@ietf.org>; Tue, 6 Oct 2020 07:42:10 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailforward.west.internal (Postfix) with ESMTP id A8977EC7; Tue, 6 Oct 2020 10:42:09 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Tue, 06 Oct 2020 10:42:09 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=edqz6hwkm0jLeXebAr6QPsNEdfQMKAaSGsI17ATzI NM=; b=gvzwSHX7F1uvXthQPPW4yjdDycaIe5k7lE+E6LA8GF0KXyL9/nKyKSr4Q jWA1WPH0CHlbsmAI91IIBt0V9g1XvUVn79uYg0Unf+ygjEk6udnmbcLmjqSzZQli 1/+7Iu7MfXLruvlYdXx+4sj6beXT7bh2aXJG9pD1QtZTEdQKJQCYn9NSco+yxUWT 2vzC58MuNZ6xg3hH9AiugxvFlHLxjHs0uZ3yqbOspQ/yGCgPkUS5yJYCA7WBNrdM oLFLSrnf/+RS0AHz6UcONTrZrkDRKDsjVxZLgn+sSPuKoPVjFGQmNUElK9iSZs5z emxHyI7nScpT4JzUg5ay9jrjxlz1g==
X-ME-Sender: <xms:QIJ8X5-22AbNiKz2I_xU4X0sEHmTMGdw7h9yEs1aP74Rrkmjkr70pQ> <xme:QIJ8X9u34iJagPBalyNUThMsni4HAmUCoxqGTJKpHgj0zX0WEbgNJQLTxXDiykDbL p_DzCpbk65fy_bx2A>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrgeeggdejlecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkfhggtggugfgjsehtkeertddttdejnecuhfhrohhmpeflrghimhgv ucflihhmrohnvgiiuceojhgrihhmvgesihhkihdrfhhiqeenucggtffrrghtthgvrhhnpe dtveetgfejvedvjedtheekkeetleegfefgiefffeeuueeljeekudefgeevvdekjeenucff ohhmrghinhepihgrnhgrrdhorhhgpdhophgvnhgtohhnnhgvtghtihhvihhthidrohhrgh dpshgvthhtihhnghhsrdhsuhhpphhorhhtpdhivghtfhdrohhrghenucfkphepkeejrdel fedrvdehrdefheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehjrghimhgvsehikhhirdhfih
X-ME-Proxy: <xmx:QIJ8X3Bi--qBOLYRBu3IvGZag79UZphXyDC53j3DHHmhvNopMw7CNA> <xmx:QIJ8X9f1nAtn0rEBawaHEF8jRnyprJvuU-oOnGDakZCuspDKL2ojwg> <xmx:QIJ8X-OaK0dtWNaeFv5sUINgIdUXvl5cwHKZdya7awNlWyVoQUwG4g> <xmx:QYJ8X4VdCF9tNzw9ppDK3cFp_zXHFslh8kUUOn5hAiIAnIi2uX0MxH1rdg8>
Received: from EMB-918HFH01 (87-93-25-35.bb.dnainternet.fi [87.93.25.35]) by mail.messagingengine.com (Postfix) with ESMTPA id 533D73280067; Tue, 6 Oct 2020 10:42:06 -0400 (EDT)
Date: Tue, 06 Oct 2020 17:42:05 +0300
From: Jaime Jiménez <jaime@iki.fi>
To: Carsten Bormann <cabo@tzi.org>
Cc: Mark Trayer <m.trayer@samsung.com>, "core-parameters@ietf.org" <core-parameters@ietf.org>
Message-ID: <20201006144205.w3c2pdqvva4d3gzq@EMB-918HFH01>
References: <CGME20201005180654uscas1p237d98feca34e8c26480fb4893ecf357c@uscas1p2.samsung.com> <0e4c1f71d9964f929ba888e963be656f@sraex01sc.sisa.samsung.com> <C7BCC9A8-5F95-46F0-B023-7D1749A8C00D@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <C7BCC9A8-5F95-46F0-B023-7D1749A8C00D@tzi.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core-parameters/2srPn9FM4dzzPxEuBPGvPPE1uPA>
Subject: Re: [core-parameters] NEW RESOURCE TYPES - oic.r.* and oic.d.*
X-BeenThere: core-parameters@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Expert review of CoAP parameters." <core-parameters.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core-parameters>, <mailto:core-parameters-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core-parameters/>
List-Post: <mailto:core-parameters@ietf.org>
List-Help: <mailto:core-parameters-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core-parameters>, <mailto:core-parameters-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Oct 2020 14:42:15 -0000

Hi Carsten and Mark,

Just FYI. I also had a look at the OCF spec and the new attributes look OK to me. 

Ciao!
-- Jaime

On 06.10.2020 14:55, Carsten Bormann wrote:
>Hi Mark,
>
>these look good to me; please go ahead as Klaus suggested and ask IANA for registration.
>
>I note that the description of the “priv” flag for oic.r.sdi in Table 55 of the OCF Security Specification (»Flag to indicate whether the Security Domain Information is copied to “/oic/res”«) and on the OpenAPI definition in C.10.4 is the wrong way around (the rest of the text around Table 55 makes that clear, but it is still very confusing, in particular if only looking at the OpenAPI description).
>
>Grüße, Carsten
>
>
>
>
>> On 2020-10-05, at 20:06, Mark Trayer <m.trayer@samsung.com> wrote:
>>
>> The Open Connectivity Foundation has specified an additional set of rt values (all beginning with “oic.”) to be registered in the
>> http://www.iana.org/assignments/core-parameters/core-parameters.xhtml#rt-link-target-att-value registry according to the “Specification Required” policy.
>> The references for all of them are in the ZIP file at https://openconnectivity.org/specs/OCF_v2.2.0%20Specification.zip
>>
>> Since registering a prefix is not currently allowed, here is a list of the separate rt values requested to register.
>>
>> Resource Type (rt=) Link Target Attribute Value
>> Attribute Value
>> Description
>> Reference
>> oic.d.afci
>> Arc Fault Circuit Interrupter
>> OCF_Device_Specification_v2.2.0 clause A.2
>> oic.d.airer
>> Airer
>> OCF_Device_Specification_v2.2.0 clause A.2
>> oic.d.gfci
>> Ground Fault Circuit Interrupter
>> OCF_Device_Specification_v2.2.0 clause A.2
>> oic.r.sdi
>> Security Domain Information
>> OCF_Security_Specification_v2.2.0 clause C.10
>> oic.r.settings.accessibility
>> Device Settings - Accessibility
>> OCF_Resource_Type_Specification_v2.2.0 clause 6.164
>> oic.r.settings.broadcasting
>> Device Settings - Broadcasting
>> OCF_Resource_Type_Specification_v2.2.0 clause 6.165
>> oic.r.settings.picture
>> Device Settings - Picture
>> OCF_Resource_Type_Specification_v2.2.0 clause 6.166
>> oic.r.settings.sound
>> Devcie Settings - Sound
>> OCF_Resource_Type_Specification_v2.2.0 clause 6.167
>> oic.r.settings.support
>> Device Settings - Support
>> OCF_Resource_Type_Specification_v2.2.0 clause 6.168
>> oic.r.settings.system
>> Device Settings - System
>> OCF_Resource_Type_Specification_v2.2.0 clause 6.169
>>
>> Please let me know if there are any questions or clarifications required in this regard.
>>
>> Best,
>> Mark Trayer
>> OCF Core Technology Working Group Chair
>> _______________________________________________
>> core-parameters mailing list
>> core-parameters@ietf.org
>> https://www.ietf.org/mailman/listinfo/core-parameters
>
>_______________________________________________
>core-parameters mailing list
>core-parameters@ietf.org
>https://www.ietf.org/mailman/listinfo/core-parameters