[Ace] Paul Wouters' Yes on draft-ietf-ace-extend-dtls-authorize-06: (with COMMENT)

Paul Wouters via Datatracker <noreply@ietf.org> Tue, 14 February 2023 20:28 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: ace@ietf.org
Delivered-To: ace@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B572C187986; Tue, 14 Feb 2023 12:28:41 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Paul Wouters via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-ace-extend-dtls-authorize@ietf.org, ace-chairs@ietf.org, ace@ietf.org, mglt.ietf@gmail.com, mglt.ietf@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 9.9.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Paul Wouters <paul.wouters@aiven.io>
Message-ID: <167640652110.15369.7644980750130585810@ietfa.amsl.com>
Date: Tue, 14 Feb 2023 12:28:41 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/pTwKlRxsCXmvaPoxwqf8nkiftrQ>
Subject: [Ace] Paul Wouters' Yes on draft-ietf-ace-extend-dtls-authorize-06: (with COMMENT)
X-BeenThere: ace@ietf.org
X-Mailman-Version: 2.1.39
List-Id: "Authentication and Authorization for Constrained Environments \(ace\)" <ace.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ace>, <mailto:ace-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ace/>
List-Post: <mailto:ace@ietf.org>
List-Help: <mailto:ace-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ace>, <mailto:ace-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2023 20:28:41 -0000

Paul Wouters has entered the following ballot position for
draft-ietf-ace-extend-dtls-authorize-06: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-ace-extend-dtls-authorize/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I also have a but of trouble interpreting this sentence:

    As resource-constrained devices are not expected to support both transport
    layer security mechanisms. Clients and Resource Servers SHOULD support DTLS
    and MAY support TLS. A Client that implements either TLS or DTLS but not
    both might fail in establishing a secure communication channel with the
    Resource Server altogether.

I am assuming the Resource Servers(RS) are not constrained. Would it not make
sense to say that RS SHOULD support both TLS and DTLS to ensure
interoperability with resource-constrained clients that support either TLS or
DTLS but not both ?