The application/maybe media type
draft-bormann-core-maybe-00

Document Type Active Internet-Draft (individual)
Last updated 2018-03-18
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
CoRE Working Group                                            C. Bormann
Internet-Draft                                   Universitaet Bremen TZI
Intended status: Informational                            March 18, 2018
Expires: September 19, 2018

                    The application/maybe media type
                      draft-bormann-core-maybe-00

Abstract

   Many media types may be used in situations where it may beneficial to
   indicate that the object represented in this media type is not yet
   (or no longer) present.

   The Observe option introduced in Observing Resources in the
   Constrained Application Protocol (CoAP) (RFC7641) requires sequences
   of responses (notifications) to carry the same Content-Format.

   The application/maybe media type provides a way to use a single media
   type (and thus Content-Format) to express presence or absence of
   information in a specific media type.

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 September 19, 2018.

Copyright Notice

   Copyright (c) 2018 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

Bormann                Expires September 19, 2018               [Page 1]
Internet-Draft      The application/maybe media type          March 2018

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  The application/maybe media type  . . . . . . . . . . . . . .   2
   3.  Discussion  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Implementation hints  . . . . . . . . . . . . . . . . . . . .   3
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   (See Abstract.)

1.1.  Terminology

   This memo uses terms from [RFC7252], [RFC7641] and [RFC7049].

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.  These words may also appear in this
   document in lower case as plain English words, absent their normative
   meanings.

   The term "byte", abbreviated by "B", is used in its now customary
   sense as a synonym for "octet".

2.  The application/maybe media type

   An application/maybe object either indicates the absence of the
   underlying media type or its presence together with an object of that
   media type.

Bormann                Expires September 19, 2018               [Page 2]
Internet-Draft      The application/maybe media type          March 2018

   This is represented by a CBOR [RFC7049] object structured as follows
   (illustrated in CDDL [I-D.ietf-cbor-cddl]):

   maybe = [
     ? (
       content-format: uint,
       content: bstr
     )
   ]

3.  Discussion

   The position for indicating a content-format could also provide an
   alternative for indicating a media type represented as a string.

   maybe1 = [
     ? (
       (content-format: uint // media-type: tstr),
       content: bstr
     )
   ]

   This would make the application/maybe media type easier to use with
   media types that do not have a content-format registered yet.
Show full document text