OSCORE profile of the Authentication and Authorization for Constrained Environments Framework
draft-ietf-ace-oscore-profile-03
ACE Working Group L. Seitz
Internet-Draft RISE SICS AB
Intended status: Standards Track F. Palombini
Expires: April 4, 2019 Ericsson AB
M. Gunnarsson
RISE SICS AB
G. Selander
Ericsson AB
October 1, 2018
OSCORE profile of the Authentication and Authorization for Constrained
Environments Framework
draft-ietf-ace-oscore-profile-03
Abstract
This memo specifies a profile for the Authentication and
Authorization for Constrained Environments (ACE) framework. It
utilizes Object Security for Constrained RESTful Environments
(OSCORE) to provide communication security, server authentication,
and proof-of-possession for a key owned by the client and bound to an
OAuth 2.0 access token.
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 https://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 April 4, 2019.
Copyright Notice
Copyright (c) 2018 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
Seitz, et al. Expires April 4, 2019 [Page 1]
Internet-Draft OSCORE Profile of ACE October 2018
(https://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 . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. Protocol Overview . . . . . . . . . . . . . . . . . . . . . . 3
3. Client-AS Communication . . . . . . . . . . . . . . . . . . . 5
3.1. C-to-AS: POST /token . . . . . . . . . . . . . . . . . . 5
3.2. AS-to-C: Access Token . . . . . . . . . . . . . . . . . . 6
4. Client-RS Communication . . . . . . . . . . . . . . . . . . . 11
4.1. C-to-RS: POST /authz-info . . . . . . . . . . . . . . . . 11
4.2. RS-to-C: 2.01 (Created) . . . . . . . . . . . . . . . . . 11
4.3. OSCORE Setup . . . . . . . . . . . . . . . . . . . . . . 12
4.4. Access rights verification . . . . . . . . . . . . . . . 13
5. Secure Communication with AS . . . . . . . . . . . . . . . . 14
6. Security Considerations . . . . . . . . . . . . . . . . . . . 14
7. Privacy Considerations . . . . . . . . . . . . . . . . . . . 15
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
9.1. Normative References . . . . . . . . . . . . . . . . . . 16
9.2. Informative References . . . . . . . . . . . . . . . . . 17
Appendix A. Profile Requirements . . . . . . . . . . . . . . . . 17
Appendix B. Using the pop-key with EDHOC (EDHOC+OSCORE) . . . . 18
B.1. Using Asymmetric Keys . . . . . . . . . . . . . . . . . . 18
B.2. Using Symmetric Keys . . . . . . . . . . . . . . . . . . 20
B.3. Processing . . . . . . . . . . . . . . . . . . . . . . . 22
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24
1. Introduction
This memo specifies a profile of the ACE framework
[I-D.ietf-ace-oauth-authz]. In this profile, a client and a resource
server use CoAP [RFC7252] to communicate. The client uses an access
token, bound to a key (the proof-of-possession key) to authorize its
access to the resource server. In order to provide communication
security, proof of possession, and server authentication they use
Show full document text