Hi Magnus,

Thank you for your review.  We have updated the document (mostly) as described 
below and posted the revised files here:
   https://www.rfc-editor.org/authors/rfc9751.xml
   https://www.rfc-editor.org/authors/rfc9751.txt
   https://www.rfc-editor.org/authors/rfc9751.pdf
   https://www.rfc-editor.org/authors/rfc9751.html

AUTH48 diffs: 
   https://www.rfc-editor.org/authors/rfc9751-auth48diff.html
   https://www.rfc-editor.org/authors/rfc9751-auth48rfcdiff.html (side by side)

Comprehensive diffs: 
   https://www.rfc-editor.org/authors/rfc9751-diff.html
   https://www.rfc-editor.org/authors/rfc9751-rfcdiff.html (side by side)


Please see the followup notes below.  We have cut resolved items from the list. 
 

> On Mar 7, 2025, at 4:59 AM, Magnus Westerlund 
> <magnus.westerlund=40ericsson....@dmarc.ietf.org> wrote:
> 
> 
> 1) <!-- [rfced] Please insert any keywords (beyond those that appear in
> the title) for use on 
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fsearch&data=05%7C02%7Cmagnus.westerlund%40ericsson.com%7C8ee01dc6487c4afb23ce08dd556262f7%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638760605627392783%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=khPswFQKDdfavf4chOsFkPKg83eh837iZfOBU8dobpE%3D&reserved=0.
>  -->
> 
> 
> MW: 

Are there any keywords you would like to include? 



> 3) <!-- [rfced] Is it correct that this document does not define "other 
> means"?  If yes, perhaps the text should indicate this is out of scope, as 
> I expected this document to update the Media Types registry in some way to 
> account for this information.  
> 
> Original (prior sentence included for context):
>    This registry is not used for any purpose
>    other than to track which media types actually have RTP payload
>    formats.  That purpose could be addressed through other means.
> -->
> 
> 
> Yes, declaring it out of scope could be a potential. We expect this to be 
> addressed as part of the update of the media type registration procedure work 
> in MediaMan WG which is ongoing.

Rather than noting “other means” are out of scope, we updated the text to read 
as follows.  Please let us know if any updates are desired. 

Current:  
  This registry is not used for any purpose other than to track which
   media types actually have RTP payload formats, which can be done
   through other means.


> 6) <!-- [rfced] What does "without affecting its status as part of an 
> informational RFC" mean?  Also, the second sentence is incomplete.  Please 
> clarify. 
> 
> Original: 
>    This paragraph is
>    changed without affecting its status as part of an informational RFC.
>    Thus removing the need to register in the "RTP Payload Format media
>    types".
> 
> Perhaps:
>    The following paragraph is
>    updated as shown below, thus removing the need for media types to be
>    registered in the "RTP Payload Format Media Types" registry.
> -->
> 
> 
> MW:
> 
>   The following paragraph is
>    updated as shown below, thus removing the need for media types to be
>    registered in the "RTP Payload Format Media Types" registry. Note that this
>    update does not impact the updated text and the rest of RFC 8088 status as 
> informational RFC.
> 
> There was raised comments that was worried that due to RFC 9751 is standards 
> track this changed text would be elevated also to standards track. Thus, I 
> think we should retain some note, but I suggest a reformulation above.

Thanks for this context.  The text currently reads as follows.  Please let us 
know if any updates are needed.

   The following paragraph is updated as shown below, thus removing the
   need for media types to be registered in the "RTP Payload Format
   Media Types" registry.  Note that this update does not impact the
   rest of RFC 8088's status as an Informational RFC.


Please review the above and let us know how you would like to proceed.  We’ll 
wait to hear further from you before continuing with publication.

Thanks Magnus! 
RFC Editor/sg



