From e2f5235e318eaad15429974656ec7c8d65956966 Mon Sep 17 00:00:00 2001 From: Dominique Hazael-Massieux Date: Tue, 23 Apr 2024 07:52:13 +0200 Subject: [PATCH 1/2] Replace references to RFC8829 with RFC9429 --- webrtc.html | 106 ++++++++++++++++++++++++++-------------------------- 1 file changed, 53 insertions(+), 53 deletions(-) diff --git a/webrtc.html b/webrtc.html index a6040be82..cb71b1808 100644 --- a/webrtc.html +++ b/webrtc.html @@ -342,7 +342,7 @@

Size of the prefetched ICE pool as defined in [[!RFC8829]]. + "ice-candidate-pool pc-constructor">[[!RFC9429]].

@@ -427,10 +427,10 @@

RTCIceTransportPolicy Enum

- As described in [[!RFC8829]], if + As described in [[!RFC9429]], if the {{RTCConfiguration/iceTransportPolicy}} member of the {{RTCConfiguration}} is specified, it defines the ICE candidate policy [[!RFC8829]] the + "ice-candidate-policy">ICE candidate policy [[!RFC9429]] the browser uses to surface the permitted candidates to the application; only these candidates will be used for connectivity checks. @@ -494,7 +494,7 @@

RTCBundlePolicy Enum

- As described in [[!RFC8829]], + As described in [[!RFC9429]], bundle policy affects which media tracks are negotiated if the remote endpoint is not bundle-aware, and what ICE candidates are gathered. If the remote endpoint is bundle-aware, all media tracks @@ -558,7 +558,7 @@

RTCRtcpMuxPolicy Enum

- As described in [[!RFC8829]], the + As described in [[!RFC9429]], the {{RTCRtcpMuxPolicy}} affects what ICE candidates are gathered to support non-multiplexed RTCP. The only value defined in this spec is {{RTCRtcpMuxPolicy/"require"}}. @@ -1122,9 +1122,9 @@

RTCPeerConnection Interface

- The [[!RFC8829]] specification, as a whole, describes the details of how + The [[!RFC9429]] specification, as a whole, describes the details of how the {{RTCPeerConnection}} operates. References to specific - subsections of [[!RFC8829]] are provided as appropriate. + subsections of [[!RFC9429]] are provided as appropriate.

@@ -1157,7 +1157,7 @@

Agent =], namely {{addIceCandidate}}, {{setConfiguration}}, {{setLocalDescription}}, {{setRemoteDescription}} and {{close}}. These interactions are described in the relevant sections in this - document and in [[!RFC8829]]. The [= ICE Agent =] also provides + document and in [[!RFC9429]]. The [= ICE Agent =] also provides indications to the user agent when the state of its internal representation of an {{RTCIceTransport}} changes, as described in . @@ -1669,7 +1669,7 @@

