Remove JSEP Modifications

index.html

@@ -206,34 +206,11 @@ <h2>Modifications to existing procedures</h2>
           </ol>
         </li>
       </ul>
-      <p>
-        In the algorithms for generating initial offers in [[RTCWEB-JSEP]] section 5.2.1,
-        replace "for each supported RTP header extension, an "a=extmap" line, as specified in
-        [[RFC5285]], section 5" " with "For each RTP header extension "e"
-        listed in {{RTCRtpTransceiver/[[HeaderExtensionsToNegotiate]]}} where {{RTCRtpHeaderExtensionCapability/direction}} is not {{RTCRtpTransceiverDirection/"stopped"}}, an "a=extmap"
-        line, as specified in [[RFC5285]], section 5, with direction taken from "e"'s {{RTCRtpHeaderExtensionCapability/direction}}
-        attribute."
-      </p>
-      <p>
-        In the algorithm for generating subsequent offers in [[RTCWEB-JSEP]] section 5.2.2, replace "The
-        RTP header extensions MUST only include those that are present in the most recent answer"
-        with "For each RTP header extension listed in {{RTCRtpTransceiver/[[HeaderExtensionsToNegotiate]]}},
-        and where {{RTCRtpHeaderExtensionCapability/direction}} is not {{RTCRtpTransceiverDirection/"stopped"}}, generate
-        an appropriate "a=extmap" line with "direction" set according to the rules of [[RFC5285]]
-        section 6, considering the {{RTCRtpHeaderExtensionCapability/direction}} in {{RTCRtpTransceiver/[[HeaderExtensionsToNegotiate]]}} to indicate the
-        answerer's desired usage".
-      </p>
-      <p>
-        In the algorithm for generating initial answers in [[RTCWEB-JSEP]] section 5.3.1, replace "For
-        each supported RTP header extension that is present in the offer" with "For each
-        supported RTP header extension that is present in the offer and is also present in
-        {{RTCRtpTransceiver/[[HeaderExtensionsToNegotiate]]}} with a {{RTCRtpHeaderExtensionCapability/direction}} different from {{RTCRtpTransceiverDirection/"stopped"}},
-        set the appropriate direction based on {{RTCRtpHeaderExtensionCapability/direction}} that does not exceed the direction in the offer".
-      </p>
-      <p class="note">
-        Since JSEP does not know about WebRTC internal slots, merging this change requires
-        more work on a JSEP revision.
-      </p>
+    <p>
+      In [[JSEPbis]] Section 5.2.1 (Initial Offers) and 5.2.2 (Subsequent Answers) an RTP header extension "e" is
+      considered "enabled" if it is listed in {{RTCRtpTransceiver/[[HeaderExtensionsToNegotiate]]}} where
+      {{RTCRtpHeaderExtensionCapability/direction}} is not {{RTCRtpTransceiverDirection/"stopped"}}.
+    </p>
     </section>
     <section id="rtp-header-extension-control-transceiver-methods">
       <h3>Methods</h3>
@@ -427,7 +404,6 @@ <h2>Attributes</h2>
                   <p>Update the underlying system about the new <var>target</var>,
                   or that there is no application preference if <var>target</var> is
                   <code>null</code>.</p>
-                </li>
                 <p>
                   If <var>track</var> is synchronized with another
                   {{RTCRtpReceiver}}'s track for
@@ -440,13 +416,14 @@ <h2>Attributes</h2>
                   continuously make sure that the actual jitter buffer target is clamped
                   within the <a>minimum allowed target</a> and <a>maximum allowed
                   target</a>.
+                </p>
                   <p class="note">
                     If the <a>user agent</a> ends up using a target different from the
                     requested one (e.g. due to network conditions or physical memory
                     constraints), this is not reflected in the
                     {{RTCRtpReceiver/[[JitterBufferTarget]]}} internal slot.
                   </p>
-                </p>
+                </li>
                 <li>
                   <p>Modifying the jitter buffer target of the underlying system SHOULD
                   affect the internal audio or video buffering gradually in order not

webrtc-extensions.js

@@ -43,6 +43,11 @@ var respecConfig = {
       },
       "CRYPTEX": {
 	"aliasOf": "RFC9335"
-    }
+      },
+      "JSEPbis": {
+	"title": "JavaScript Session Establishment Protocol (JSEP) - bis",
+	"href": "https://www.ietf.org/archive/id/draft-uberti-rtcweb-rfc8829bis-04.html",
+	"publisher": "IETF"
+      }
     }
 }