draft-ietf-ace-extend-dtls-authorize-00.txt   draft-ietf-ace-extend-dtls-authorize-01.txt 
Network Working Group O. Bergmann Network Working Group O. Bergmann
Internet-Draft TZI Internet-Draft TZI
Updates: draft-ietf-ace-dtls-authorize (if J. Preuß Mattsson Updates: draft-ietf-ace-dtls-authorize (if J. Preuß Mattsson
approved) G. Selander approved) G. Selander
Intended status: Standards Track Ericsson Intended status: Standards Track Ericsson
Expires: 5 June 2022 2 December 2021 Expires: 8 August 2022 4 February 2022
Extension of the ACE CoAP-DTLS Profile to TLS Extension of the ACE CoAP-DTLS Profile to TLS
draft-ietf-ace-extend-dtls-authorize-00 draft-ietf-ace-extend-dtls-authorize-01
Abstract Abstract
This document updates the ACE CoAP-DTLS profile by specifying that This document updates the ACE CoAP-DTLS profile by specifying that
the profile applies to TLS as well as DTLS. the profile applies to TLS as well as DTLS.
Discussion Venues Discussion Venues
This note is to be removed before publishing as an RFC. This note is to be removed before publishing as an RFC.
skipping to change at page 1, line 45 skipping to change at page 1, line 45
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on 5 June 2022. This Internet-Draft will expire on 8 August 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2022 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components and restrictions with respect to this document. Code Components
extracted from this document must include Revised BSD License text as extracted from this document must include Revised BSD License text as
described in Section 4.e of the Trust Legal Provisions and are described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Revised BSD License. provided without warranty as described in the Revised BSD License.
skipping to change at page 2, line 44 skipping to change at page 2, line 44
constrained implementations, CoAP over UDP [RFC7252] is the first constrained implementations, CoAP over UDP [RFC7252] is the first
choice, but when deploying ACE in networks controlled by other choice, but when deploying ACE in networks controlled by other
entities (such as the Internet), UDP might be blocked on the path 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 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 to CoAP over TCP [RFC8323] for NAT or firewall traversal. This
feature is supported by the OSCORE profile feature is supported by the OSCORE profile
[I-D.ietf-ace-oscore-profile] but is lacking from the DTLS 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 This document updates [I-D.ietf-ace-dtls-authorize] by specifying
that the profile applies to TLS as well as DTLS. The same access 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 rights are valid in case transport layer security is either DTLS or
on the transport layer security. TLS, and the same access token can be used.
2. IANA Considerations 2. IANA Considerations
No IANA Considerations. No IANA Considerations.
3. Security Considerations 3. Security Considerations
The security consideration and requirements in TLS 1.3 [RFC8446] and The security consideration and requirements in TLS 1.3 [RFC8446] and
BCP 195 [RFC7525] [RFC8996] also apply to this document. BCP 195 [RFC7525] [RFC8996] also apply to this document.
 End of changes. 5 change blocks. 
6 lines changed or deleted 6 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/