Movatterモバイル変換


[0]ホーム

URL:


Search RFCs

Advanced Search

RFC Editor

RFC 8768

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

File formats:

icon for HTMLicon for text fileicon for v3pdficon 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 listcore@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 maylead to infinite forwarding loops, which is undesirable. To preventand detect such loops, this document specifies the Hop-Limit CoAPoption.


For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.




IABIANAIETFIRTFISEISOCIETF Trust
ReportsPrivacy StatementSite MapContact Us

Advanced Search

[8]ページ先頭

©2009-2026 Movatter.jp