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

mohamed.boucadair@orange.com Mon, 23 March 2020 07:18 UTC

Return-Path: <mohamed.boucadair@orange.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 3C4D53A087F; Mon, 23 Mar 2020 00:18:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.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 Uf2iNhmUW1Yt; Mon, 23 Mar 2020 00:18:41 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7607B3A087E; Mon, 23 Mar 2020 00:18:41 -0700 (PDT)
Received: from opfedar00.francetelecom.fr (unknown [xx.xx.xx.11]) by opfedar23.francetelecom.fr (ESMTP service) with ESMTP id 48m5Mg61jvzBrlD; Mon, 23 Mar 2020 08:18:39 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1584947919; bh=R0+X/I7R3bP6tLMwa82YA7j9Yrga9Iyj6TvFnSP0mTo=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=sVsAsBd7W/QvJduYEwu8L3TtvuOy2K4Z2P5VxUDA26F9MrPJzEYLjOWptCxsxQHIn YRt2tJrZ95zfpGuAkGQbsGIwdPPsg/wVXKmpMxqVoP0RH+BozCyYDZTlgXfIeJx0Hf vBxxVY3EqdaDPevDbqAhQPIG0pmtwYaSiTgNpvGQRkl0TgT8q2S+sQcMr/yQI1pA7r C3tTBwiusjYOEffygGnovKVFcwZWxXJvXtRE8SzhlTDbOFPhqPw72YlVKq5cnFx4DZ IMqZuE2Q/ZQn6hInDKiQfUHcnF7N+BELB9/YY8j19vAgnxRnNc7ug/56afg8kWqy6y yJnUhp7XriphA==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.64]) by opfedar00.francetelecom.fr (ESMTP service) with ESMTP id 48m5Mg4yrdzCqkG; Mon, 23 Mar 2020 08:18:39 +0100 (CET)
From: <mohamed.boucadair@orange.com>
To: Carsten Bormann <cabo@tzi.org>
CC: "dots@ietf.org" <dots@ietf.org>, "core@ietf.org" <core@ietf.org>
Thread-Topic: [core] RFC 8768 on Constrained Application Protocol (CoAP) Hop-Limit Option
Thread-Index: AQHV/zh0o79CF5P8k0SY1cBIdSPMTKhSlxIAgAMvPRA=
Date: Mon, 23 Mar 2020 07:18:39 +0000
Message-ID: =?utf-8?q?=3C787AE7BB302AE849A7480A190F8B93303147B5EA=40OPEXCAUB?= =?utf-8?q?MA2=2Ecorporate=2Eadroot=2Einfra=2Eftgroup=3E?=
References: <20200321042126.5078DF40713@rfc-editor.org> <C9C99C44-AD7B-4354-9735-6F25D253DDDB@tzi.org>
In-Reply-To: <C9C99C44-AD7B-4354-9735-6F25D253DDDB@tzi.org>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.247]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/2d2-UnPfdibTfbt9kKBIshG1xFI>
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:18:45 -0000

Hi Cartsen, 

Thank you Carsten and the core WG for helping to get this through. 

There was a point raised during the publication of this RFC: HTTP option encapsulating CoAP ones. I hope that someone can take that work. 

Cheers,
Med

> -----Message d'origine-----
> De : core [mailto:core-bounces@ietf.org] De la part de Carsten Bormann
> Envoyé : samedi 21 mars 2020 08:34
> À : core@ietf.org WG
> Objet : Re: [core] RFC 8768 on Constrained Application Protocol (CoAP)
> Hop-Limit Option
> 
> Congratulations for the publication of the 13th RFC from this WG!
> 
> The original -00 was submitted 2018-08-16, so it took a bit more than
> 1½ years to get this published (initial submission to approval was
> 2018-08-16 to 2019-11-26, so 1¼ years).
> 
> This CoRE RFC is notable in that it originated in a non-IoT WG, the
> DOTS WG (DDoS Open Threat Signaling).  I think there was some room for
> improvement in how we(*) handled this, but we did succeed, and in a
> time frame that is still quite reasonable.
> 
> Thanks to the authors for bringing this to the CoRE WG!
> 
> Grüße, Carsten
> 
> (*) I think I can say that because it’s mostly me that is to blame
> here, and I am optimistic the current chairs can be better than my
> contribution at the time was...
> 
> 
> > On 2020-03-21, at 05:21, rfc-editor@rfc-editor.org wrote:
> >
> > A new Request for Comments is now available in online RFC libraries.
> >
> >
> >        RFC 8768
> >
> >        Title:      Constrained Application Protocol (CoAP)
> >                    Hop-Limit Option
> >        Author:     M. Boucadair,
> >                    T. Reddy.K,
> >                    J. Shallow
> >        Status:     Standards Track
> >        Stream:     IETF
> >        Date:       March 2020
> >        Mailbox:    mohamed.boucadair@orange.com,
> >                    kondtir@gmail.com,
> >                    supjps-ietf@jpshallow.com
> >        Pages:      8
> >        Updates/Obsoletes/SeeAlso:   None
> >
> >        I-D Tag:    draft-ietf-core-hop-limit-07.txt
> >
> >        URL:        https://www.rfc-editor.org/info/rfc8768
> >
> >        DOI:        10.17487/RFC8768
> >
> > The presence of Constrained Application Protocol (CoAP) proxies may
> > lead to infinite forwarding loops, which is undesirable. To prevent
> > and detect such loops, this document specifies the Hop-Limit CoAP
> > option.
> >
> > This document is a product of the Constrained RESTful Environments
> Working Group of the IETF.
> >
> > This is now a Proposed Standard.
> >
> > STANDARDS TRACK: This document specifies an Internet Standards Track
> > protocol for the Internet community, and requests discussion and
> suggestions
> > for improvements.  Please refer to the current edition of the
> Official
> > Internet Protocol Standards (https://www.rfc-editor.org/standards)
> for the
> > standardization state and status of this protocol.  Distribution of
> this
> > memo is unlimited.
> >
> > This announcement is sent to the IETF-Announce and rfc-dist lists.
> > To subscribe or unsubscribe, see
> >  https://www.ietf.org/mailman/listinfo/ietf-announce
> >  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
> >
> > For searching the RFC series, see https://www.rfc-editor.org/search
> > For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
> >
> > Requests for special distribution should be addressed to either the
> > author of the RFC in question, or to rfc-editor@rfc-editor.org.
> Unless
> > specifically noted otherwise on the RFC itself, all RFCs are for
> > unlimited distribution.
> >
> >
> > The RFC Editor Team
> > Association Management Solutions, LLC
> >
> > _______________________________________________
> > IETF-Announce mailing list
> > IETF-Announce@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf-announce
> 
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core