[core] 🔔 WGLC of draft-ietf-core-hop-limit-03.txt

[Carsten Bormann <[e-mail]>]

During the last interim, we said we want to run a Working Group last call on

https://tools.ietf.org/html/draft-ietf-core-hop-limit-03


When we discussed this at the interim, we said that, apart from the overall state of the document, we would like to address two questions in this WGLC:

(1) With a way to perform proxy loop mitigation now available, what is our recommendation for usage?  Is this something that is (a) specific to DOTS, something that (b) it would now be reasonable to expect a proxy to add, or (c) something that every CoAP implementation should do?  (At the interim, we were leaning towards (b).)

(2) The HTTP world has a concurrent document addressing the same issue, 

https://tools.ietf.org/html/rfc8586

The technical approach is different here (based on leaving breadcrumbs in the requests), so it acts as a true loop prevention mechanism, not just mitigation.  It also is more expensive, adding dozens of bytes to each request passing a proxy.  Still, we want to make sure the difference in approaches is well justified.


The WGLC will end in exactly 336 hours so we can discuss the outcome at the CoRE WG Interim meeting on 2019-06-26.  Please indicate your position in a message to the CoRE mailing list ([e-mail]) or, exceptionally, to the chairs ([e-mail]).


Grüße, Carsten