Subject: [core] TR: New Version Notification for draft-ietf-core-hop-limit-04.txt

From: <[email-masked]>
Date: Wed, 3 Jul 2019 14:54:30 +0000

Hi all, 

We tried to address the comments raised during the WGLC. The main changes are:
* Include a new section to clarify the intended usage. This one is kindly provided by Carsten.
* Add a new section to specify HTTP mappings.
* Clarify the usage when there is no space left to prepend a proxy information.

Other edits were also made.

Please let's know if we missed any of the WGLC comments.

Cheers,
Med

> -----Message d'origine-----
> De : [email-masked] [mailto:[email-masked]]
> Envoyé : mercredi 3 juillet 2019 16:50
> À : Tirumaleswar Reddy; Jon Shallow; Reddy K; BOUCADAIR Mohamed TGI/OLN
> Objet : New Version Notification for draft-ietf-core-hop-limit-04.txt
> 
> 
> A new version of I-D, draft-ietf-core-hop-limit-04.txt
> has been successfully submitted by Mohamed Boucadair and posted to the
> IETF repository.
> 
> Name:		draft-ietf-core-hop-limit
> Revision:	04
> Title:		Constrained Application Protocol (CoAP) Hop-Limit Option
> Document date:	2019-07-03
> Group:		core
> Pages:		8
> URL:            https://www.ietf.org/internet-drafts/draft-ietf-core-hop-
> limit-04.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-core-hop-
> limit/
> Htmlized:       https://tools.ietf.org/html/draft-ietf-core-hop-limit-04
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-core-hop-
> limit
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-core-hop-
> limit-04
> 
> 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.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat