[Id-event] Francesca Palombini's No Objection on draft-ietf-secevent-subject-identifiers-16: (with COMMENT)

Francesca Palombini via Datatracker <noreply@ietf.org> Tue, 21 February 2023 14:23 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: id-event@ietf.org
Delivered-To: id-event@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 936ADC14EB19; Tue, 21 Feb 2023 06:23:24 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Francesca Palombini via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-secevent-subject-identifiers@ietf.org, secevent-chairs@ietf.org, id-event@ietf.org, yaronf.ietf@gmail.com, yaronf.ietf@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 9.10.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Francesca Palombini <francesca.palombini@ericsson.com>
Message-ID: <167698940459.38971.13677902202162419802@ietfa.amsl.com>
Date: Tue, 21 Feb 2023 06:23:24 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/6jZpIEdBF3ZXi8Ozj21tL3jMeEA>
Subject: [Id-event] Francesca Palombini's No Objection on draft-ietf-secevent-subject-identifiers-16: (with COMMENT)
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.39
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2023 14:23:24 -0000

Francesca Palombini has entered the following ballot position for
draft-ietf-secevent-subject-identifiers-16: 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/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-secevent-subject-identifiers/



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

Thank you for the work on this document.

Many thanks to Paul Kyzivat for his ART ART review:
https://mailarchive.ietf.org/arch/msg/art/3UoUPXy96ynW4msza41RfQqzsss/. I
haven't seen any answer to Paul's review, which I think gives input for
improvements and clarifications, so I would strongly encourage the authors to
evaluate and respond to Paul's comments. Regarding Paul's 1st comment, I think
that ship has sailed, so I would not insist on any change there.

Additionally, I was surprised to see the following statement in the expert
guidelines:

> In the case where a request is rejected, the Expert Reviewer must provide the
requesting party with a written statement expressing the reason for rejection,
and be prepared to cite any sources of information that went into that decision.

Although I understand wanting to know the reasoning behind a rejection, I would
not formulate this as a formal requirement on the experts.

Francesca