<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-2">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Aptos;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;
mso-ligatures:standardcontextual;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#467886;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#467886" vlink="#96607D" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Spec Call Notes 31-Mar-25<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Aaron Parecki<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Michael Fraser<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Mike Jones<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Takeaways from IETF 122<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> Michael: The Client ID prefix discussions were worthwhile<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> Aaron: I think we'll find a way for everyone to get what they need<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> Aaron: Joseph is worried about situations where URLs can be used in multiple ways<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> We will be discussing Client ID prefixes on the next Connect WG call<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> Mike: Having a clear decision on the rfc7523bis direction was useful<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> Mike and Brian Campbell are working on updating the draft<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> Mike: The ML-DSA private key representation discussion was significant<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> NIST specified two ways of representing private keys for ML-DSA – a “seed” and an “expanded private key”.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> COSE and JOSE had been using only the “seed” representation, because it is more compact.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> But the Lamps working group, which is defining the X.509 certificate representation for ML-DSA, decided to support both representations – in part, because some HSMs are already
in the market that use the expanded private key representation.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> COSE and JOSE are considering following suit.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> Please discuss on the
<a href="mailto:cose@ietf.org">cose@ietf.org</a> mailing list<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Federation Issue <a href="https://github.com/openid/federation/issues/193">
https://github.com/openid/federation/issues/193</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> Concerns around the practicality of the requirement for an empty json object on present entity type identifiers<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> Mike: It's a declaration that the Entity supports the Entity Type<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> Michael: We may want to say that it's OK if the Entity Type appears in the Resolved Metadata<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> Mike asked Michael to add that comment to the issue<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Federation Interop Event<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> Michael and Łukasz Jaromin will both be there in person<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> Michael volunteered to host a test federation that others can join<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> Mike said that we want at least one test federation with multiple Trust Anchors<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
</body>
</html>