<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Brian,</div><div><br></div><div>I've reviewed the draft at <a href="https://dickhardt.github.io/openid-key-binding/main.html">https://dickhardt.github.io/openid-key-binding/main.html</a> and cannot find the RFC 7549 reference you described. The document does not contain a reference to "The OAuth 2.0 Authorization Framework: Bearer Token Usage" or RFC 6750, nor does it cite RFC 7549.</div><div>If you're looking at a different version or document, please clarify. Otherwise, I'm unclear what specific error you're referring to.<br><br>If you have substantive technical concerns about the proposal, I'm happy to address them. The working group's time is best spent on technical merit rather than formatting.</div><div><br></div><div>/Dick</div></div></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Thu, Oct 9, 2025 at 5:38 AM Brian Campbell <<a href="mailto:bcampbell@pingidentity.com">bcampbell@pingidentity.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Dick,</div><div><br></div><div>Your message comes across as unnecessarily sarcastic and disrespectful, even by my threshold for such things, and I believe it is entirely inappropriate. I have raised code of conduct concerns with OIDF's Executive Director about this message (Gail and a few others are copied here too to put in on record) but also a larger pattern of behavior towards me and other participants.</div><div><br></div><div>For the record, the issues I noted previously were not limited to unresolved references or mistakes in indentation. The draft, and more importantly, how it has been brought to the working group, also has substantive problems that go well beyond formatting. Those were simply the easiest things to demonstrate concretely. Even there, though, they point to deeper problems.</div><div><br></div><div>As just one example, there was a reference to the title "The OAuth 2.0
Authorization Framework: Bearer Token Usage," which is the same as the
title of RFC 6750, which was ostensibly co-authored by you. But it was
cited as RFC 7549, which is the entirely unrelated "3GPP SIP URI Inter-Operator Traffic Leg Parameter", and lists a
group of authors not on either RFC 7549 or 6750. I can venture some
guesses as to what happened there but it's really immaterial.</div><div><br></div><div>The larger concern is that it is, at least to me, highly disrespectful to present something with such a significant number of issues - and even more so when the substance is potentially controversial, prone to misunderstanding, or overlapping with existing work - compounded by dismissive and at times insulting engagement when met with disagreement.</div><div><br></div><div>I’d like to see us get back to a place where discussions here are constructive and focused on improving the work and output of the entire working group and foundation itself, even when there’s disagreement. That requires both technical rigor, basic respect, honesty and integrity. I hope we can move forward on that basis. Proceeding with adoption of this as currently presented is not that, however.</div><div></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Oct 3, 2025 at 8:46 AM Dick Hardt <<a href="mailto:dick.hardt@gmail.com" rel="noreferrer" target="_blank">dick.hardt@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">Hi Brian, my sincere apologies for the inconvenience of the references not resolving and mistakes in indentation -- that must have been very distracting when reading the text. Thank you for not pointing out the issues previously, as they existed in the earlier draft, that would have been very embarrassing. I appreciate your thoughtful response on how to resolve this. It is such a pleasure working with you -- having you participate in this WG is such a delight!<br><br>With your expert guidance I have resolved the issues you pointed out so that no one else has to suffer the way you did. Others can find the updated draft at:<br><br><a href="https://dickhardt.github.io/openid-key-binding/main.html" rel="noreferrer" target="_blank">https://dickhardt.github.io/openid-key-binding/main.html</a><br><br><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Oct 2, 2025 at 10:12 PM Brian Campbell via Openid-specs-ab <<a href="mailto:openid-specs-ab@lists.openid.net" rel="noreferrer" target="_blank">openid-specs-ab@lists.openid.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>As I said on the WG call earlier today, I believe it would be appropriate for a baseline level of document hygiene/quality to be in place before the individuals in the WG are asked to invest time looking at a draft, let alone considering adoption of something. Mistakes happen, of course, but I, for one, would really appreciate not having the feeling that something wasn't even looked over before it was posted/submitted. Screenshot snippets of a few examples of problematic areas of the draft are below. It's certainly not an exhaustive list though. Nor is this my only concern with the work. </div><div><br></div><div><br></div><div><img src="cid:ii_mg9gmi4u0" alt="Screenshot 2025-10-02 at 7.17.44 AM.png" width="571" height="66" style="margin-right: 0px;"></div><div><br></div><div><img src="cid:ii_mg9w8pbt2" alt="Screenshot 2025-10-02 at 2.50.49 PM.png" width="584" height="84" style="margin-right: 0px;"></div><div><br><img src="cid:ii_mg9gmljc1" alt="Screenshot 2025-10-02 at 7.18.12 AM.png" width="589" height="115" style="margin-right: 0px;"><br><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Oct 2, 2025 at 6:45 AM Michael Jones via Openid-specs-ab <<a href="mailto:openid-specs-ab@lists.openid.net" rel="noreferrer" target="_blank">openid-specs-ab@lists.openid.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<div lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size:11pt">Responding to feedback from the initial call for adoption, the authors of the OpenID Connect Key Binding specification revised it to clear up potential misunderstandings of what the draft does and doesn't
do. The revised specification was submitted to the working group for consideration in the message
<a href="https://lists.openid.net/pipermail/openid-specs-ab/2025-October/011023.html" rel="noreferrer" target="_blank">
https://lists.openid.net/pipermail/openid-specs-ab/2025-October/011023.html</a>.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">This message starts a one-week call for adoption for the revised specification, ending on Thursday, October 9<sup>th</sup>. Even if you responded to the initial call for adoption, please reply to this one
stating your views.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"> Thank you,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"> -- Mike (writing as a Connect WG chair)<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
</div>
</div>
_______________________________________________<br>
Openid-specs-ab mailing list<br>
<a href="mailto:Openid-specs-ab@lists.openid.net" rel="noreferrer" target="_blank">Openid-specs-ab@lists.openid.net</a><br>
<a href="https://lists.openid.net/mailman/listinfo/openid-specs-ab" rel="noreferrer noreferrer" target="_blank">https://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br>
</div></blockquote></div>
<br>
<i style="margin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseline;background:rgb(255,255,255);font-family:proxima-nova-zendesk,system-ui,-apple-system,system-ui,"Segoe UI",Roboto,Oxygen-Sans,Ubuntu,Cantarell,"Helvetica Neue",Arial,sans-serif;color:rgb(85,85,85)"><span style="margin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseline;background:transparent;font-family:proxima-nova-zendesk,system-ui,-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Oxygen-Sans,Ubuntu,Cantarell,"Helvetica Neue",Arial,sans-serif;font-weight:600"><font size="2">CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you have received this communication in error, please notify the sender immediately by e-mail and delete the message and any file attachments from your computer. Thank you.</font></span></i>_______________________________________________<br>
Openid-specs-ab mailing list<br>
<a href="mailto:Openid-specs-ab@lists.openid.net" rel="noreferrer" target="_blank">Openid-specs-ab@lists.openid.net</a><br>
<a href="https://lists.openid.net/mailman/listinfo/openid-specs-ab" rel="noreferrer noreferrer" target="_blank">https://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br>
</blockquote></div>
</blockquote></div></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div></div>
<br>
<i style="margin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseline;background:rgb(255,255,255);font-family:proxima-nova-zendesk,system-ui,-apple-system,system-ui,"Segoe UI",Roboto,Oxygen-Sans,Ubuntu,Cantarell,"Helvetica Neue",Arial,sans-serif;color:rgb(85,85,85)"><span style="margin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseline;background:transparent;font-family:proxima-nova-zendesk,system-ui,-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Oxygen-Sans,Ubuntu,Cantarell,"Helvetica Neue",Arial,sans-serif;font-weight:600"><font size="2">CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you have received this communication in error, please notify the sender immediately by e-mail and delete the message and any file attachments from your computer. Thank you.</font></span></i></blockquote></div></div>