[webtransport] Fix TLS exporter interface w3c/webtransport@f321bec

＋ Fix references to fetch() and websocket
w3c/webtransport@826fe29

Author: triple-underscore

webtransport-ja.html

@@ -196,8 +196,8 @@
 ●●options
 
 spec_title:WebTransport
-spec_date:2026-05-19
-trans_update:2026-05-26
+spec_date:2026-06-04
+trans_update:2026-06-11
 source_checked:260225
 	page_state_key:
 original_url:https://w3c.github.io/webtransport/
@@ -589,6 +589,8 @@
 	%見越される同時並行な流入~双方向~stream数:anticipatedConcurrentIncomingBidirectionalStreams
 	%~label長さ:labelLength
 	%文脈~長さ:contextLength
+	%出力~長さ:outputLength
+	%最大~長さ:-
 	%鍵~用の素材:keyingMaterial
 	%集められた統計:gatheredStats
 	%~datagram統計:datagramStats
@@ -1443,6 +1445,8 @@
 
 [CSP3]
     Mike West; Antonio Sartori. ＜Content Security Policy Level 3＞. URL: https://w3c.github.io/webappsec-csp/
+[CSS2]
+    Bert Bos; et al. ＜Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification＞. URL: https://drafts.csswg.org/css2/
 [DOM]
     Anne van Kesteren. ＜DOM Standard＞. Living Standard. URL: https://dom.spec.whatwg.org/
 [ECMASCRIPT-6.0]
@@ -1491,6 +1495,8 @@
     Victor Vasiliev. ＜WebTransport Protocol Framework＞. Internet-Draft. URL: https://datatracker.ietf.org/doc/html/draft-ietf-webtrans-overview
 [WEBIDL]
     Edgar Chen; Timothy Gu. ＜Web IDL Standard＞. Living Standard. URL: https://webidl.spec.whatwg.org/
+[WEBSOCKETS]
+    Adam Rice. ＜WebSockets Standard＞. Living Standard. URL: https://websockets.spec.whatwg.org/
 
 ●●ref_informative
 
@@ -3441,7 +3447,7 @@ <h2 title="WebTransport Interface">6. `WebTransport^I ~interface</h2>
   `constructor＠#dom-webtransport-webtransport$(`USVString$ %url, optional `WebTransportOptions$I %options = {});
 
   `Promise$&lt;`WebTransportConnectionStats$I&gt; `getStats$mT();
-  [`NewObject$] `Promise$&lt;`Uint8Array$I&gt; `exportKeyingMaterial$mT(`BufferSource$I %label, optional `BufferSource$I %context);
+  [`NewObject$] `Promise$&lt;`Uint8Array$I&gt; `exportKeyingMaterial$mT(`BufferSource$I %label, `BufferSource$I %context, `unsigned long$ %outputLength);
   readonly attribute `Promise$&lt;`undefined$&gt; `ready$mT;
   readonly attribute `WebTransportReliabilityMode$I `reliability$mT;
   readonly attribute `WebTransportCongestionControl$I `congestionControl$mT;
@@ -5444,9 +5450,9 @@ <h3 title="Methods">6.4. ~method</h3>
 	</dd>
 
 	<dt>
-`exportKeyingMaterial(label, context)@mT
+`exportKeyingMaterial(label, context, outputLength)@mT
 ◎
-exportKeyingMaterial(BufferSource label, optional BufferSource context)
+exportKeyingMaterial(BufferSource label, BufferSource context, unsigned long outputLength)
 </dt>
 
 	<dd>
@@ -5504,6 +5510,22 @@ <h3 title="Methods">6.4. ~method</h3>
 ~RET `却下される~promise$( `RangeError$E )
 ◎
 If contextLength is more than 255, return a promise rejected with a RangeError.
+</li>
+			<li>
+%最大~長さ ~LET `実装定義$な整数
+— 4096 以上になるモノトスル
+◎
+↓</li>
+			<li>
+~IF［
+%出力~長さ ~EQ 0
+］~OR［
+%出力~長さ ~GT %最大~長さ
+］
+⇒
+~RET `却下される~promise$( `RangeError$E 例外 )
+◎
+If outputLength is 0 or more than an implementation-defined value—which must be at least 4096—return a promise rejected with a RangeError.
 </li>
 			<li>
 %~promise ~LET `新たな~promise$
@@ -5551,12 +5573,11 @@ <h3 title="Methods">6.4. ~method</h3>
 にて定義されるとおり，~TLS鍵~exporterを呼出して生産される`~byte列$
 — 次を与える下で
 ⇒＃
-%~label長さ,
 %~label,
-%文脈~長さ,
-%文脈
+%文脈,
+%出力~長さ
 ◎
-Let keyingMaterial be a Uint8Array that is produced by invoking a TLS key exporter, as defined in [WEB-TRANSPORT-OVERVIEW] Section 4.1, with labelLength, label, contextLength, and if present, context.
+Let keyingMaterial be a Uint8Array that is produced by invoking a TLS key exporter, as defined in [WEB-TRANSPORT-OVERVIEW] Section 4.1, with label, context, and outputLength.
 </li>
 					<li>
 <p>
@@ -11188,15 +11209,15 @@ <h3 title="Fingerprinting and Tracking">14.5. 指紋収集と追跡</h3>
 <p>
 重要なこととして、
 他の~web~platform~API
-— `FETCH$r, `WEBRTC$r など —
+— `fetch()＠~FETCH#dom-global-fetch$c や `WebSocket＠~WEBSOCKET#websocket$I など —
 も，ごく類似な~networking能力を供することを認識すること。
 したがって、
 ~WebTransport~APIを追加することに因る~privacyへの悪影響は，
 実質無いに等しい。
 この節における考慮点は、
 他の~networking能力にも等しく適用される。
 ◎
-It is important to recognize that very similar networking capabilities are provided by other web platform APIs (such as fetch and [webrtc]). The net adverse effect on privacy due to adding WebTransport is therefore minimal. The considerations in this section applies equally to other networking capabilities.
+It is important to recognize that very similar networking capabilities are provided by other web platform APIs (such as fetch() and WebSocket). The net adverse effect on privacy due to adding WebTransport is therefore minimal. The considerations in this section applies equally to other networking capabilities.
 </p>
 
 <p>