<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: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=us-ascii">
<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:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Spec Call Notes 26-Jun-23<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Nat Sakimura<o:p></o:p></p>
<p class="MsoNormal">Giuseppe De Marco<o:p></o:p></p>
<p class="MsoNormal">Vittorio Bertocci<o:p></o:p></p>
<p class="MsoNormal">Mike Jones<o:p></o:p></p>
<p class="MsoNormal">Kosuke Koiwai<o:p></o:p></p>
<p class="MsoNormal">Naveen CM<o:p></o:p></p>
<p class="MsoNormal">David Waite<o:p></o:p></p>
<p class="MsoNormal">Edmund Jay<o:p></o:p></p>
<p class="MsoNormal">Dima Postnikov<o:p></o:p></p>
<p class="MsoNormal">Aaron Parecki<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Events<o:p></o:p></p>
<p class="MsoNormal"> OAuth Security Workshop<o:p></o:p></p>
<p class="MsoNormal"> <a href="https://oauth.secworkshop.events/osw2023">
https://oauth.secworkshop.events/osw2023</a><o:p></o:p></p>
<p class="MsoNormal"> The workshop will be August 22-24 in London<o:p></o:p></p>
<p class="MsoNormal"> The proposal submission deadline is Sunday, July 2<o:p></o:p></p>
<p class="MsoNormal"> IETF 117 San Francisco<o:p></o:p></p>
<p class="MsoNormal"> <a href="https://www.ietf.org/how/meetings/117/">
https://www.ietf.org/how/meetings/117/</a><o:p></o:p></p>
<p class="MsoNormal"> The draft submission deadline is Monday, July 10<o:p></o:p></p>
<p class="MsoNormal"> NIST is hosting a meeting about SP 800-63<o:p></o:p></p>
<p class="MsoNormal"> <a href="https://www.nccoe.nist.gov/get-involved/attend-events/digital-identity-whats-next-nist">
https://www.nccoe.nist.gov/get-involved/attend-events/digital-identity-whats-next-nist</a><o:p></o:p></p>
<p class="MsoNormal"> It is July 25-26 (overlapping IETF) in Washington DC and virtually<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Display Types<o:p></o:p></p>
<p class="MsoNormal"> Mike published a call for adoption on June 12th, the deadline for which was today<o:p></o:p></p>
<p class="MsoNormal"> On the list, three people spoke in favor of adoption and Aaron Parecki opposed adoption<o:p></o:p></p>
<p class="MsoNormal"> On the call Vittorio said that he thought more motivation for the draft would be needed<o:p></o:p></p>
<p class="MsoNormal"> Vittorio said that Facebook Connect used to have similar parameters, which could result in confusion<o:p></o:p></p>
<p class="MsoNormal"> The user agent string and the parameter can provide conflicting information<o:p></o:p></p>
<p class="MsoNormal"> For instance, the display might be a TV or a mobile phone<o:p></o:p></p>
<p class="MsoNormal"> On the call, David Waite said that the only display value he's seen in the wild is "popup"<o:p></o:p></p>
<p class="MsoNormal"> He said that we can already tell what kind of content to provide via the accept header<o:p></o:p></p>
<p class="MsoNormal"> Vittorio said that "popup" has different security characteristics<o:p></o:p></p>
<p class="MsoNormal"> Kosuke said that he didn't have a stronger counterargument about the criticisms<o:p></o:p></p>
<p class="MsoNormal"> Kosuke explained that, yes, you might be able to tell that a device is a TV from the user agent string<o:p></o:p></p>
<p class="MsoNormal"> but that there aren't standards for knowing that a device is a TV in that way<o:p></o:p></p>
<p class="MsoNormal"> Kosuke said that TVs may have looser security requirements than some other devices<o:p></o:p></p>
<p class="MsoNormal"> Vittorio suggested that we ask the W3C about adding information to the user agent string<o:p></o:p></p>
<p class="MsoNormal"> saying that the device is a TV or has limited input capabilities<o:p></o:p></p>
<p class="MsoNormal"> Vittorio said that making something a standard requires that it has particular characteristics<o:p></o:p></p>
<p class="MsoNormal"> That it be enforceable, that there be demand for it<o:p></o:p></p>
<p class="MsoNormal"> He doesn't feel that it's a good candidate for standardization but he won't speak against it if it is adopted<o:p></o:p></p>
<p class="MsoNormal"> DW said that he doesn't see much use of the display parameter<o:p></o:p></p>
<p class="MsoNormal"> He said that just knowing it's a TV doesn't tell the OP what behaviors it can count on<o:p></o:p></p>
<p class="MsoNormal"> In most cases, he wouldn't know what actions to take based on the display parameter<o:p></o:p></p>
<p class="MsoNormal"> Nat wondered whether knowing more, such as 1024x768 display size, might be useful<o:p></o:p></p>
<p class="MsoNormal"> DW said that by the time the OP got a request, it could already tell, for instance, that the device wanted WEP content<o:p></o:p></p>
<p class="MsoNormal"> He said that he wouldn't know what to do if he received display=tv<o:p></o:p></p>
<p class="MsoNormal"> He'd like to know what user experiences should be triggered by the parameter<o:p></o:p></p>
<p class="MsoNormal"> Kosuke said that he can go back to the TV people and ask them what kinds of actions they want the parameter to trigger<o:p></o:p></p>
<p class="MsoNormal"> Nat agreed that having that data would be useful<o:p></o:p></p>
<p class="MsoNormal"> Mike concluded that we will discuss possible adoption again once we have considered the additional data<o:p></o:p></p>
<p class="MsoNormal"> Later in the call, Aaron joined<o:p></o:p></p>
<p class="MsoNormal"> He was curious if there are things that can't be learned from the invoking environment that are useful<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Trust Chain CBOR Header Parameter<o:p></o:p></p>
<p class="MsoNormal"> Giuseppe plans to propose a Trust Chain COSE Header Parameter<o:p></o:p></p>
<p class="MsoNormal"> <a href="https://github.com/peppelinux/cose-sign-header-openid-federation-trust-chain/blob/master/draft-cose-sign--header-trust-chain.md">
https://github.com/peppelinux/cose-sign-header-openid-federation-trust-chain/blob/master/draft-cose-sign--header-trust-chain.md</a><o:p></o:p></p>
<p class="MsoNormal"> Mike owes Giuseppe feedback on his draft<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">PRs<o:p></o:p></p>
<p class="MsoNormal"> <a href="https://bitbucket.org/openid/connect/pull-requests/">
https://bitbucket.org/openid/connect/pull-requests/</a><o:p></o:p></p>
<p class="MsoNormal"> PR #529: Added support for trust mark delegation.<o:p></o:p></p>
<p class="MsoNormal"> Giuseppe gave the example of vehicle inspection, where the body mandating the inspection isn't the one doing it<o:p></o:p></p>
<p class="MsoNormal"> There are currently two approvals<o:p></o:p></p>
<p class="MsoNormal"> More reviews are requested<o:p></o:p></p>
<p class="MsoNormal"> PR #507: feat: [Federation] added iat and exp in trust marked endpoint<o:p></o:p></p>
<p class="MsoNormal"> Unless a reason to keep working on this is stated before then,<o:p></o:p></p>
<p class="MsoNormal"> we’ll plan to close this during the Federation editors' call on Friday<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Open Issues<o:p></o:p></p>
<p class="MsoNormal"> <a href="https://bitbucket.org/openid/connect/issues?status=new&status=open">
https://bitbucket.org/openid/connect/issues?status=new&status=open</a><o:p></o:p></p>
<p class="MsoNormal"> #1752: Core - 15.5.3 CSRF Attack on Fragment Response Example<o:p></o:p></p>
<p class="MsoNormal"> Adam Strickland responded with a new comment<o:p></o:p></p>
<p class="MsoNormal"> Mike said that he still isn't clear to him what specifically to do to address Adam's concern<o:p></o:p></p>
<p class="MsoNormal"> Mike will ask for specifics in an issue comment<o:p></o:p></p>
<p class="MsoNormal"> #1958: invalid_or_missing_proof and invalid_proof<o:p></o:p></p>
<p class="MsoNormal"> Nat tagged the issue with the component Credential Issuance<o:p></o:p></p>
<p class="MsoNormal"> #1955: [Federation] Policy language: disambiguation about subset_of and essential operators<o:p></o:p></p>
<p class="MsoNormal"> We will discuss possibly adding the requested table during Friday's Federation editors' call<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Next Call<o:p></o:p></p>
<p class="MsoNormal"> The next call will be Thursday, June 29 at 7am Pacific Time<o:p></o:p></p>
</div>
</body>
</html>