Hi Rebecca, These changes are complete:
In the Link Relation Types registry: ice-server Conveys the STUN and TURN servers that can be used by an ICE agent to establish a connection with a peer. [RFC-ietf-wish-whip-16] In WHIP: WebRTC-HTTP Ingestion Protocol (WHIP) WebRTC-HTTP Ingestion Protocol (WHIP) URNs URN Name Reference IANA Registry Reference Change Controller urn:ietf:params:whip:ext WebRTC-HTTP ingestion protocol (WHIP) extension URNs [RFC-ietf-wish-whip-16, Section 6.4] See "WebRTC-HTTP Ingestion Protocol (WHIP) Extension URNs" on [https://www.iana.org/assignments/whip] IETF WebRTC-HTTP Ingestion Protocol (WHIP) Extension URNs URN Name Reference IANA Registry Reference Change Controller No registrations at this time. Please see: https://www.iana.org/assignments/link-relations/ https://www.iana.org/assignments/whip/ Best regards, David Dong IANA Services Sr. Specialist On Tue Mar 18 16:17:22 2025, rvanrhee...@staff.rfc-editor.org wrote: > Hi IANA, > > Please update the registries as described below to match the edited > document. If needed, the files are available here: > > https://www.rfc-editor.org/authors/rfc9725.txt > https://www.rfc-editor.org/authors/rfc9725.pdf > https://www.rfc-editor.org/authors/rfc9725.html > > https://www.rfc-editor.org/authors/rfc9725-diff.html > https://www.rfc-editor.org/authors/rfc9725-rfcdiff.html > > > 1) Lowercase "Agent" in the Description field of the "Link Relation > Types” registry (https://www.iana.org/assignments/link-relations) > > OLD ("Agent”): > Conveys the STUN and TURN servers that can be used by an > ICE Agent to establish a connection with a peer. > > NEW ("agent”): > Conveys the STUN and TURN servers that can be used by > an ICE agent to establish a connection with a peer. > > > 2) Capitalize title of the registry group at > https://www.iana.org/assignments/whip: > > OLD: > WebRTC-HTTP ingestion protocol (WHIP) > > NEW (capitalize “Ingestion Ingestion”): > WebRTC-HTTP Ingestion Protocol (WHIP) > > > 3) Capitalize the titles of the following registries at > https://www.iana.org/assignments/whip: > > OLD: > WebRTC-HTTP ingestion protocol (WHIP) URNs > WebRTC-HTTP ingestion protocol (WHIP) Extension URNs > > NEW (capitalize "Ingestion Protocol”): > WebRTC-HTTP Ingestion Protocol (WHIP) URNs > WebRTC-HTTP Ingestion Protocol (WHIP) Extension URNs > > > 4) Update the column headings for both registries at > https://www.iana.org/assignments/whip to match the edited document > (specifically, to match Section 6.3, Section 6.4, and the template in > Section 6.5.3): > > OLD: > URI > > NEW: > URN > > OLD: > Description > > NEW: > Name > > > 5) Update section number in “Reference” field in the "WebRTC-HTTP > ingestion protocol (WHIP) URNs” registry > (https://www.iana.org/assignments/whip): > > OLD: > Section 6.3.2 > > NEW: > Section 6.4 > > > 6) Update "IANA Registry Reference” field in the "WebRTC-HTTP > ingestion protocol (WHIP) URNs” registry > (https://www.iana.org/assignments/whip). > > OLD: > [https://www.iana.org/assignments/whip] > > NEW: > See "WebRTC-HTTP Ingestion Protocol (WHIP) Extension URNs" on > [https://www.iana.org/assignments/whip] > > > Thank you, > RFC Editor/rv > > > > > > On Mar 18, 2025, at 9:03 AM, Rebecca VanRheenen > > <rvanrhee...@staff.rfc-editor.org> wrote: > > > > Hi Murray and Sergio, > > > > We have marked your approvals on the AUTH48 status page for this > > document (see https://www.rfc-editor.org/auth48/rfc9725). > > > > In a separate email, we will request that IANA update the registries > > to match the edited document. Once that is done, we will prepare this > > document for publication. > > > > Thank you! > > RFC Editor/rv > > > > > > > >> On Mar 18, 2025, at 2:38 AM, Sergio Garcia Murillo > >> <sergio.garcia.muri...@gmail.com> wrote: > >> > >> I have made the final review of the document and I approve it! > >> > >> Great job everyone, thank you very much > >> Sergio > >> > >> On Mon, Mar 17, 2025 at 7:04 PM Rebecca VanRheenen > >> <rvanrhee...@staff.rfc-editor.org> wrote: > >> Sounds great, Sergio. Thank you! > >> > >> Sincerely, > >> RFC Editor/rv > >> > >> > >> > >>> On Mar 17, 2025, at 10:05 AM, Sergio Garcia Murillo > >>> <sergio.garcia.muri...@gmail.com> wrote: > >>> > >>> I will do a final review tomorrow morning my time and hopefully > >>> give my approval asap > >>> > >>> El lun, 17 mar 2025, 18:04, Rebecca VanRheenen > >>> <rvanrhee...@staff.rfc-editor.org> escribió: > >>> Hi Murray, > >>> > >>> We marked your AD approval on the AUTH48 status page for this > >>> document (see https://www.rfc-editor.org/auth48/rfc9725). > >>> > >>> We now need the following: 1) your approval for Alexandre and 2) > >>> Sergio’s approval. It seems that there may be a chance to wrap up > >>> approvals before the changeover on Wednesday, but if that isn’t > >>> possible, we’ll reach out to Andy as the incoming AD. > >>> > >>> After receiving these approvals, we’ll ask IANA to make some > >>> updates to the registries to match the edited document before > >>> publishing. > >>> > >>> For your convenience, here are the files: > >>> > >>> Updated XML file: > >>> https://www.rfc-editor.org/authors/rfc9725.xml > >>> > >>> Updated output files: > >>> https://www.rfc-editor.org/authors/rfc9725.txt > >>> https://www.rfc-editor.org/authors/rfc9725.pdf > >>> https://www.rfc-editor.org/authors/rfc9725.html > >>> > >>> Diff files showing all changes made during AUTH48: > >>> https://www.rfc-editor.org/authors/rfc9725-auth48diff.html > >>> https://www.rfc-editor.org/authors/rfc9725-auth48rfcdiff.html (side > >>> by side) > >>> > >>> Diff files showing all changes: > >>> https://www.rfc-editor.org/authors/rfc9725-diff.html > >>> https://www.rfc-editor.org/authors/rfc9725-rfcdiff.html (side by > >>> side) > >>> https://www.rfc-editor.org/authors/rfc9725-alt-diff.html (shows > >>> changes where text is moved or deleted) > >>> > >>> Thank you, > >>> RFC Editor/rv > >>> > >>> > >>> > >>>> On Mar 15, 2025, at 7:50 PM, Murray S. Kucherawy > >>>> <superu...@gmail.com> wrote: > >>>> > >>>> On Sun, Mar 16, 2025 at 8:24 AM Sean Turner <s...@sn3rd.com> > >>>> wrote: > >>>> Just so it’s clear you are giving approval both as an AD and for > >>>> Alexandre? > >>>> > >>>> My understanding is that I just approved the stuff Rebecca asked > >>>> me to approve as an AD because they're possibly substantive > >>>> changes since the IESG approved. The "approve on behalf of > >>>> Alexandre" step happens separately; I've said I would do that when > >>>> asked, but I don't think it's been asked yet. My answer there is > >>>> unchanged (I will be happy to do so), but becomes meaningless > >>>> sometime on Wednesday. > >>>> > >>>> -MSK > >>> > >> > > -- auth48archive mailing list -- auth48archive@rfc-editor.org To unsubscribe send an email to auth48archive-le...@rfc-editor.org
