[lamps] Re: WGLC for draft-ietf-lamps-private-key-stmt-attr

[Mike Ounsworth <[e-mail]>]

Tim,

I agree with your summary; these are reasonable questions to ask about using these mechanisms, but these considerations don't belong in the RFC. Ship it.

---
Mike Ounsworth
________________________________
From: Tim Hollebeek <tim.hollebeek=[e-mail]>
Sent: Tuesday, April 29, 2025 12:24:26 PM
To: SPASM <[e-mail]>
Subject: [EXTERNAL] [lamps] Re: WGLC for draft-ietf-lamps-private-key-stmt-attr


After reviewing the discussion a few times, the consensus appears to be to move forward with this draft. As to the discussion which ensued,



  1.  It is a matter of policy whether proof of this kind is accepted by an ecosystem
  2.  If such an ecosystem chooses to accept such proofs, there are reasonable considerations that need to be made about what to do errors are later found with that evidence
  3.  Those questions are largely about the ecosystem’s certificate policies, and not about this RFC, whose scope is the technical description of the attribute and how it can be used
  4.  Specifying a single mechanism and/or specific policy requirements would constrain ecosystem designers in unhelpful ways



The draft RFC, with Russ’s recent updates, already covers all these points so we have no further work to do here.



I’ll start the process of getting the Shepherd writeup written.



-Tim



From: Tim Hollebeek
Sent: Tuesday, March 25, 2025 3:14 PM
To: SPASM <[e-mail]>
Subject: WGLC for draft-ietf-lamps-private-key-stmt-attr



This is the working group last call for draft-lamps-private-key-stmt-attr:



“An Attribute for Statement of Possession of a Private Key”



https://datatracker.ietf.org/doc/draft-ietf-lamps-private-key-stmt-attr



Please post comments to the list by 8 April 2025.



-Tim



Any email and files/attachments transmitted with it are intended solely for the use of the individual or entity to whom they are addressed. If this message has been sent to you in error, you must not copy, distribute or disclose of the information it contains. Please notify Entrust immediately and delete the message from your system.