[Dots] TR: Last Call: <draft-ietf-core-hop-limit-05.txt> (Constrained Application Protocol (CoAP) Hop-Limit Option) to Proposed Standard

<mohamed.boucadair@orange.com> Tue, 17 September 2019 06:27 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C4DD12008C for <dots@ietfa.amsl.com>; Mon, 16 Sep 2019 23:27:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 k0KA4dTBDvHw for <dots@ietfa.amsl.com>; Mon, 16 Sep 2019 23:27:41 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61EC3120058 for <dots@ietf.org>; Mon, 16 Sep 2019 23:27:41 -0700 (PDT)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) by opfedar24.francetelecom.fr (ESMTP service) with ESMTP id 46XY7c0Zr7z5wP0 for <dots@ietf.org>; Tue, 17 Sep 2019 08:27:40 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.73]) by opfedar02.francetelecom.fr (ESMTP service) with ESMTP id 46XY7b6v0YzCr6k for <dots@ietf.org>; Tue, 17 Sep 2019 08:27:39 +0200 (CEST)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM23.corporate.adroot.infra.ftgroup ([fe80::9108:27dc:3496:8db3%21]) with mapi id 14.03.0468.000; Tue, 17 Sep 2019 08:27:39 +0200
From: <mohamed.boucadair@orange.com>
To: "dots@ietf.org" <dots@ietf.org>
Thread-Topic: Last Call: <draft-ietf-core-hop-limit-05.txt> (Constrained Application Protocol (CoAP) Hop-Limit Option) to Proposed Standard
Thread-Index: AQHVajxGp+LXPiYpbkiEK/s1xEA4F6cvbEuw
Date: Tue, 17 Sep 2019 06:27:38 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933031321AF5@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <156838351509.32043.17242089334872616244.idtracker@ietfa.amsl.com>
In-Reply-To: <156838351509.32043.17242089334872616244.idtracker@ietfa.amsl.com>
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/dots/4t6OFqUfFtuVCg-WRg-zaisNRdk>
Subject: [Dots] TR: Last Call: <draft-ietf-core-hop-limit-05.txt> (Constrained Application Protocol (CoAP) Hop-Limit Option) to Proposed Standard
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Sep 2019 06:27:43 -0000

Hi all,

FYI. This draft is cited as a normative reference in the base DOTS spec.  

Please let us know if you have any comment on the hop-limit spec. 

Cheers,
Med

> -----Message d'origine-----
> De : iesg-secretary@ietf.org [mailto:iesg-secretary@ietf.org]
> Envoyé : vendredi 13 septembre 2019 16:05
> À : IETF-Announce
> Cc : draft-ietf-core-hop-limit@ietf.org; Jaime Jimenez; jaime@iki.fi;
> core@ietf.org; alexey.melnikov@isode.com; core-chairs@ietf.org
> Objet : Last Call: <draft-ietf-core-hop-limit-05.txt> (Constrained
> Application Protocol (CoAP) Hop-Limit Option) to Proposed Standard
> 
> 
> The IESG has received a request from the Constrained RESTful Environments
> WG
> (core) to consider the following document: - 'Constrained Application
> Protocol (CoAP) Hop-Limit Option'
>   <draft-ietf-core-hop-limit-05.txt> as Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final
> comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2019-09-27. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the beginning
> of
> the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    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.
> 
> 
> 
> 
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-core-hop-limit/
> 
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-core-hop-limit/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 
>