Architectural Considerations in Smart Object Networking
draft-iab-smart-object-architecture-04

The information below is for an old version of the document
Document Type Active Internet-Draft
Last updated 2014-07-04
Replaces draft-tschofenig-smart-object-architecture
Stream IAB
Intended RFC status (None)
Formats plain text pdf html bibtex
Additional URLs
Stream IAB state IAB Review
Consensus Boilerplate Unknown
RFC Editor Note (None)
Network Working Group                                      H. Tschofenig
Internet-Draft
Intended status: Informational                                  J. Arkko
Expires: January 5, 2015
                                                               D. Thaler

                                                            D. McPherson

                                                            July 4, 2014

        Architectural Considerations in Smart Object Networking
               draft-iab-smart-object-architecture-04.txt

Abstract

   Following the theme "Everything that can be connected will be
   connected", engineers and researchers designing smart object networks
   need to decide how to achieve this in practice.

   This document offers guidance to engineers designing Internet
   connected smart objects.

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 January 5, 2015.

Copyright Notice

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

Tschofenig, et al.       Expires January 5, 2015                [Page 1]
Internet-Draft  Smart Object Architectural Considerations      July 2014

   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
   2.  Utilize Design Patterns . . . . . . . . . . . . . . . . . . .   3
     2.1.  Device-to-Device Communication Pattern  . . . . . . . . .   4
     2.2.  Device-to-Cloud Communication Pattern . . . . . . . . . .   5
     2.3.  Device-to-Gateway Communication Pattern . . . . . . . . .   6
     2.4.  Back-end Data Sharing Pattern . . . . . . . . . . . . . .   7
   3.  Re-Use Internet Protocols . . . . . . . . . . . . . . . . . .   8
   4.  The Deployed Internet Matters . . . . . . . . . . . . . . . .  11
   5.  Design for Change . . . . . . . . . . . . . . . . . . . . . .  12
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   7.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  14
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  15
   10. Informative References  . . . . . . . . . . . . . . . . . . .  15
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

   RFC 6574 [1] refers to smart objects (also called "Things", as in
   Internet of Things in other publications) as devices with constraints
   on energy, bandwidth, memory, size, cost, etc.  This is a fuzzy
   definition, as there is clearly a continuum in device capabilities
   and there is no hard line to draw between devices that can run
   Internet Protocols and those that can't.

   Interconnecting smart objects with the Internet creates exciting new
   innovative use cases and products.  An increasing number of products
   put the Internet Protocol suite on smaller and smaller devices and
   offer the ability to process, visualize, and gain new insight from
   the collected sensor data.  The network effect can be increased if
   the data collected from many different devices can be combined.

   Developing embedded systems is a complex task and designing Internet
   connected smart objects is even harder since it "requires expertise
   with Internet protocols in addition to software programming and
   hardware skills.  To simply the development task, and thereby to
   lower the cost of developing new products and prototypes, we believe
   that re-use of prior work is essential.  Therefore, we provide high-

Tschofenig, et al.       Expires January 5, 2015                [Page 2]
Internet-Draft  Smart Object Architectural Considerations      July 2014

   level guidance on the use of Internet technology for the development
   of smart objects.
Show full document text