Skip to main content

Extension of the ACE CoAP-DTLS Profile to TLS
draft-ietf-ace-extend-dtls-authorize-00

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 9430.
Authors Olaf Bergmann , John Preuß Mattsson , Göran Selander
Last updated 2021-12-02
RFC stream Internet Engineering Task Force (IETF)
Formats
Reviews
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Became RFC 9430 (Proposed Standard)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)
draft-ietf-ace-extend-dtls-authorize-00
Network Working Group                                        O. Bergmann
Internet-Draft                                                       TZI
Updates: draft-ietf-ace-dtls-authorize (if             J. Preuß Mattsson
         approved)                                           G. Selander
Intended status: Standards Track                                Ericsson
Expires: 5 June 2022                                     2 December 2021

             Extension of the ACE CoAP-DTLS Profile to TLS
                draft-ietf-ace-extend-dtls-authorize-00

Abstract

   This document updates the ACE CoAP-DTLS profile by specifying that
   the profile applies to TLS as well as DTLS.

Discussion Venues

   This note is to be removed before publishing as an RFC.

   Discussion of this document takes place on the Authentication and
   Authorization for Constrained Environments Working Group mailing list
   (ace@ietf.org), which is archived at
   https://mailarchive.ietf.org/arch/browse/ace/.

   Source for this draft and an issue tracker can be found at
   https://github.com/ace-wg/ace-extend-dtls-authorize.

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 5 June 2022.

Bergmann, et al.           Expires 5 June 2022                  [Page 1]
Internet-Draft             CoAP-DTLS Extension             December 2021

Copyright Notice

   Copyright (c) 2021 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 (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 Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   2
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   4.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Normative References  . . . . . . . . . . . . . . . . . .   3
     4.2.  Informative References  . . . . . . . . . . . . . . . . .   3
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   4

1.  Introduction

   [I-D.ietf-ace-dtls-authorize] only specifies use of DTLS
   [I-D.ietf-tls-dtls13] but works equally well for TLS.  For many
   constrained implementations, CoAP over UDP [RFC7252] is the first
   choice, but when deploying ACE in networks controlled by other
   entities (such as the Internet), UDP might be blocked on the path
   between the client and the RS, and the client might have to fall back
   to CoAP over TCP [RFC8323] for NAT or firewall traversal.  This
   feature is supported by the OSCORE profile
   [I-D.ietf-ace-oscore-profile] but is lacking from the DTLS profile.

   This document updates [I-D.ietf-ace-dtls-authorize] by specifying
   that the profile applies to TLS as well as DTLS.  The same access
   token is valid for both DTLS or TLS.  The access rights do not depend
   on the transport layer security.

2.  IANA Considerations

   No IANA Considerations.

Bergmann, et al.           Expires 5 June 2022                  [Page 2]
Internet-Draft             CoAP-DTLS Extension             December 2021

3.  Security Considerations

   The security consideration and requirements in TLS 1.3 [RFC8446] and
   BCP 195 [RFC7525] [RFC8996] also apply to this document.

4.  References

4.1.  Normative References

   [I-D.ietf-ace-dtls-authorize]
              Gerdes, S., Bergmann, O., Bormann, C., Selander, G., and
              L. Seitz, "Datagram Transport Layer Security (DTLS)
              Profile for Authentication and Authorization for
              Constrained Environments (ACE)", Work in Progress,
              Internet-Draft, draft-ietf-ace-dtls-authorize-18, 4 June
              2021, <https://www.ietf.org/archive/id/draft-ietf-ace-
              dtls-authorize-18.txt>.

   [I-D.ietf-tls-dtls13]
              Rescorla, E., Tschofenig, H., and N. Modadugu, "The
              Datagram Transport Layer Security (DTLS) Protocol Version
              1.3", Work in Progress, Internet-Draft, draft-ietf-tls-
              dtls13-43, 30 April 2021, <https://www.ietf.org/internet-
              drafts/draft-ietf-tls-dtls13-43.txt>.

   [RFC7252]  Shelby, Z., Hartke, K., and C. Bormann, "The Constrained
              Application Protocol (CoAP)", RFC 7252,
              DOI 10.17487/RFC7252, June 2014,
              <https://www.rfc-editor.org/info/rfc7252>.

   [RFC8323]  Bormann, C., Lemay, S., Tschofenig, H., Hartke, K.,
              Silverajan, B., and B. Raymor, Ed., "CoAP (Constrained
              Application Protocol) over TCP, TLS, and WebSockets",
              RFC 8323, DOI 10.17487/RFC8323, February 2018,
              <https://www.rfc-editor.org/info/rfc8323>.

   [RFC8446]  Rescorla, E., "The Transport Layer Security (TLS) Protocol
              Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
              <https://www.rfc-editor.org/info/rfc8446>.

4.2.  Informative References

Bergmann, et al.           Expires 5 June 2022                  [Page 3]
Internet-Draft             CoAP-DTLS Extension             December 2021

   [I-D.ietf-ace-oscore-profile]
              Palombini, F., Seitz, L., Selander, G., and M. Gunnarsson,
              "OSCORE Profile of the Authentication and Authorization
              for Constrained Environments Framework", Work in Progress,
              Internet-Draft, draft-ietf-ace-oscore-profile-19, 6 May
              2021, <https://www.ietf.org/archive/id/draft-ietf-ace-
              oscore-profile-19.txt>.

   [RFC7525]  Sheffer, Y., Holz, R., and P. Saint-Andre,
              "Recommendations for Secure Use of Transport Layer
              Security (TLS) and Datagram Transport Layer Security
              (DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525, May
              2015, <https://www.rfc-editor.org/info/rfc7525>.

   [RFC8996]  Moriarty, K. and S. Farrell, "Deprecating TLS 1.0 and TLS
              1.1", BCP 195, RFC 8996, DOI 10.17487/RFC8996, March 2021,
              <https://www.rfc-editor.org/info/rfc8996>.

Acknowledgments

Authors' Addresses

   Olaf Bergmann
   Universität Bremen TZI
   Bremen, D-28359
   Germany

   Email: bergmann@tzi.org

   John Preuß Mattsson
   Ericsson AB
   SE-164 80 Stockholm
   Sweden

   Email: john.mattsson@ericsson.com

   Göran Selander
   Ericsson AB
   SE-164 80 Stockholm
   Sweden

   Email: goran.selander@ericsson.com

Bergmann, et al.           Expires 5 June 2022                  [Page 4]