RFC 8768

Constrained Application Protocol (CoAP) Hop-Limit Option, March 2020

File formats:

icon for HTML icon for text file icon for v3pdf icon for XML
Also available: XML file for editing
 
Status:
PROPOSED STANDARD
Authors:
M. Boucadair
T. Reddy.K
J. Shallow
Stream:
IETF
Source:
core (wit)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC8768

Discuss this RFC: Send questions or comments to the mailing list core@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 8768


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.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search