> 
> 
> Thank you.
> 
> RFC Editor
> 
> 
> On Feb 24, 2025, at 10:03 PM, rfc-edi...@rfc-editor.org wrote:
> 
> *****IMPORTANT*****
> 
> Updated 2025/02/24
> 
> RFC Author(s):
> --------------
> 
> Instructions for Completing AUTH48
> 
> Your document has now entered AUTH48.  Once it has been reviewed and 
> approved by you and all coauthors, it will be published as an RFC.  
> If an author is no longer available, there are several remedies 
> available as listed in the FAQ 
> (https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Ffaq%2F&data=05%7C02%7Cmagnus.westerlund%40ericsson.com%7C8ee01dc6487c4afb23ce08dd556262f7%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638760605627447574%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=QngYGt6h80mCFMsQ27k44hq3Moi65pXyBtA%2B3tft4%2Fc%3D&reserved=0).
> 
> You and you coauthors are responsible for engaging other parties 
> (e.g., Contributors or Working Group) as necessary before providing 
> your approval.
> 
> Planning your review 
> ---------------------
> 
> Please review the following aspects of your document:
> 
> *  RFC Editor questions
> 
>    Please review and resolve any questions raised by the RFC Editor 
>    that have been included in the XML file as comments marked as 
>    follows:
> 
>    <!-- [rfced] ... -->
> 
>    These questions will also be sent in a subsequent email.
> 
> *  Changes submitted by coauthors 
> 
>    Please ensure that you review any changes submitted by your 
>    coauthors.  We assume that if you do not speak up that you 
>    agree to changes submitted by your coauthors.
> 
> *  Content 
> 
>    Please review the full content of the document, as this cannot 
>    change once the RFC is published.  Please pay particular attention to:
>    - IANA considerations updates (if applicable)
>    - contact information
>    - references
> 
> *  Copyright notices and legends
> 
>    Please review the copyright notice and legends as defined in
>    RFC 5378 and the Trust Legal Provisions 
>    (TLP – 
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftrustee.ietf.org%2Flicense-info&data=05%7C02%7Cmagnus.westerlund%40ericsson.com%7C8ee01dc6487c4afb23ce08dd556262f7%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638760605627458543%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=mwgxPIbWbIBAoniPRSzkx9KfgYA0qGxwZQ%2BJzsGl6nc%3D&reserved=0).
> 
> *  Semantic markup
> 
>    Please review the markup in the XML file to ensure that elements of  
>    content are correctly tagged.  For example, ensure that <sourcecode> 
>    and <artwork> are set correctly.  See details at 
>    
> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fauthors.ietf.org%2Frfcxml-vocabulary&data=05%7C02%7Cmagnus.westerlund%40ericsson.com%7C8ee01dc6487c4afb23ce08dd556262f7%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638760605627469401%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=oIQKkJVLu17x26K%2B1CioNS%2Bvl7VdoGm1Zd2G3PFvOzw%3D&reserved=0>.
> 
> *  Formatted output
> 
>    Please review the PDF, HTML, and TXT files to ensure that the 
>    formatted output, as generated from the markup in the XML file, is 
>    reasonable.  Please note that the TXT will have formatting 
>    limitations compared to the PDF and HTML.
> 
> 
> Submitting changes
> ------------------
> 
> To submit changes, please reply to this email using ‘REPLY ALL’ as all 
> the parties CCed on this message need to see your changes. The parties 
> include:
> 
>    *  your coauthors
>    
>    *  rfc-edi...@rfc-editor.org (the RPC team)
> 
>    *  other document participants, depending on the stream (e.g., 
>       IETF Stream participants are your working group chairs, the 
>       responsible ADs, and the document shepherd).
>      
>    *  auth48archive@rfc-editor.org, which is a new archival mailing list 
>       to preserve AUTH48 conversations; it is not an active discussion 
>       list:
>      
>      *  More info:
>         
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Fietf-announce%2Fyb6lpIGh-4Q9l2USxIAe6P8O4Zc&data=05%7C02%7Cmagnus.westerlund%40ericsson.com%7C8ee01dc6487c4afb23ce08dd556262f7%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638760605627480030%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=jp4xHBey7kMhz6p9Jo4%2B02xKOK11OGQcIGE%2Fb6NK6oc%3D&reserved=0
>      
>      *  The archive itself:
>         
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fbrowse%2Fauth48archive%2F&data=05%7C02%7Cmagnus.westerlund%40ericsson.com%7C8ee01dc6487c4afb23ce08dd556262f7%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638760605627490805%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=2VT8ul%2But5%2BgBKU9cs8SKTrVM2p1HMDFFk%2B5x%2FQavIU%3D&reserved=0
> 
>      *  Note: If only absolutely necessary, you may temporarily opt out 
>         of the archiving of messages (e.g., to discuss a sensitive matter).
>         If needed, please add a note at the top of the message that you 
>         have dropped the address. When the discussion is concluded, 
>         auth48archive@rfc-editor.org will be re-added to the CC list and 
>         its addition will be noted at the top of the message. 
> 
> You may submit your changes in one of two ways:
> 
> An update to the provided XML file
>  — OR —
> An explicit list of changes in this format
> 
> Section # (or indicate Global)
> 
> OLD:
> old text
> 
> NEW:
> new text
> 
> You do not need to reply with both an updated XML file and an explicit 
> list of changes, as either form is sufficient.
> 
> We will ask a stream manager to review and approve any changes that seem
> beyond editorial in nature, e.g., addition of new text, deletion of text, 
> and technical changes.  Information about stream managers can be found in 
> the FAQ.  Editorial changes do not require approval from a stream manager.
> 
> 
> Approving for publication
> --------------------------
> 
> To approve your RFC for publication, please reply to this email stating
> that you approve this RFC for publication.  Please use ‘REPLY ALL’,
> as all the parties CCed on this message need to see your approval.
> 
> 
> Files 
> -----
> 
> The files are available here:
>    
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9751.xml&data=05%7C02%7Cmagnus.westerlund%40ericsson.com%7C8ee01dc6487c4afb23ce08dd556262f7%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638760605627501561%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=gSVq4hHTp7Hk59MiMMPKI8oLmQ0Qst0DEORo93cq3bo%3D&reserved=0
>    
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9751.html&data=05%7C02%7Cmagnus.westerlund%40ericsson.com%7C8ee01dc6487c4afb23ce08dd556262f7%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638760605627512277%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=vto3LxvETStJDxPbTlHdSqV%2BoyQj%2BtBT9odRtf3gVVA%3D&reserved=0
>    
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9751.pdf&data=05%7C02%7Cmagnus.westerlund%40ericsson.com%7C8ee01dc6487c4afb23ce08dd556262f7%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638760605627522775%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=82ciclb8Yw9blN0DZZSSy4H5wqzleytn%2FCz6A6tCkNQ%3D&reserved=0
>    
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9751.txt&data=05%7C02%7Cmagnus.westerlund%40ericsson.com%7C8ee01dc6487c4afb23ce08dd556262f7%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638760605627533287%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=f%2Faf3SYIopeCqp1GaKpOkUu1TuKEPMINlwKDsNjwepw%3D&reserved=0
> 
> Diff file of the text:
>    
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9751-diff.html&data=05%7C02%7Cmagnus.westerlund%40ericsson.com%7C8ee01dc6487c4afb23ce08dd556262f7%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638760605627544726%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=YcKAF67rQssIZw%2FsXjXyXiPiHXlB7gADLy3ELLsDrMw%3D&reserved=0
>    
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9751-rfcdiff.html&data=05%7C02%7Cmagnus.westerlund%40ericsson.com%7C8ee01dc6487c4afb23ce08dd556262f7%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638760605627556295%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=LWNx09hlp5scwfnFiuueOjao0zZ3m%2FToraP5YtArugQ%3D&reserved=0
>  (side by side)
> 
> Diff of the XML: 
>    
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9751-xmldiff1.html&data=05%7C02%7Cmagnus.westerlund%40ericsson.com%7C8ee01dc6487c4afb23ce08dd556262f7%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638760605627566916%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=2jWtEIy%2BdamZaQJdnXbaBj1Zb23vksoV%2BaAuZA8mOCI%3D&reserved=0
> 
> 
> Tracking progress
> -----------------
> 
> The details of the AUTH48 status of your document are here:
>    
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauth48%2Frfc9751&data=05%7C02%7Cmagnus.westerlund%40ericsson.com%7C8ee01dc6487c4afb23ce08dd556262f7%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638760605627577586%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=hWBljc%2BLNcFf7HpGs%2FzCemnD5UV45HGZLzFCpuVXex0%3D&reserved=0
> 
> Please let us know if you have any questions.  
> 
> Thank you for your cooperation,
> 
> RFC Editor
> 
> --------------------------------------
> RFC 9751 (draft-ietf-avtcore-rtp-payload-registry-05)
> 
> Title            : Closing the RTP Payload Format Media Types IANA Registry
> Author(s)        : M. Westerlund
> WG Chair(s)      : Dr. Bernard D. Aboba, Jonathan Lennox
> Area Director(s) : Zaheduzzaman Sarker, Francesca Palombini
> 
> 

-- 
auth48archive mailing list -- auth48archive@rfc-editor.org
To unsubscribe send an email to auth48archive-le...@rfc-editor.org

Reply via email to