IETF Logo Mail Archive

Re: [core] CoAP option for Well-Known Uri-Path

Carsten Bormann <cabo@tzi.org> Mon, 20 September 2021 08:45 UTC

Return-Path: <cabo@tzi.org>
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 0AEE53A1A7C for <core@ietfa.amsl.com>; Mon, 20 Sep 2021 01:45:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, 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 kTlwv1AlG88L for <core@ietfa.amsl.com>; Mon, 20 Sep 2021 01:45:09 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 647703A1A7B for <core@ietf.org>; Mon, 20 Sep 2021 01:45:08 -0700 (PDT)
Received: from smtpclient.apple (ip-109-43-50-15.web.vodafone.de [109.43.50.15]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4HCdRN6lybz2xJx; Mon, 20 Sep 2021 10:45:04 +0200 (CEST)
Content-Type: multipart/alternative; boundary="Apple-Mail-6F9E16A9-3F24-4E34-AE0E-0A9EDAC0CAB2"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <19899.1632082533@localhost>
Date: Mon, 20 Sep 2021 10:43:16 +0200
Cc: core@ietf.org
Message-Id: <F894A6A4-9AE2-4BF1-9261-136B33138245@tzi.org>
References: <19899.1632082533@localhost>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: iPhone Mail (18H17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/Rz7F2acdFbkCDY_s9M__1dnJBew>
Subject: Re: [core] CoAP option for Well-Known Uri-Path
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, 20 Sep 2021 08:45:14 -0000

I think the main reason that we didn’t do this right away was that the original Usage (. Well known core) was relatively rare and implied even larger data. But with other protocols using wk it may start making more sense. Unfortunately, there is no option position left that would keep the correct order in the Uri. Oh well. 

Sent from mobile, sorry for terse

> On 19. Sep 2021, at 22:16, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> 
> Has anyone considered a CoAP-Option that would compress well-known prefixes?
> So, instead of:
>    Uri-Path ".well-known"
>    Uri-Path "brski"
>    Uri-Path "sen"
> 
> one could have:
>    Well-Known-Uri-Path [CBOR-int from to be created .well-known Registry column]
>    Uri-Path "sen"
> 
> Takes some coordination to get it deployed, but in some greenfields we could
> do this now.
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
>           Sandelman Software Works Inc, Ottawa and Worldwide
> 
> 
> 
> 
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core

v2.23.0 | Report a Bug | By Email