ACE use cases
draft-seitz-ace-usecases-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-07-02
Replaced by draft-ietf-ace-usecases, rfc7744
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)
ACE Working Group                                          L. Seitz, Ed.
Internet-Draft                                       SICS Swedish ICT AB
Intended status: Informational                            S. Gerdes, Ed.
Expires: January 3, 2015                         Universitaet Bremen TZI
                                                             G. Selander
                                                                Ericsson
                                                                 M. Mani
                                                                   Itron
                                                                S. Kumar
                                                        Philips Research
                                                           July 02, 2014

                             ACE use cases
                      draft-seitz-ace-usecases-01

Abstract

   This document presents use cases for authentication and access
   control in scenarios involving constrained RESTful devices.  Where
   specific details are relevant, it is assumed that the devices use
   CoAP as communication protocol, however most conclusions apply
   generally.

   A number of security requirements are derived from the use cases,
   which are intended as a guideline for developing a comprehensive
   authentication and access control approach for this class of
   scenarios.

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 3, 2015.

Copyright Notice

Seitz, et al.            Expires January 3, 2015                [Page 1]
Internet-Draft                ACE use cases                    July 2014

   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
   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.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Use Cases  . . . . . . . . . . . . . . . . . . . . . . . . . .  4
     2.1.  Container monitoring . . . . . . . . . . . . . . . . . . .  4
       2.1.1.  Bananas for Munich . . . . . . . . . . . . . . . . . .  4
       2.1.2.  Requirements . . . . . . . . . . . . . . . . . . . . .  5
     2.2.  Home Automation  . . . . . . . . . . . . . . . . . . . . .  5
       2.2.1.  Remotely letting in a visitor  . . . . . . . . . . . .  6
       2.2.2.  Requirements . . . . . . . . . . . . . . . . . . . . .  6
     2.3.  Personal Health Monitoring . . . . . . . . . . . . . . . .  7
       2.3.1.  John and the heart rate monitor  . . . . . . . . . . .  7
       2.3.2.  Requirements . . . . . . . . . . . . . . . . . . . . .  8
     2.4.  Building Automation  . . . . . . . . . . . . . . . . . . .  9
       2.4.1.  Device Lifecycle . . . . . . . . . . . . . . . . . . .  9
       2.4.2.  Requirements . . . . . . . . . . . . . . . . . . . . . 11
     2.5.  Smart Metering . . . . . . . . . . . . . . . . . . . . . . 12
       2.5.1.  Drive-by metering  . . . . . . . . . . . . . . . . . . 12
       2.5.2.  Meshed Topology  . . . . . . . . . . . . . . . . . . . 13
       2.5.3.  Customer Direct Access to the metering Data  . . . . . 13
       2.5.4.  Requirements . . . . . . . . . . . . . . . . . . . . . 13
   3.  Consolidated Requirements From The Use Cases . . . . . . . . . 14
     3.1.  General Security Requirements  . . . . . . . . . . . . . . 14
     3.2.  Authentication Requirements  . . . . . . . . . . . . . . . 15
     3.3.  Access Control Requirements  . . . . . . . . . . . . . . . 15
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . . 17
   5.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 18
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 19
   7.  Informative References . . . . . . . . . . . . . . . . . . . . 20
Show full document text