<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=utf-8">
<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;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#002060;}
.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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060">I’ll note that the “events” syntax below is based on Phil Hunt’s ID Events proposal, which William has been working on with him. See the id-event mailing list
for more details. The announcement of the id-event mailing list is at <a href="http://www.ietf.org/mail-archive/web/ietf-announce/current/msg14839.html">
http://www.ietf.org/mail-archive/web/ietf-announce/current/msg14839.html</a>.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060"> -- Mike<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060"><o:p> </o:p></span></a></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Openid-specs-ab [mailto:openid-specs-ab-bounces@lists.openid.net]
<b>On Behalf Of </b>William Denniss<br>
<b>Sent:</b> Thursday, April 7, 2016 6:46 PM<br>
<b>To:</b> openid-specs-ab@lists.openid.net<br>
<b>Subject:</b> [Openid-specs-ab] Back-Channel Logout Token Proposal<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">I had a discussion with Mike, John and Nat about event JWT formats at IETF95, specifically as they relate to the Back-Channel Logout spec.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Here is an example of what the Back-Channel Logout Token could look like with an extensible event treatment:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> {<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> "iss": "<a href="https://server.example.com">https://server.example.com</a>",<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> "aud": "s6BhdRkqt3",<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> "jti": "3d0c3cf797584bd193bd0fb1bd4e7d30",<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> "sub": "248289761001",<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> "iat": 1458668180,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> "exp": 1458668580,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> "events": [<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> "<a href="https://specs.openid.net/logout">https://specs.openid.net/logout</a>"<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> ],<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> "<a href="https://specs.openid.net/logout">https://specs.openid.net/logout</a>": {<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> "sid": "08a5019c-17e1-4977-8f42-65a12843ea02"<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> }<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> }<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The proposed change is replacing the "logout_only" claim in the
<a href="http://openid.net/specs/openid-connect-backchannel-1_0.html#LogoutToken">
current draft</a> with an "events" claim, a list of event type URI references. Each of these event type URIs is also a claim of its own, containing the event-specific attributes. The Back-Channel Logout spec would register just 1 event type: "<a href="https://specs.openid.net/logout">https://specs.openid.net/logout</a>",
and the "sid" attribute would move to the logout attribute group.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>