Javascript disabled? Like other modern websites, the IETF Datatracker relies on Javascript. Please enable Javascript for full functionality.

Constrained Application Protocol (CoAP) Hop-Limit Option
RFC 8768

Revision differences

From revision

To revision

Diff format

Document history

Date	By	Action
2020-03-20	(System)	Received changes through RFC Editor sync (created alias RFC 8768, changed abstract to 'The presence of Constrained Application Protocol (CoAP) proxies may lead to … Received changes through RFC Editor sync (created alias RFC 8768, changed abstract to '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.', changed pages to 8, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2020-03-20, changed IESG state to RFC Published)
2020-03-20	(System)	RFC published