In parallel, start the process to apply description as described in [[!RFC8829]], + "processing-a-local-desc processing-a-remote-desc">[[!RFC9429]], with these additional restrictions:

    @@ -1684,7 +1684,7 @@

  1. If remote is false and this triggers the ICE candidate gathering process in [[!RFC8829]], the [= ICE Agent =] + "applying-a-local-desc">[[!RFC9429]], the [= ICE Agent =] MUST NOT gather candidates that would be [= administratively prohibited =].

    @@ -1692,7 +1692,7 @@

  2. If remote is true and this triggers ICE connectivity checks in [[!RFC8829]], the + "applying-a-remote-desc">[[!RFC9429]], the [= ICE Agent =] MUST NOT attempt to connect to candidates that are [= administratively prohibited =].

    @@ -1728,7 +1728,7 @@

    connection.{{RTCPeerConnection/[[SignalingState]]}} as described in - [[!RFC8829]], then [= reject =] p with + [[!RFC9429]], then [= reject =] p with a newly [= exception/created =] {{InvalidStateError}} and abort these steps.

    @@ -2362,7 +2362,7 @@

  3. As described by [[!RFC8829]], + "applying-a-remote-desc">[[!RFC9429]], attempt to find an existing {{RTCRtpTransceiver}} object, transceiver, to represent the [= @@ -3099,7 +3099,7 @@

    value of configuration.{{RTCConfiguration/iceTransportPolicy}}. As defined in [[!RFC8829]], if the new [= ICE + "setconfiguration">[[!RFC9429]], if the new [= ICE transports setting =] changes the existing setting, no action will be taken until the next gathering phase. If a script wants this to happen immediately, it should do an ICE @@ -3110,14 +3110,14 @@

    Set the [= ICE Agent =]'s prefetched ICE candidate pool size as defined in [[!RFC8829]] to the + "ice-candidate-pool pc-constructor">[[!RFC9429]] to the value of configuration.{{RTCConfiguration/iceCandidatePoolSize}}. If the new [= ICE candidate pool size =] changes the existing setting, this may result in immediate gathering of new pooled candidates, or discarding of existing pooled candidates, as defined in [[!RFC8829]]. + "setconfiguration">[[!RFC9429]].

  4. @@ -3128,7 +3128,7 @@

    As defined in [[!RFC8829]], if a new list of servers + "setconfiguration">[[!RFC9429]], if a new list of servers replaces the [= ICE Agent =]'s existing [= ICE servers list=], no action will be taken until the next gathering phase. If a script wants this to happen immediately, it should do an ICE @@ -3417,7 +3417,7 @@

    the remote peer is able to accept trickled ICE candidates [[RFC8838]]. The value is determined based on whether a remote description indicates support for trickle ICE, as - defined in [[!RFC8829]]. + defined in [[!RFC9429]]. Prior to the completion of {{RTCPeerConnection/setRemoteDescription}}, this value is null. @@ -3520,10 +3520,10 @@

    Creating the SDP MUST follow the appropriate process for - generating an offer described in [[!RFC8829]], except the user + generating an offer described in [[!RFC9429]], except the user agent MUST treat a {{RTCRtpTransceiver/stopping}} transceiver as {{RTCRtpTransceiver/stopped}} for the - purposes of RFC8829 in this case. + purposes of RFC9429 in this case.

    As an offer, the generated SDP will contain the full set of @@ -3642,7 +3642,7 @@

    Inspect the offerer's system state to determine the currently available resources as necessary for generating the offer, as described in - [[!RFC8829]]. + [[!RFC9429]].

  5. @@ -3695,7 +3695,7 @@

    inspection, the current state of connection and its {{RTCRtpTransceiver}}s, generate an SDP offer, sdpString, as described in [[!RFC8829]]. + "create-offer">[[!RFC9429]].

    1. @@ -3832,7 +3832,7 @@

      corresponding offer, specifies how the media plane should be established. The generation of the SDP MUST follow the appropriate process for generating an answer described in - [[!RFC8829]]. + [[!RFC9429]].

      The generated SDP will also contain the [= ICE agent =]'s @@ -3854,7 +3854,7 @@

      "RTCPeerConnection-setLocalDescription-pranswer.html,RTCPeerConnection-setRemoteDescription-pranswer.html"> An answer can be marked as provisional, as described in [[!RFC8829]], by setting + "use-of-provisional-answer">[[!RFC9429]], by setting the {{RTCSessionDescriptionInit/type}} to {{RTCSdpType/"pranswer"}}.

      @@ -3935,7 +3935,7 @@

      Inspect the answerer's system state to determine the currently available resources as necessary for generating the answer, as described in - [[!RFC8829]]. + [[!RFC9429]].

    2. @@ -3989,7 +3989,7 @@

      connection and its {{RTCRtpTransceiver}}s, generate an SDP answer, sdpString, as described in [[!RFC8829]]. + "generating-an-answer">[[!RFC9429]].

      1. @@ -4138,7 +4138,7 @@

        Passing in a description is optional. If left out, then {{setLocalDescription}} will implicitly [= create an offer =] or [= create an answer =], as needed. As noted in - [[!RFC8829]], if a + [[!RFC9429]], if a description with SDP is passed in, that SDP is not allowed to have changed from when it was returned from either {{createOffer}} or {{createAnswer}}. @@ -4302,7 +4302,7 @@

        As noted in [[!RFC8829]], calling this + "applying-a-local-desc">[[!RFC9429]], calling this method may trigger the ICE candidate gathering process by the [= ICE Agent =].

        @@ -4353,7 +4353,7 @@

        connection.{{RTCPeerConnection/[[SignalingState]]}} as described in [[!RFC8829]], + "processing-a-local-desc processing-a-remote-desc">[[!RFC9429]], then run the following sub steps:

          @@ -4517,7 +4517,7 @@

          In parallel, if the candidate is not [= administratively prohibited =], add the ICE candidate candidate as described in - [[!RFC8829]]. + [[!RFC9429]]. Use candidate.{{RTCIceCandidate/usernameFragment}} to identify the ICE [= generation =]; if @@ -4717,7 +4717,7 @@

          The {{setConfiguration}} method updates the configuration of this {{RTCPeerConnection}} object. This includes changing the configuration of the [= ICE Agent =]. As noted - in [[!RFC8829]], + in [[!RFC9429]], when the ICE configuration changes in a way that requires a new gathering phase, an ICE restart is required.

          @@ -5939,7 +5939,7 @@

          does not match transceiver.{{RTCRtpTransceiver/[[Direction]]}} intersected with the offered direction (as described in - [[!RFC8829]]), + [[!RFC9429]]), return true.

          @@ -7479,7 +7479,7 @@

          detection or bandwidth estimation.

          - Following the rules in [[!RFC8829]], + Following the rules in [[!RFC9429]], the video MAY be downscaled. The media MUST NOT be upscaled to create fake data that did not occur in the input source, the media MUST NOT be cropped except as needed to @@ -7799,7 +7799,7 @@

          "sdp">sendrecv or sendonly and add the MSID of the sender's streams, as defined in [[!RFC8829]]. + "subsequent-offers subsequent-answers">[[!RFC9429]].

          If any {{RTCRtpSender}} object in senders @@ -7968,7 +7968,7 @@

          media description =] for the corresponding transceiver as {{RTCRtpTransceiverDirection/"recvonly"}} or {{RTCRtpTransceiverDirection/"inactive"}}, as defined in - [[!RFC8829]]. + [[!RFC9429]].

          @@ -8094,7 +8094,7 @@

          Adding a transceiver will cause future calls to {{createOffer}} to add a [= media description =] for the corresponding transceiver, as defined in [[!RFC8829]]. + "subsequent-offers">[[!RFC9429]].

          The initial value of {{RTCRtpTransceiver/mid}} is null. @@ -8308,11 +8308,11 @@

          If sendEncodings is set, then subsequent calls to {{createOffer}} will be configured to send multiple RTP encodings as defined in [[!RFC8829]]. When + "subsequent-offers initial-offers">[[!RFC9429]]. When {{RTCPeerConnection/setRemoteDescription}} is called with a corresponding remote description that is able to receive multiple RTP encodings as defined in - [[!RFC8829]], the + [[!RFC9429]], the {{RTCRtpSender}} may send multiple RTP encodings and the parameters retrieved via the transceiver's {{RTCRtpTransceiver/sender}}.{{RTCRtpSender/getParameters()}} @@ -8746,7 +8746,7 @@

          sender is to be associated with. The {{RTCRtpSender/[[AssociatedMediaStreamIds]]}} slot is used when sender is represented in SDP as described in - [[!RFC8829]]. + [[!RFC9429]].

        1. @@ -9667,7 +9667,7 @@

          If set, this RTP encoding will be sent with the RID header extension as defined by [[!RFC8829]]. The RID is not + "initial-offers">[[!RFC9429]]. The RID is not modifiable via {{RTCRtpSender/setParameters}}. It can only be set or modified in {{RTCPeerConnection/addTransceiver}} on the sending side. Read-only parameter. @@ -9969,7 +9969,7 @@

          The "format specific parameters" field from the a=fmtp line in the SDP corresponding to the codec, if one exists, as defined by - [[!RFC8829]]. + [[!RFC9429]].

          @@ -10746,7 +10746,7 @@

          The {{RTCRtpTransceiver}} interface represents a combination of an {{RTCRtpSender}} and an {{RTCRtpReceiver}} that share a common [= media stream "identification-tag" =]. As defined in [[!RFC8829]], an {{RTCRtpTransceiver}} is said + "rtptransceivers">[[!RFC9429]], an {{RTCRtpTransceiver}} is said to be associated with a [= media description =] if its "mid" property is non-null and matches a [= media stream "identification-tag" =] in the [= media description =]; otherwise it @@ -10755,7 +10755,7 @@

          A {{RTCRtpTransceiver}} may become associated with a new pending - description in RFC8829 while still being disassociated with the + description in RFC9429 while still being disassociated with the current description. This may happen in [= check if negotiation is needed =].

          @@ -10841,7 +10841,7 @@

          Let transceiver have a [[\JsepMid]] internal slot, initialized to null. This is the "RtpTransceiver mid property" defined in [[!RFC8829]], and is only + "initial-offers initial-answers">[[!RFC9429]], and is only modified there.

          2. @@ -10927,7 +10927,7 @@

          As defined in [[!RFC8829]], the + "transceiver-direction">[[!RFC9429]], the direction attribute indicates the preferred direction of this transceiver, which will be used in calls to {{RTCPeerConnection/createOffer}} and @@ -10939,7 +10939,7 @@

          sendonly, recvonly or inactive as defined in [[!RFC8829]] + "subsequent-offers subsequent-answers">[[!RFC9429]]

          On getting, the user agent MUST run the following steps: @@ -11031,7 +11031,7 @@

          As defined in [[!RFC8829]], the + "transceiver-current-direction">[[!RFC9429]], the currentDirection attribute indicates the current direction negotiated for this transceiver. The value of currentDirection is independent of the value of @@ -11093,9 +11093,9 @@

          {{RTCPeerConnection/createOffer}} to generate a zero port in the [= media description =] for the corresponding transceiver, as defined in [[!RFC8829]] (The user agent MUST treat a + "transceiver-stop">[[!RFC9429]] (The user agent MUST treat a {{stopping}} transceiver as {{stopped}} for the purposes of - RFC8829 only in this case). However, to avoid problems with + RFC9429 only in this case). However, to avoid problems with [[RFC8843]], a transceiver that is {{stopping}}, but not {{stopped}}, will not affect {{RTCPeerConnection/createAnswer}}. @@ -11106,7 +11106,7 @@

          {{RTCPeerConnection/createAnswer}} to generate a zero port in the [= media description =] for the corresponding transceiver, as defined in [[!RFC8829]]. + "transceiver-stop">[[!RFC9429]].

          The transceiver will remain in the {{stopping}} state, unless @@ -11291,7 +11291,7 @@

          codecs. These payload types are referenced by the m=video or m=audio lines in the order of preference, and codecs that are not negotiated do not appear in this list as defined in - section 5.2.1 of [[!RFC8829]]. A previously negotiated codec + section 5.2.1 of [[!RFC9429]]. A previously negotiated codec that is subsequently removed disappears from the m=video or m=audio line, and while its codec payload type is not to be reused in future offers or answers, its payload type may also @@ -11499,7 +11499,7 @@

          agent is expected to stop sending some of the simulcast streams.

          - As defined in [[!RFC8829]], an + As defined in [[!RFC9429]], an offer from a user-agent will only contain a "send" description and no "recv" description on the a=simulcast line. Alternatives and restrictions (described in @@ -11512,7 +11512,7 @@

          {{RTCPeerConnection/addTransceiver}}. However when {{RTCPeerConnection/setRemoteDescription}} is called with a corresponding remote description that is able to send multiple RTP - encodings as defined in [[!RFC8829]], and the browser supports + encodings as defined in [[!RFC9429]], and the browser supports receiving multiple RTP encodings, the {{RTCRtpReceiver}} may receive multiple RTP encodings and the parameters retrieved via the transceiver's From 49c99ac5ed97a0a6cc85056b80fb3a728df2abfe Mon Sep 17 00:00:00 2001 From: Dominique Hazael-Massieux Date: Tue, 23 Apr 2024 07:52:35 +0200 Subject: [PATCH 2/2] Document reference update as candidate correction --- amendments.json | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/amendments.json b/amendments.json index 9d946b728..8a86a36e0 100644 --- a/amendments.json +++ b/amendments.json @@ -895,5 +895,15 @@ "web-platform-tests/wpt#45427" ] } + ], + "normative-references": [ + { + "description": "Replace RFC8829 reference with RFC9429", + "type": "correction", + "status": "candidate", + "pr": 2966, + "id": 46, + "testUpdates": "already-tested" + } ] }