Constrained Application Protocol (CoAP) Hop Limit Option
draft-boucadair-core-hop-limit-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Mohamed Boucadair , Tirumaleswar Reddy.K , Jon Shallow | ||
| Last updated | 2018-08-16 | ||
| Replaced by | RFC 8768 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-core-hop-limit | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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.
Authors
Mohamed Boucadair
Tirumaleswar Reddy.K
Jon Shallow
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)