An architecture for authorization in constrained environments
draft-ietf-ace-actors-01

The information below is for an old version of the document
Document Type Active Internet-Draft (ace WG)
Last updated 2015-09-29
Replaces draft-seitz-ace-problem-description
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
ACE Working Group                                              S. Gerdes
Internet-Draft                                   Universitaet Bremen TZI
Intended status: Informational                                  L. Seitz
Expires: March 31, 2016                              SICS Swedish ICT AB
                                                             G. Selander
                                                                Ericsson
                                                         C. Bormann, Ed.
                                                 Universitaet Bremen TZI
                                                      September 28, 2015

     An architecture for authorization in constrained environments
                        draft-ietf-ace-actors-01

Abstract

   Constrained-node networks are networks where some nodes have severe
   constraints on code size, state memory, processing capabilities, user
   interface, power and communication bandwidth (RFC 7228).

   This document provides terminology, and identifies the elements that
   an architecture needs to address, providing a problem statement, for
   authentication and authorization in these networks.

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 March 31, 2016.

Copyright Notice

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

Gerdes, et al.           Expires March 31, 2016                 [Page 1]
Internet-Draft                 ace-actors                 September 2015

   (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 . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Architecture and High-level Problem Statement . . . . . . . .   5
     2.1.  Elements of an Architecture . . . . . . . . . . . . . . .   5
     2.2.  Architecture Variants . . . . . . . . . . . . . . . . . .   8
     2.3.  Information flows . . . . . . . . . . . . . . . . . . . .  11
     2.4.  Problem statement . . . . . . . . . . . . . . . . . . . .  12
   3.  Security Objectives . . . . . . . . . . . . . . . . . . . . .  12
     3.1.  End-to-End Security Objectives  . . . . . . . . . . . . .  13
   4.  Authentication and Authorization  . . . . . . . . . . . . . .  13
   5.  Actors and their Tasks  . . . . . . . . . . . . . . . . . . .  15
     5.1.  Constrained Level Actors  . . . . . . . . . . . . . . . .  16
     5.2.  Principal Level Actors  . . . . . . . . . . . . . . . . .  17
     5.3.  Less-Constrained Level Actors . . . . . . . . . . . . . .  17
   6.  Kinds of Protocols  . . . . . . . . . . . . . . . . . . . . .  18
     6.1.  Constrained Level Protocols . . . . . . . . . . . . . . .  18
       6.1.1.  Cross Level Support Protocols . . . . . . . . . . . .  19
     6.2.  Less-Constrained Level Protocols  . . . . . . . . . . . .  19
   7.  Elements of a Solution  . . . . . . . . . . . . . . . . . . .  19
     7.1.  Authorization . . . . . . . . . . . . . . . . . . . . . .  19
     7.2.  Authentication  . . . . . . . . . . . . . . . . . . . . .  20
     7.3.  Communication Security  . . . . . . . . . . . . . . . . .  20
     7.4.  Cryptographic Keys  . . . . . . . . . . . . . . . . . . .  21
   8.  Assumptions and Requirements  . . . . . . . . . . . . . . . .  22
     8.1.  Architecture  . . . . . . . . . . . . . . . . . . . . . .  22
     8.2.  Constrained Devices . . . . . . . . . . . . . . . . . . .  22
     8.3.  Authentication  . . . . . . . . . . . . . . . . . . . . .  23
     8.4.  Server-side Authorization . . . . . . . . . . . . . . . .  24
     8.5.  Client-side Authorization Information . . . . . . . . . .  24
     8.6.  Server-side Authorization Information . . . . . . . . . .  24
     8.7.  Resource Access . . . . . . . . . . . . . . . . . . . . .  25
Show full document text