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

From: <[email-masked]>
Date: Tue, 17 Sep 2019 06:27:38 +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 : [email-masked] [mailto:[email-masked]]
> Envoyé : vendredi 13 septembre 2019 16:05
> À : IETF-Announce
> Cc : [email-masked]; Jaime Jimenez; [email-masked];
> [email-masked]; [email-masked]; [email-masked]
> 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
> [email-masked] mailing lists by 2019-09-27. Exceptionally, comments may be
> sent to [email-masked] 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.
> 
> 
>