Transport of CoAP over SMS
draft-becker-core-coap-sms-gprs-06

Document Type Active Internet-Draft (individual)
Last updated 2017-02-19
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)
CoRE                                                 K. Kuladinithi, Ed.
Internet-Draft                 ComNets, Hamburg University of Technology
Intended status: Standards Track                               M. Becker
Expires: August 24, 2017                           Tridonic GmbH & Co KG
                                                                   K. Li
                                                           Alibaba Group
                                                              T. Poetsch
                                           New York University Abu Dhabi
                                                       February 20, 2017

                       Transport of CoAP over SMS
                   draft-becker-core-coap-sms-gprs-06

Abstract

   Short Message Service (SMS) of mobile cellular networks is frequently
   used in Machine-To-Machine (M2M) communications, such as for
   telematic devices.  The service offers small packet sizes and high
   delays just as other typical low-power and lossy networks (LLNs),
   i.e. 6LoWPANs.  The design of the Constrained Application Protocol
   (CoAP, RFC7252), that took the limitations of LLNs into account, is
   thus also applicable to other transports.  The adaptation of CoAP to
   SMS transport mechanisms is described in this document.

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 August 24, 2017.

Copyright Notice

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

Kuladinithi, et al.      Expires August 24, 2017                [Page 1]
Internet-Draft                CoAP over SMS                February 2017

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Motivation  . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     1.3.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   2.  Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  MO-MT Scenarios . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  MT Scenarios  . . . . . . . . . . . . . . . . . . . . . .   4
     2.3.  MO Scenarios  . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Message Exchanges . . . . . . . . . . . . . . . . . . . . . .   6
     3.1.  Message Exchange for SMS in a Cellular-To-Cellular
           Mobile-Originated and Mobile-Terminated Scenario  . . . .   6
   4.  Encoding Schemes of CoAP for SMS transport  . . . . . . . . .   7
   5.  Message Size Implementation Considerations  . . . . . . . . .   7
   6.  Addressing  . . . . . . . . . . . . . . . . . . . . . . . . .   8
   7.  Options . . . . . . . . . . . . . . . . . . . . . . . . . . .   8
     7.1.  New Options for mixed IP operation. . . . . . . . . . . .   8
   8.  URI Scheme  . . . . . . . . . . . . . . . . . . . . . . . . .   9
   9.  Transmission Parameters . . . . . . . . . . . . . . . . . . .   9
   10. Multicast . . . . . . . . . . . . . . . . . . . . . . . . . .   9
   11. Security Considerations . . . . . . . . . . . . . . . . . . .   9
   12. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
     12.1.  CoAP Option Number . . . . . . . . . . . . . . . . . . .  10
     12.2.  URI Scheme Registration  . . . . . . . . . . . . . . . .  10
   13. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     13.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     13.2.  Informative References . . . . . . . . . . . . . . . . .  11
   Appendix A.  SMS encoding . . . . . . . . . . . . . . . . . . . .  12
Show full document text