IETF Logo Mail Archive

Re: [core] RFC 8768 on Constrained Application Protocol (CoAP) Hop-Limit Option

Carsten Bormann <cabo@tzi.org> Mon, 23 March 2020 07:24 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 995333A0879; Mon, 23 Mar 2020 00:24:33 -0700 (PDT)
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, 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 wDsBPUzxNijK; Mon, 23 Mar 2020 00:24:31 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCAE63A0861; Mon, 23 Mar 2020 00:24:30 -0700 (PDT)
Received: from [192.168.217.147] (p548DCD70.dip0.t-ipconnect.de [84.141.205.112]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 48m5VN72DZzyws; Mon, 23 Mar 2020 08:24:28 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <787AE7BB302AE849A7480A190F8B93303147B5EA@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Date: Mon, 23 Mar 2020 08:24:28 +0100
Cc: "dots@ietf.org" <dots@ietf.org>, "core@ietf.org" <core@ietf.org>
X-Mao-Original-Outgoing-Id: 606641068.7406729-4bfbbd449e01cb3ffb1965fa5bb8b5cc
Content-Transfer-Encoding: quoted-printable
Message-Id: <02223369-0FA8-4B77-B64D-732911C936BE@tzi.org>
References: <20200321042126.5078DF40713@rfc-editor.org> <C9C99C44-AD7B-4354-9735-6F25D253DDDB@tzi.org> <787AE7BB302AE849A7480A190F8B93303147B5EA@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
To: mohamed.boucadair@orange.com
X-Mailer: Apple Mail (2.3608.60.0.2.5)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/Jx4BddozttaQGYVMZ-m05ap0p88>
Subject: Re: [core] RFC 8768 on Constrained Application Protocol (CoAP) Hop-Limit Option
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, 23 Mar 2020 07:24:34 -0000

On 2020-03-23, at 08:18, mohamed.boucadair@orange.com wrote:
> 
> There was a point raised during the publication of this RFC: HTTP option encapsulating CoAP ones. I hope that someone can take that work. 

It’s on my to-do list.

Anyone who wants to help?

Grüße, Carsten

v2.23.0 | Report a Bug | By Email