| Internet-Draft | CoAP-DTLS Extension | December 2021 |
| Bergmann, et al. | Expires 5 June 2022 | [Page] |
This document updates the ACE CoAP-DTLS profile by specifying that the profile applies to TLS as well as DTLS.¶
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.¶
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.¶
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.¶
[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.¶
No IANA Considerations.¶
The security consideration and requirements in TLS 1.3 [RFC8446] and BCP 195 [RFC7525] [RFC8996] also apply to this document.¶