Re: [core] [Anima] constrained resources at root for debugging connectivity

Peter van der Stok <stokcons@bbhmail.nl> Thu, 22 July 2021 06:56 UTC

Return-Path: <stokcons@bbhmail.nl>
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 B88883A3B3A; Wed, 21 Jul 2021 23:56:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.093
X-Spam-Level:
X-Spam-Status: No, score=-2.093 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bbhmail.nl
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 jwKue5GPyDWa; Wed, 21 Jul 2021 23:55:58 -0700 (PDT)
Received: from smtprelay.hostedemail.com (smtprelay0046.hostedemail.com [216.40.44.46]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC0A23A3B36; Wed, 21 Jul 2021 23:55:57 -0700 (PDT)
Received: from omf06.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay01.hostedemail.com (Postfix) with ESMTP id ED987100E7B49; Thu, 22 Jul 2021 06:55:55 +0000 (UTC)
Received: from [HIDDEN] (Authenticated sender: stokcons@bbhmail.nl) by omf06.hostedemail.com (Postfix) with ESMTPA id 9631C2448BC; Thu, 22 Jul 2021 06:55:55 +0000 (UTC)
MIME-Version: 1.0
Date: Thu, 22 Jul 2021 08:55:55 +0200
From: Peter van der Stok <stokcons@bbhmail.nl>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: Esko Dijk <esko.dijk@iotconsultancy.nl>, anima@ietf.org, core@ietf.org
Reply-To: stokcons@bbhmail.nl
In-Reply-To: <25674.1626896178@localhost>
References: <AM8P190MB097901225CE72EF7973ADCC4FD139@AM8P190MB0979.EURP190.PROD.OUTLOOK.COM> <AM8P190MB09791181A1D8F74ECDC6F04FFD129@AM8P190MB0979.EURP190.PROD.OUTLOOK.COM> <d2da849f46f57a410d28f47d4ed32f97@bbhmail.nl> <AM8P190MB0979B2CB8DEDB7E9FDCF9C73FDE19@AM8P190MB0979.EURP190.PROD.OUTLOOK.COM> <6b1b6fc38752b6f0598d4289c7cfeb31@bbhmail.nl> <AM8P190MB0979C689144DE6989C5D33E7FDE29@AM8P190MB0979.EURP190.PROD.OUTLOOK.COM> <8c3348a5adb2b2c0d0a4b615cadc75a6@bbhmail.nl> <AM8P190MB0979EC82DA418ECF74440BA9FDE29@AM8P190MB0979.EURP190.PROD.OUTLOOK.COM> <57da5e79b97eeca3967da119a60b0ed6@bbhmail.nl> <AM8P190MB0979EBF594EA31877BFBED5DFDE29@AM8P190MB0979.EURP190.PROD.OUTLOOK.COM> <18975.1626788349@localhost> <AM8P190MB097925B04E575071242002CFFDE39@AM8P190MB0979.EURP190.PROD.OUTLOOK.COM> <25674.1626896178@localhost>
User-Agent: Roundcube Webmail/1.4.11
Message-ID: <d74844a35caf7562aeeed8127d454dc7@bbhmail.nl>
X-Sender: stokcons@bbhmail.nl
Organization: vanderstok consultancy
Content-Type: multipart/alternative; boundary="=_31766e53aceb2e8260c9d0050e54d310"
X-Rspamd-Server: rspamout04
X-Rspamd-Queue-Id: 9631C2448BC
X-Stat-Signature: s47kt4u4icw57dk6g4rqm5wuougs79tt
X-Session-Marker: 73746F6B636F6E73406262686D61696C2E6E6C
X-Session-ID: U2FsdGVkX18uT3dgqVi8mx+HNBWRnfSrWmx9arg1dnU=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bbhmail.nl; h=mime-version:date:from:to:cc:subject:reply-to:in-reply-to:references:message-id:content-type; s=key; bh=gldsS7ap+HlHmaWWs1mXHAWfxt/WimEvxfKtaiVW1sw=; b=KPZT+IUoSOcwGgqx1exBscq09Tm2gGnlsTvc3TcJr+pdrpYUSxtGI9Q9/n17JDvvcs0ZPGNEUTKbqyW/4TuCaQBwgcKKbQ92Qe0pc8RC0I0JyVsuoSpUf56KaBh787/HUTmZYEjpOwKwDTeiuMFdP+YocDYM+DgQOFr3odXRAiI=
X-HE-Tag: 1626936955-288880
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/-TDO--PcbSov003_JetE9puTlcQ>
Subject: Re: [core] [Anima] constrained resources at root for debugging connectivity
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: Thu, 22 Jul 2021 06:56:04 -0000

Is there a way to use Olaf's "coap-client" to do the ping?
I don't see an option, and it also doesn't seem to be commonly built 
with DTLS.

No, I have a three lines of code for doing a ping, from pledge; not from 
coap_client

Peter
Michael Richardson schreef op 2021-07-21 21:36:

> Esko Dijk <esko.dijk@iotconsultancy.nl> wrote:
>> There is already a "CoAP ping" described in RFC 7252 that can be
>> used. It does not access any resource, just the CoAP server endpoint 
>> at
>> CoAP message layer. As a side effect of this ping your DTLS stack will
>> set up the connection which is handy.
> 
> I recalled that later in the day that CoAP "ping" is not connected to 
> CoAP
> "echo" :-)
> I think that there is also potentially a need for a way to debug 
> possible MTU
> issues.
> Is there a way to use Olaf's "coap-client" to do the ping?
> I don't see an option, and it also doesn't seem to be commonly built 
> with DTLS.
> We also have the issue of CCM8 vs OpenSSL that I thought got solved, 
> but it
> appears that it has not been, so one needs a tool built with mbedtls or 
> wolfSSL.
> 
>> So I don't think we need a resource at / that produces 2.05 , this is
>> for the maintainer of the server to decide how to allocate that
>> resource space.
> 
>> Besides we have already defined some well-known resources accessible
>> with GET ( in core/est/brski) that the client could make use of to 
>> test
>> connectivity.
> 
>> Even a non-existing resource in the /.well-known/X space could be used
>> just to get a 4.04 which confirms the server is working properly. This
>> is even better that trying to GET a resource of who knows how large
>> size.
> 
> BTW, I've changed my /version.json so that it now looks for and returns 
> the
> client certificate that it saw:
> 
> curl
> --cert spec/files/product/00-D0-E5-02-00-2E/device.crt
> --key  spec/files/product/00-D0-E5-02-00-2E/key.pem
> https://masa.honeydukes.sandelman.ca/version.json
> 
> ->
> 
> {"version":"1.1.0","revision":"582044cfc536fd295e8bdcd3b90f30453d7784d3","Hostname":"masa.honeydukes.sandelman.ca","client_certificate":"-----BEGIN 
> CERTIFICATE-----\nMIICBjCCAYugAwIBAgIEXKnlyDAKBggqhkjOPQQDAjBNMRIwEAYKCZImiZPyLGQB\nGRYCY2ExGTAXBgoJkiaJk/IsZAEZFglzYW5kZWxtYW4xHDAaBgNVBAMME1Vuc3Ry\ndW5nIEhpZ2h3YXkgQ0EwIBcNMTkwNDI0MDIxNjU4WhgPMjk5OTEyMzEwMDAwMDBa\nMBwxGjAYBgNVBAUMETAwLWQwLWU1LTAyLTAwLTJlMFkwEwYHKoZIzj0CAQYIKoZI\nzj0DAQcDQgAEey+I0TtIhm8ivRJY36vF5ZRHs/IwhQWRc2Ql70rN+aYLZPOIXYc6\nZzlO62kDYBo3IPrcjkiPVnhoCosUBpTzbqOBhzCBhDAdBgNVHQ4EFgQU/g+KaX9o\nDEKY2K3NGe7Vr/9geDAwCQYDVR0TBAIwADArBgNVHREEJDAioCAGCSsGAQQBgu5S\nAaATDBEwMC1EMC1FNS0wMi0wMC0yRTArBgkrBgEEAYLuUgIEHgwcbWFzYS5ob25l\neWR1a2VzLnNhbmRlbG1hbi5jYTAKBggqhkjOPQQDAgNpADBmAjEAuEwTKPMzS/Xm\nAhR4tFtDo3YHoPoBsaw/6UUYDHot4EoKy2L8AlriFzti/iNmH67/AjEAnRjH2R0T\n98DZjBIhz7W8LM52AeymMdCtsJyuDRjtVuncGEfMO/OWuFFx5qwYR63I\n-----END 
> CERTIFICATE-----\n"}
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT 
> consulting )
> Sandelman Software Works Inc, Ottawa and Worldwide
> 
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima