Constrained Application Protocol (CoAP) Hop-Limit Option
draft-ietf-core-hop-limit-04

Document Type Active Internet-Draft (core WG)
Last updated 2019-07-03
Replaces draft-boucadair-core-hop-limit
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state In WG Last Call
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
CORE                                                        M. Boucadair
Internet-Draft                                                    Orange
Intended status: Standards Track                                T. Reddy
Expires: January 4, 2020                                          McAfee
                                                              J. Shallow
                                                            July 3, 2019

        Constrained Application Protocol (CoAP) Hop-Limit Option
                      draft-ietf-core-hop-limit-04

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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 4, 2020.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Boucadair, et al.        Expires January 4, 2020                [Page 1]
Internet-Draft            CoAP Hop Limit Option                July 2019

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Intended Usage  . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Hop-Limit Option  . . . . . . . . . . . . . . . . . . . . . .   3
   4.  HTTP-Mapping Considerations . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
     5.1.  CoAP Response Code  . . . . . . . . . . . . . . . . . . .   5
     5.2.  CoAP Option Number  . . . . . . . . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   More and more applications are using the Constrained Application
   Protocol (CoAP) [RFC7252] as a communication protocol between
   involved application agents.  For example,
   [I-D.ietf-dots-signal-channel] specifies how CoAP is used as a
   distributed denial-of-service (DDoS) attack signaling protocol for
   seeking for help from DDoS mitigation providers.  In such contexts, a
   CoAP client can communicate directly with a server or indirectly via
   proxies.

   When multiple proxies are involved, infinite forwarding loops may be
   experienced (e.g., routing misconfiguration, policy conflicts).  To
   prevent such loops, this document defines a new CoAP option, called
   Hop-Limit (Section 3).  Also, the document defines a new CoAP
   Response Code (Section 5.1) to report loops together with relevant
   diagnostic information to ease troubleshooting.

1.1.  Intended Usage

   The Hop-Limit option has originally been designed for a specific use
   case [I-D.ietf-dots-signal-channel].  However, its intended usage is
   general: CoAP proxies that do not have specific knowledge that proxy
   forwarding loops are avoided in some other way, are expected to
   implement this option and have it enabled by default.

   Note that this means that a server that receives requests both via
   proxies and directly from clients may see otherwise identical

Boucadair, et al.        Expires January 4, 2020                [Page 2]
Internet-Draft            CoAP Hop Limit Option                July 2019

   requests with and without the Hop-Limit option included; servers with
Show full document text