CoAP Protocol Negotiation
draft-silverajan-core-coap-protocol-negotiation-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-09-08
Stream (None)
Intended RFC status (None)
Formats pdf htmlized 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)
CoRE Working Group                                         B. Silverajan
Internet-Draft                          Tampere University of Technology
Intended status: Informational                         September 8, 2015
Expires: March 11, 2016

                       CoAP Protocol Negotiation
           draft-silverajan-core-coap-protocol-negotiation-01

Abstract

   CoAP has been standardised as an application-level REST-based
   protocol.  This document introduces a way forward for CoAP clients
   and servers to exchange resource representations when multiple
   transports exist at an endpoint, by agreeing upon alternate locations
   as well as transport and protocol configurations.

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 March 11, 2016.

Copyright Notice

   Copyright (c) 2015 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Silverajan               Expires March 11, 2016                 [Page 1]
Internet-Draft          CoAP Protocol Negotiation         September 2015

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Rationale . . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Goals . . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  New Link Attribute and Relation types . . . . . . . . . . . .   4
   5.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . .   7
     A.1.  From -00 to -01 . . . . . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   In the Constrained Application Protocol (CoAP) [RFC7252], resources
   are uniquely represented by Uniform Resource Identifiers (URIs).
   Using URIs, CoAP endpoints, such as clients, origin servers and
   proxies, are able to exchange representations using REST-based
   methods.  A URI in CoAP serves two purposes.  Firstly, it functions
   as a locator, by specifying the network location of the endpoint
   hosting the resource, and the underlying transport used by CoAP for
   accessing the resource representation.  Secondly, it identifies the
   name of the specific resource found at that endpoint together with
   its namespace, or resource path.

   This draft proposes a new link format attribute as well as a new link
   relation type that together enable an origin server to serve a
   resource from other protocol configuratons or endpoints.  CoAP
   clients then interact with an origin server's CoRE resource discovery
   interface to obtain a set of links describing alternate locations of
   resources.

2.  Rationale

   Ongoing activity and discussion in CoRE has revealed the need to
   convey CoAP messages over not just UDP and DTLS, but also over
   alternative transports such as SMS [I-D.becker-core-coap-sms-gprs],
   TCP [I-D.tschofenig-core-coap-tcp-tls] and WebSockets
   [I-D.savolainen-core-coap-websockets].  The underlying transport to
   be used by CoAP is identified by the scheme component of a new URI
   format, as described in
   [I-D.silverajan-core-coap-alternative-transports].

Silverajan               Expires March 11, 2016                 [Page 2]
Internet-Draft          CoAP Protocol Negotiation         September 2015
Show full document text