[OAUTH-WG] Re: New draft: Presenting Issuer-Signed JWT Credentials to Resource Servers with DPoP

Jijie Wei <pki@varwof.com> Wed, 07 October 2026 14:29 UTC

Received: from smtpbgeu2.qq.com (smtpbgeu2.qq.com [18.194.254.142]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id EF3F53F for <oauth@ietf.org>; Wed, 07 Oct 2026 14:29:53 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=none; spf=pass (mx.ietf.org: domain of pki@varwof.com designates 18.194.254.142 as permitted sender) smtp.mailfrom=pki@varwof.com; dmarc=none
EX-QQ-RecipientCnt: 2
X-QQ-GoodBg: 2
X-QQ-SSF: 00400000000000F0
X-QQ-FEAT: D4aqtcRDiqTOUTwKUmpbOFu19RZU8ZIl/AuaV9DVT4I=
X-QQ-BUSINESS-ORIGIN: 2
X-QQ-Originating-IP: E1Fam4GCJxKQBX/3VetBvEaFVXxGWK+C6fRVpImTJEU=
X-Originating-IP: 36.34.49.117
X-QQ-STYLE:
X-QQ-mid: lv2sz3b-0t1791383386t687c5e6e
From: Jijie Wei <pki@varwof.com>
To: oauth <oauth@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Date: Wed, 07 Oct 2026 22:29:46 +0800
X-Priority: 3
Message-ID: <tencent_11695B223271F8A412CF356A@qq.com>
X-QQ-MIME: TCMime 1.0 by Tencent
X-Mailer: QQMail 2.x
X-QQ-Mailer: QQMail 2.x
X-BIZMAIL-ID: 14932612214219472758
X-Address-Ticket: version=;type=;ticket_id=;id_list=;display_name=;session_id=;
X-QQ-SENDSIZE: 520
Received: from qq.com (unknown [127.0.0.1]) by smtp.qq.com (ESMTP) with SMTP id ; Wed, 07 Oct 2026 22:29:46 +0800 (CST)
Feedback-ID: lv:varwof.com:qybglogicsvrgz:qybglogicsvrgz5b-1
X-QQ-XMAILINFO: NPhoNcGPHxa8+EUdm8ApCGngNiwnbJC48tesTe//10vxA/RIE4GDq6v2 xdoID7ExShjpx/oeO5gJXXEYe4Xg/g8xPM9o/cwlrteX2PETQmH+Ru4hZpcBLFfcsTJFPLD uCiJ+thFW/sZDczfuzHadvDAqIOB9MQN+WYwlWVpSCAqz/MuJsPXMqUPkoEUXF5+CiX/A3W x+BapEEHiIK/XRiRgQlRfxBuDQEp8fOIwzYfntKkMbxn+zP7NbbU+Hb8I8QLgBLbv+ggFs8 JiLroxYzO1M7xgttr1urIfNfrd45EfUlHYTmiDLXk8VIVWOQQaJS8oiQewz0IXzAY4IOIkF 04NPZtWYWVwNAsgRfa0/MxaMZka1iCyfw7d21+IMV8ydL/L4+aX7ssW0BbyzNVvF9qHf5xc U41MRTO1UxbqSQl96vpEerSQyFzO+gGeU+XQUV1qlcz3AInJ9dMXvrd6bA6/LJuoZy7k+To 3sFJeGpPdl+SMhIHsZUODQy0t6Btm5V+5RO8YTyaL+6PBC39gYBeuzfI529YZMyG2p6iiXr 6lUkKsnzS2axZ4dNkY8sj+8IX035da8Y1lpEksCHZB2ld48MaviDwz6IT3bDbaksN0BOSrU sNE55OrttQsTgglzm9RhDSCAXkZK2pl0Jk/xZQYWjtGdXFzx9eTszG4RjGQzJhTmrxpDkCm iCxteBcCxgI5mPLrYZ9foQQDsEvl59EdT9AHA1Atav7ZgEOu5oQOqML0fmUgspLgeoMjSo+ OJwRg1lGFagGaFHDD3ddUVQBdXS/weBdjX7ojwrB2TjSUUPtGlf2vly5LgulmQFIOGSxQMW nc8USqJOSEwosqt9Hr0fnpnEua3pd6EIreJ+vLOjwnQAOxCTUG7j9CojzSY+s6KnWqqgsOl x8vrld5XdO0fftKpubvVXR5sWT8t7l2HBKWfTc69drGpW6d6+F/ldfrxMjAA1bVL5fwIRMK 73es+jmwcAE2ha0jIY4CFAxkqiICUm8q9s0ZOQKr6+JLNsmrnD2KRCkYGsaeBlCEHlwgfaT 0RKll8pvbamFcHo3skgxNlJg1jc/aM4Y4tcR4sDOfmVZYBXA+NcXhFeKlF5qwfhGiSzjLfa n6Ahjk4KtcXpVVCu7VTqiHqzHOvQYgGbxJzNeyL7ca4XbuaI1gl7X4gSLTYpLemvA==
X-QQ-XMRINFO: MPJ6Tf5t3I/ylTmHUqvI8+Wpn+Gzalws3A==
X-QQ-RECHKSPAM: 0
X-Spamd-Bar: /
Message-ID-Hash: OKXNMGMQCYYYY2TFKRIG3RJED6MZNB23
X-Message-ID-Hash: OKXNMGMQCYYYY2TFKRIG3RJED6MZNB23
X-MailFrom: pki@varwof.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-oauth.ietf.org-0; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: nine01223 <nine01223@naver.com>
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [OAUTH-WG] Re: New draft: Presenting Issuer-Signed JWT Credentials to Resource Servers with DPoP
List-Id: OAUTH WG <oauth.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/hpC5ecJTZg0AOOB42WaqNdb23hE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Owner: <mailto:oauth-owner@ietf.org>
List-Post: <mailto:oauth@ietf.org>
List-Subscribe: <mailto:oauth-join@ietf.org>
List-Unsubscribe: <mailto:oauth-leave@ietf.org>

Su-hyeon,

On the nonce half. For an unsolicited call the delivery is defined, though not
in RFC 9901: RFC 9449 Section 9 has the resource server answer a request that
carries no nonce, using a 401 with the use_dpop_nonce error and a DPoP-Nonce
header, and the client retries with that value in the proof. So a resource
server can supply a nonce to a client that never asked it for one.

What that leaves open is aud. The proof binds htu and htm, not the audience of
the credential, and RFC 9901 leaves a KB-JWT's aud to the protocol in use.

So is the gap you mean the KB-JWT equivalent of Section 9 -- an HTTP-level
nonce and audience binding defined for a direct credential presentation -- and
would reusing Section 9 be the intended answer, or does that not carry,
because the challenge and the nonce belong to DPoP rather than to the
credential?

[Drafted with AI assistance; I have checked every point and agree with it.]

Best,
Jijie Wei