Magnus, Thank you for your reply. Updated accordingly and will publish the document shortly.
RFC Editor/ar > On Mar 19, 2025, at 1:00 PM, Magnus Westerlund > <magnus.westerl...@ericsson.com> wrote: > > Hi, > > Yes the suggestion is clearer please go ahead and use it. > > /Magnus > > From: Alice Russo <aru...@staff.rfc-editor.org> > Date: Wednesday, 19 March 2025 at 11:33 > To: Magnus Westerlund <magnus.westerl...@ericsson.com> > Cc: avtcore-...@ietf.org <avtcore-...@ietf.org>, avtcore-cha...@ietf.org > <avtcore-cha...@ietf.org>, bernard.ab...@gmail.com <bernard.ab...@gmail.com>, > zahed.sarker.i...@gmail.com<zahed.sarker.i...@gmail.com>, > auth48archive@rfc-editor.org <auth48archive@rfc-editor.org>, RFC Editor > <rfc-edi...@rfc-editor.org> > Subject: question - Re: AUTH48: RFC-to-be 9751 > <draft-ietf-avtcore-rtp-payload-registry-05> for your review > > [You don't often get email from aru...@staff.rfc-editor.org. Learn why this > is important athttps://aka.ms/LearnAboutSenderIdentification ] > > Hi Magnus, > As we prepare this document for publication > (https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9751.html&data=05%7C02%7Cmagnus.westerlund%40ericsson.com%7Cfc5e6d5321f948958fa308dd669f3c20%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638779556279599076%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=%2Bt1zZbuxGNpYf%2FXXvgReLx2Xufh%2FFAeRNaaVqJJ4Vvc%3D&reserved=0 > and additional formats), a question about the opening sentence of the > abstract: Is the following change acceptable? We find it more clear (i.e., to > prevent misreading it as authors of (a) formats and (b) WG process). > > Current: > A number of authors defining RTP payload formats and the Working > Group process have failed to ensure that the media types are > registered in the IANA "RTP Payload Format Media Types" registry as > recommended by RFC 8088. To simplify the process and rely only on > the "Media Types" registry, this document closes the RTP payload- > specific registry. In addition, it updates the instruction in RFC > 8088 to reflect this change. > > Perhaps: > The working group process and authors of RTP payload formats have > sometimes failed to ensure that the media types are registered in the > IANA "RTP Payload Format Media Types" registry as recommended by RFC > 8088. To simplify the process and rely only on the "Media Types" > registry, this document closes the RTP payload- specific registry. > In addition, it updates the instruction in RFC 8088 to reflect this > change. > > > Thank you. > RFC Editor/ar -- auth48archive mailing list -- auth48archive@rfc-editor.org To unsubscribe send an email to auth48archive-le...@rfc-editor.org
