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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-12-28
Stream IAB
Intended RFC status (None)
Formats plain text pdf html bibtex
Additional URLs
Stream IAB state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
Network Working Group                                      H. Tschofenig
Internet-Draft                                                  J. Arkko
Intended status: Informational                                 D. Thaler
Expires: July 1, 2013                                       D. McPherson
                                                       December 28, 2012

        Architectural Considerations in Smart Object Networking
               draft-iab-smart-object-architecture-00.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.  How can different
   forms of embedded and constrained devices be interconnected?  How can
   they employ and interact with the currently deployed Internet?  This
   memo discusses smart objects and some of the architectural choices
   involved in designing smart object networks and protocols that they
   use.

   The document is being discussed at
   https://www.ietf.org/mailman/listinfo/architecture-discuss

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 July 1, 2013.

Copyright Notice

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

Tschofenig, et al.        Expires July 1, 2013                  [Page 1]
Internet-Draft  Smart Object Architectural Considerations  December 2012

   (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
   2.  Specific and General Purpose Solutions . . . . . . . . . . . .  5
   3.  Deployment Constraints in the Internet . . . . . . . . . . . .  7
   4.  The Need for Standards . . . . . . . . . . . . . . . . . . . .  9
     4.1.  Managing Complexity  . . . . . . . . . . . . . . . . . . .  9
     4.2.  Interoperability Architecture  . . . . . . . . . . . . . . 10
     4.3.  Internet Protocols for Proprietary Protocol
           Developments . . . . . . . . . . . . . . . . . . . . . . . 13
     4.4.  Interoperability . . . . . . . . . . . . . . . . . . . . . 14
     4.5.  Design for Change  . . . . . . . . . . . . . . . . . . . . 16
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . . 17
   6.  Privacy Considerations . . . . . . . . . . . . . . . . . . . . 18
   7.  Summary  . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 23
   9.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 24
   10. Informative References . . . . . . . . . . . . . . . . . . . . 25
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 27

Tschofenig, et al.        Expires July 1, 2013                  [Page 2]
Internet-Draft  Smart Object Architectural Considerations  December 2012

1.  Introduction

   In RFC 6574 [1], we refer to smart objects 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 be classified as smart objects and those that can't.

   Following the theme "Everything that can be connected will be
   connected", engineers and researchers designing smart object networks
   need to address a number of questions.  How can different forms of
   embedded and constrained devices be interconnected?  How can they
   employ and interact with the currently deployed Internet?

   These questions have been discussed at length.  For instance, when
   the Internet Architecture Board (IAB) scheduled a workshop on Smart
   Objects, the IETF community was asked to develop views on how
   Internet protocols can be utilized by smart objects.  A report of the
Show full document text