Re: [rtcweb] Fwd: New Version Notification for draft-uberti-rtcweb-rfc8829bis-00.txt

Section 3.5.1 makes clear that only sections that are restarting are
affected:

   Note that gathering phases only gather the candidates needed by
   new/recycled/restarting "m=" sections; other "m=" sections continue
   to use their existing candidates.  Also, if an "m=" section is
   bundled (either by a successful bundle negotiation or by being marked
   as bundle-only), then candidates will be gathered and exchanged for
   that "m=" section if and only if its MID item is a BUNDLE-tag, as
   described in [RFC8843 <https://datatracker.ietf.org/doc/html/rfc8843>].

On Sat, Jul 10, 2021 at 7:17 PM Roman Shpount <roman@telurix.com> wrote:

> I have a question regarding max-compat in subsequent offers with
> iceRestart:
>
> Should new candidates be gathered for all m= lines or only for the m=lines
> which are not bundled after the previous offer/answer exchange?
>
> I would suggest that new candidates should be gathered for all m=lines to
> be compatible with 3PCC.
>
> Thank You,
> _____________
> Roman Shpount
>
>
> On Sat, Jul 10, 2021 at 9:11 PM Justin Uberti <justin@uberti.name> wrote:
>
>> As discussed at IETF 110. Diff from RFC8829:
>> https://tools.ietf.org/rfcdiff?url1=https://www.rfc-editor.org/rfc/rfc8829.txt&url2=https://www.ietf.org/archive/id/draft-uberti-rtcweb-rfc8829bis-00.txt
>>
>> ---------- Forwarded message ---------
>> From: <internet-drafts@ietf.org>
>> Date: Sat, Jul 10, 2021 at 6:03 PM
>> Subject: New Version Notification for
>> draft-uberti-rtcweb-rfc8829bis-00.txt
>> To: Cullen Jennings <fluffy@iii.ca>ca>, Eric Rescorla <ekr@rtfm.com>om>,
>> Justin Uberti <justin@uberti.name>
>>
>>
>>
>> A new version of I-D, draft-uberti-rtcweb-rfc8829bis-00.txt
>> has been successfully submitted by Justin Uberti and posted to the
>> IETF repository.
>>
>> Name:           draft-uberti-rtcweb-rfc8829bis
>> Revision:       00
>> Title:          JavaScript Session Establishment Protocol (JSEP)
>> Document date:  2021-07-10
>> Group:          Individual Submission
>> Pages:          106
>> URL:
>> https://www.ietf.org/archive/id/draft-uberti-rtcweb-rfc8829bis-00.txt
>> Status:
>> https://datatracker.ietf.org/doc/draft-uberti-rtcweb-rfc8829bis/
>> Html:
>> https://www.ietf.org/archive/id/draft-uberti-rtcweb-rfc8829bis-00.html
>> Htmlized:
>> https://datatracker.ietf.org/doc/html/draft-uberti-rtcweb-rfc8829bis
>>
>>
>> Abstract:
>>    This document describes the mechanisms for allowing a JavaScript
>>    application to control the signaling plane of a multimedia session
>>    via the interface specified in the W3C RTCPeerConnection API and
>>    discusses how this relates to existing signaling protocols.
>>
>>    This specification obsoletes RFC 8829.
>>
>>
>>
>>
>> The IETF Secretariat
>>
>>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>>
>