Access Control Framework for Constrained Environments
draft-selander-core-access-control-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-07-05
Stream (None)
Intended RFC status (None)
Formats pdf htmlized 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 Working Group                                           G. Selander
Internet-Draft                                                  M. Sethi
Intended Status: Standards Track                                Ericsson
Expires: January 6, 2014                                        L. Seitz
                                                        SICS Swedish ICT
                                                            July 5, 2013

         Access Control Framework for Constrained Environments 
                 draft-selander-core-access-control-00

Abstract

   The Constrained Application Protocol (CoAP) is a light-weight web
   transfer protocol designed to be used in constrained nodes and
   constrained networks.  Communication security support for CoAP,
   including authentication, encryption, integrity protection, is well
   understood and a DTLS binding for CoAP is specified, but
   authorization and access control are not described in detail. 

   This document describes a generic and dynamic access control
   framework suitable for constrained environments using CoAP.  The
   framework builds on standards and well known paradigms for access
   control, externalizing authorization decision making to unconstrained
   nodes while performing authorization decision enforcement and
   verification of local conditions in constrained devices.

   In addition, this document provides alternative or complementary key
   management to the CoAP security modes.

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   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".

   The list of current Internet-Drafts can be accessed at
 

<Author>                Expires January 6, 2014                 [Page 1]
INTERNET DRAFT              <Document Title>                July 5, 2013

   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

Copyright and License Notice

   Copyright (c) 2013 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 . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1  Terminology . . . . . . . . . . . . . . . . . . . . . . . .  5
   2.  Requirements, rationale and outline  . . . . . . . . . . . . .  5
     2.1  Requirements  . . . . . . . . . . . . . . . . . . . . . . .  5
     2.2  Rationale . . . . . . . . . . . . . . . . . . . . . . . . .  6
     2.3  Outline of Access Control Framework . . . . . . . . . . . .  8
   3.  Roles  . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     3.1  Resource Owner  . . . . . . . . . . . . . . . . . . . . . . 10
     3.2  Authorization Server  . . . . . . . . . . . . . . . . . . . 10
     3.3  Client  . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     3.4  Resource Server . . . . . . . . . . . . . . . . . . . . . . 11
   4.  Assertion profiles . . . . . . . . . . . . . . . . . . . . . . 12
     4.1  Assertion requirements  . . . . . . . . . . . . . . . . . . 12
     4.2  Assertion wrapping  . . . . . . . . . . . . . . . . . . . . 13
     4.3  Assertion transport . . . . . . . . . . . . . . . . . . . . 13
   5. Message protection profiles . . . . . . . . . . . . . . . . . . 14
     5.1  Communication security profile  . . . . . . . . . . . . . . 14
       5.1.1 Assertion caching in resource server (informational) . . 15
     5.2  Object security profile . . . . . . . . . . . . . . . . . . 16
       5.2.1 GET  . . . . . . . . . . . . . . . . . . . . . . . . . . 17
       5.2.2 PUT/POST . . . . . . . . . . . . . . . . . . . . . . . . 17
       5.2.3 DELETE . . . . . . . . . . . . . . . . . . . . . . . . . 18
       5.2.4 Assertion replay protection (informational)  . . . . . . 18
 

<Author>                Expires January 6, 2014                 [Page 2]
Show full document text