[Ace] Martin Duke's No Objection on draft-ietf-ace-oscore-profile-17: (with COMMENT)

Martin Duke via Datatracker <noreply@ietf.org> Fri, 19 March 2021 22:39 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 DF9723A1295; Fri, 19 Mar 2021 15:39:31 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Martin Duke via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-ace-oscore-profile@ietf.org, ace-chairs@ietf.org, ace@ietf.org, Jim Schaad <ietf@augustcellars.com>, ietf@augustcellars.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.27.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Martin Duke <martin.h.duke@gmail.com>
Message-ID: <161619357138.21782.3555422752704211953@ietfa.amsl.com>
Date: Fri, 19 Mar 2021 15:39:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/T0yl5KayxwdEloSxSRaXBqzGfPw>
Subject: [Ace] Martin Duke's No Objection on draft-ietf-ace-oscore-profile-17: (with COMMENT)
X-BeenThere: ace@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 19 Mar 2021 22:39:32 -0000

Martin Duke has entered the following ballot position for
draft-ietf-ace-oscore-profile-17: No Objection

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/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.

The document, along with other ballot positions, can be found here:


Sec 4.1. I don't understand how the OSCORE security context is secure. In Sec
4.1 it says the C-RS communications need not be protected. But the context is
fully derived from parameters that go back and forth over this channel. Why
can't an observer simply compute the OSCORE keys?