<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DNS on Control Plane by Karl McGuinness</title><link>https://notes.karlmcguinness.com/tags/dns/</link><description>Recent content in DNS on Control Plane by Karl McGuinness</description><generator>Hugo</generator><language>en-us</language><managingEditor>public@karlmcguinness.com (Karl McGuinness)</managingEditor><webMaster>public@karlmcguinness.com (Karl McGuinness)</webMaster><lastBuildDate>Wed, 03 Jun 2026 14:00:00 -0700</lastBuildDate><atom:link href="https://notes.karlmcguinness.com/tags/dns/index.xml" rel="self" type="application/rss+xml"/><item><title>Trusting Issuers in Open-World OAuth</title><link>https://notes.karlmcguinness.com/notes/trusting-issuers-in-open-world-oauth/</link><pubDate>Wed, 03 Jun 2026 14:00:00 -0700</pubDate><author>public@karlmcguinness.com (Karl McGuinness)</author><guid>https://notes.karlmcguinness.com/notes/trusting-issuers-in-open-world-oauth/</guid><description>Self-service agent sign-up surfaces a first-contact trust problem. A Resource Authorization Server can verify a JWT and still not know whether the issuer is allowed to assert identities for the subject&amp;rsquo;s domain. Federation proves issuer authenticity, not namespace authority. Static allowlists do not scale to runtime onboarding. The Identity Assertion Trust Framework lets a Resource AS publish the evidence it requires, while Domain-Authorized Issuer Discovery lets a domain owner publish which issuers may assert identities in its namespace. Together they compose with ID-JAG and JWT-bearer grants without changing the grant surface.</description></item></channel></rss>