COAP Redirects
draft-thaler-core-redirect-01

Document Type Active Internet-Draft (individual)
Last updated 2016-10-31
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          D. Thaler
Internet-Draft                                                 Microsoft
Intended status: Informational                          October 31, 2016
Expires: May 4, 2017

                             COAP Redirects
                     draft-thaler-core-redirect-01

Abstract

   This document allows a Constrained Application Protocol (CoAP) server
   to redirect a client to a new URI.  The primary use case is to allow
   a client using multicast CoAP discovery to learn a COAPS endpoint of
   the server, without the server revealing privacy-sensitive
   information.  This improves security and privacy in environments with
   untrusted clients.

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 http://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 May 4, 2017.

Copyright Notice

   Copyright (c) 2016 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
   (http://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

Thaler                     Expires May 4, 2017                  [Page 1]
Internet-Draft               COAP Redirects                 October 2016

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Example . . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Alternatives Considered . . . . . . . . . . . . . . . . . . .   4
     2.1.  Just use normal multicast discovery . . . . . . . . . . .   4
     2.2.  Just use a resource directory . . . . . . . . . . . . . .   4
     2.3.  Use Alternative-Address . . . . . . . . . . . . . . . . .   5
   3.  Redirects . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Option Definitions  . . . . . . . . . . . . . . . . . . .   5
       3.1.1.  Location-Scheme and Location-Authority  . . . . . . .   5
     3.2.  Response Codes  . . . . . . . . . . . . . . . . . . . . .   6
       3.2.1.  3.01 Moved Permanently  . . . . . . . . . . . . . . .   6
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   The Constrained Application Protocol (CoAP) [RFC7252] is a
   specialized web transfer protocol for use with constrained nodes and
   constrained networks.  When COAP nodes can appear on a network that
   allows untrusted clients, security and privacy issues can arise, as
   discussed in Section 11 of [RFC7252].

   This document focuses on a solution for a specific use case:
   preventing privacy-sensitive information from being passed to
   untrusted clients, especially as part of resource discovery.  The
   resource discovery phase is important because DTLS is not used with
   multicast COAP.

   The specific relevant threats are:

   o  Correlation across location: If a COAP server can move between
      multiple networks in which an attacker has a presence, the
      attacker can potentially correlate responses from the COAP server
      across the two locations and determine that the same entity is
      moving between those two locations.  This can even be used to
      identify individuals, such as when the COAP server is in a
      wearable device.

Thaler                     Expires May 4, 2017                  [Page 2]
Internet-Draft               COAP Redirects                 October 2016
Show full document text