Hi David, Thank you for making these changes!
Sincerely, RFC Editor/rv > On Jun 20, 2025, at 7:07 PM, David Dong via RT <[email protected]> wrote: > > Hi Rebecca, > > This is complete; thank you: > > https://www.iana.org/assignments/media-types/application/rs-metadata+xml > > Best regards, > > David Dong > IANA Services Sr. Specialist > > On Fri Jun 20 18:39:13 2025, [email protected] wrote: >> Hi IANA, >> >> We made some updates to the media type registration template in >> Section 4.1 of this document. Please update the following template to >> match the edited document: >> >> https://www.iana.org/assignments/media-types/application/rs- >> metadata+xml >> >> Here are the the edited output files: >> https://www.rfc-editor.org/authors/rfc9806.txt >> https://www.rfc-editor.org/authors/rfc9806.html >> https://www.rfc-editor.org/authors/rfc9806.pdf >> >> And here is the diff file showing the changes: >> https://www.rfc-editor.org/authors/rfc9806-diff.html >> >> Please let us know if you have any questions. >> >> Thank you! >> RFC Editor/rv >> >> >>> On Jun 19, 2025, at 10:53 PM, Dan Mongrain >>> <[email protected]> wrote: >>> >>> I fully approve the document in its current condition. >>> >>> Thanx, >>> Dan >>> Dan Mongrain, eng. >>> Principal Engineer, >>> VESTA Solutions >>> www.VESTAPublicSafety.com >>> >>> >>> o: +1.819.931.2129 >>> m: +1.613.558.0764 >>> e: [email protected] >>> www.linkedin.com/in/DanMongrain >>> >>> On Thu, Jun 19, 2025, 22:26 Rebecca VanRheenen >>> <[email protected]> wrote: >>> Hi Dan, >>> >>> You noted: >>>> I have fully reviewed the RFC editors' questions and resulting >>>> output and they are more than satisfactory. >>> >>> Based on this, we believe that no changes are needed per questions >>> #2-5 (question #1 was for the AD). Please let us know if you approve >>> the document in its current form. Once you provide your approval, we >>> will mark it on the AUTH48 status page for this document >>> (https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc- >>> 2Deditor.org_auth48_rfc9806&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_C93KOmcBXCBnhee2v6PYlc&r=n9aaU9xSQM4- >>> mK_yF4tJzi7SeOWS3tTUWut1BhcRBI5vMR5LUWrTKzC_1DF8wC_4&m=_M05u__Abilxza6b5ZCRvZgTfO- >>> AfdCJGAXv-xE-- >>> 6ZapM3Mg7fLHBgcUeVRy2Mi&s=yJ8AYapYUj1OlwRlT82f2Ks7LKqK1vxyrl_m8- >>> b5vGQ&e= ). >>> >>> We’ll continue to wait for Andy’s response to question #1. >>> >>> Please let us know if you have any questions! >>> >>> Thank you, >>> RFC Editor/rv >>> >>> >>>> On Jun 18, 2025, at 3:23 PM, Dan Mongrain >>>> <[email protected]> wrote: >>>> >>>> Good afternoon, >>>> >>>> If I may plead, can we please change the status of the errata at >>>> our earliest convenience? I have fully reviewed the RFC editors' >>>> questions and resulting output and they are more than satisfactory. >>>> Only thing preventing this document from moving forward is the >>>> status of the errata. >>>> >>>> Thanx, >>>> Dan >>>> Dan Mongrain, eng. >>>> Principal Engineer, >>>> VESTA Solutions >>>> http://www.VESTAPublicSafety.com >>>> >>>> >>>> o: +1.819.931.2129 >>>> m: +1.613.558.0764 >>>> e: [email protected] >>>> https://urldefense.proofpoint.com/v2/url?u=http- >>>> 3A__www.linkedin.com_in_DanMongrain&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_C93KOmcBXCBnhee2v6PYlc&r=n9aaU9xSQM4- >>>> mK_yF4tJzi7SeOWS3tTUWut1BhcRBI5vMR5LUWrTKzC_1DF8wC_4&m=_M05u__Abilxza6b5ZCRvZgTfO- >>>> AfdCJGAXv-xE-- >>>> 6ZapM3Mg7fLHBgcUeVRy2Mi&s=HsvGKkLHbZTZkuVG9S7pN2DdQ0KijQXFQKn1W5thRTY&e= >>>> >>>> >>>> On Tue, Jun 17, 2025 at 12:42 PM Brian Rosen <[email protected]> >>>> wrote: >>>> Andy >>>> >>>> I have no idea why this wasn’t resolved as Verified, but it should >>>> have been. Shame on me for not folliowing through on it. At this >>>> point, hold for document update is just as good because we have >>>> that document here. >>>> >>>> It’s a very real problem, which has actually caused inter problems >>>> in the wild, hence the document. >>>> >>>> Brian >>>> >>>> >>>>> On Jun 17, 2025, at 12:08 PM, [email protected] wrote: >>>>> >>>>> Dan and AD*, >>>>> >>>>> *AD, please see question #1 below. >>>>> >>>>> Dan, while reviewing this document during AUTH48, please resolve >>>>> (as necessary) the following questions, which are also in the XML >>>>> file. >>>>> >>>>> >>>>> 1) <!-- [rfced] *AD - This document references the following >>>>> erratum report: >>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc- >>>>> 2Deditor.org_errata_eid7987&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_C93KOmcBXCBnhee2v6PYlc&r=n9aaU9xSQM4- >>>>> mK_yF4tJzi7SeOWS3tTUWut1BhcRBI5vMR5LUWrTKzC_1DF8wC_4&m=pAsO4SBd1jx2YMD675szlMVQpxFD_gwp4mAoHS1u0VqpjTHQyehOyCFjpj- >>>>> zFQuF&s=QNT4GN3jeuKaoQ8sTENByNzO4jOxZPPEgvLpB-H36X4&e= . >>>>> >>>>> This erratum is currently in Reported state. The Web Portion of >>>>> the Style Guide >>>>> (https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc- >>>>> 2Deditor.org_styleguide_part2_-23ref- >>>>> 5Ferrata&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_C93KOmcBXCBnhee2v6PYlc&r=n9aaU9xSQM4- >>>>> mK_yF4tJzi7SeOWS3tTUWut1BhcRBI5vMR5LUWrTKzC_1DF8wC_4&m=pAsO4SBd1jx2YMD675szlMVQpxFD_gwp4mAoHS1u0VqpjTHQyehOyCFjpj- >>>>> zFQuF&s=v2UpAp1GjxN0dcsTdn4kk0mHSBF8UZcclhP5rClcIEY&e= ) states, >>>>> "Errata in >>>>> the Reported state should not be referenced; they are not >>>>> considered stable." >>>>> The RPC strongly recommends that a referenced erratum report be >>>>> either >>>>> Verified or Held for Document Update. >>>>> >>>>> As AD, would you address this erratum report? >>>>> --> >>>>> >>>>> >>>>> 2) <!-- [rfced] Please note that the title of the document has >>>>> been updated as >>>>> follows. Abbreviations have been expanded per Section 3.6 of RFC >>>>> 7322 ("RFC >>>>> Style Guide"), and we updated "correcting" to "to Correct". >>>>> Please review. >>>>> >>>>> Original: >>>>> Updates to SIPREC correcting Metadata Media Type >>>>> >>>>> Current: >>>>> Updates to SIP-Based Media Recording (SIPREC) to Correct >>>>> Metadata Media Type >>>>> --> >>>>> >>>>> >>>>> 3) <!-- [rfced] We made some changes in the media type template >>>>> in Section 4.1 >>>>> Please review and let us know any concerns. Note that we will ask >>>>> IANA to >>>>> update the template at >>>>> https://urldefense.proofpoint.com/v2/url?u=https- >>>>> 3A__www.iana.org_assignments_media-2Dtypes_application_rs- >>>>> 2Dmetadata- >>>>> 2Bxml&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_C93KOmcBXCBnhee2v6PYlc&r=n9aaU9xSQM4- >>>>> mK_yF4tJzi7SeOWS3tTUWut1BhcRBI5vMR5LUWrTKzC_1DF8wC_4&m=pAsO4SBd1jx2YMD675szlMVQpxFD_gwp4mAoHS1u0VqpjTHQyehOyCFjpj- >>>>> zFQuF&s=69zn4urpfT54ntZHWIKKQVSwUoBGumK0pi6i-gF6A-I&e= >>>>> to match the edited document prior to publication. >>>>> --> >>>>> >>>>> >>>>> 4) <!-- [rfced] FYI - We have added expansions for the following >>>>> abbreviations >>>>> per Section 3.6 of RFC 7322 ("RFC Style Guide"). Please review >>>>> each >>>>> expansion in the document carefully to ensure correctness. >>>>> >>>>> Session Recording Clients (SRCs) >>>>> Session Recording Servers (SRSs) >>>>> --> >>>>> >>>>> >>>>> 5) <!-- [rfced] Please review the "Inclusive Language" portion of >>>>> the online >>>>> Style Guide <https://urldefense.proofpoint.com/v2/url?u=https- >>>>> 3A__www.rfc-2Deditor.org_styleguide_part2_-23inclusive- >>>>> 5Flanguage&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_C93KOmcBXCBnhee2v6PYlc&r=n9aaU9xSQM4- >>>>> mK_yF4tJzi7SeOWS3tTUWut1BhcRBI5vMR5LUWrTKzC_1DF8wC_4&m=pAsO4SBd1jx2YMD675szlMVQpxFD_gwp4mAoHS1u0VqpjTHQyehOyCFjpj- >>>>> zFQuF&s=mnoSVqjBdx15fmIp4Ox21WEDlvkw2SI741G6GRlrl5g&e= > >>>>> and let us know if any changes are needed. Updates of this >>>>> nature typically >>>>> result in more precise language, which is helpful for readers. >>>>> >>>>> Note that our script did not flag any words in particular, but >>>>> this should >>>>> still be reviewed as a best practice. >>>>> --> >>>>> >>>>> >>>>> Thank you. >>>>> >>>>> RFC Editor/rv >>>>> >>>>> >>>>> >>>>> On Jun 17, 2025, at 12:04 PM, [email protected] wrote: >>>>> >>>>> *****IMPORTANT***** >>>>> >>>>> Updated 2025/06/17 >>>>> >>>>> 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://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc- >>>>> 2Deditor.org_faq_&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_C93KOmcBXCBnhee2v6PYlc&r=n9aaU9xSQM4- >>>>> mK_yF4tJzi7SeOWS3tTUWut1BhcRBI5vMR5LUWrTKzC_1DF8wC_4&m=pAsO4SBd1jx2YMD675szlMVQpxFD_gwp4mAoHS1u0VqpjTHQyehOyCFjpj- >>>>> zFQuF&s=kuqEe5RjQRaXOAiw5JSGO8LIKQ2Nkx4J-wxghZFiEL8&e= ). >>>>> >>>>> 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://urldefense.proofpoint.com/v2/url?u=https- >>>>> 3A__trustee.ietf.org_license- >>>>> 2Dinfo&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_C93KOmcBXCBnhee2v6PYlc&r=n9aaU9xSQM4- >>>>> mK_yF4tJzi7SeOWS3tTUWut1BhcRBI5vMR5LUWrTKzC_1DF8wC_4&m=pAsO4SBd1jx2YMD675szlMVQpxFD_gwp4mAoHS1u0VqpjTHQyehOyCFjpj- >>>>> zFQuF&s=dCkvWYUfKtv3F9suoPwsnuKtiGTN2a750Fhe9SP_PJU&e= ). >>>>> >>>>> * 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://urldefense.proofpoint.com/v2/url?u=https- >>>>> 3A__authors.ietf.org_rfcxml- >>>>> 2Dvocabulary&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_C93KOmcBXCBnhee2v6PYlc&r=n9aaU9xSQM4- >>>>> mK_yF4tJzi7SeOWS3tTUWut1BhcRBI5vMR5LUWrTKzC_1DF8wC_4&m=pAsO4SBd1jx2YMD675szlMVQpxFD_gwp4mAoHS1u0VqpjTHQyehOyCFjpj- >>>>> zFQuF&s=IUdQn1nUdrL1m6viWjhw4HgYaA6VuV5i6yrBLHC5XgM&e= >. >>>>> >>>>> * 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 >>>>> >>>>> * [email protected] (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). >>>>> >>>>> * [email protected], which is a new archival mailing >>>>> list >>>>> to preserve AUTH48 conversations; it is not an active >>>>> discussion >>>>> list: >>>>> >>>>> * More info: >>>>> https://urldefense.proofpoint.com/v2/url?u=https- >>>>> 3A__mailarchive.ietf.org_arch_msg_ietf-2Dannounce_yb6lpIGh- >>>>> 2D4Q9l2USxIAe6P8O4Zc&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_C93KOmcBXCBnhee2v6PYlc&r=n9aaU9xSQM4- >>>>> mK_yF4tJzi7SeOWS3tTUWut1BhcRBI5vMR5LUWrTKzC_1DF8wC_4&m=pAsO4SBd1jx2YMD675szlMVQpxFD_gwp4mAoHS1u0VqpjTHQyehOyCFjpj- >>>>> zFQuF&s=c11qErYCyEFkXW58ZnQYxAhZgaCaOsI6tBZKJBE_lT8&e= >>>>> >>>>> * The archive itself: >>>>> https://urldefense.proofpoint.com/v2/url?u=https- >>>>> 3A__mailarchive.ietf.org_arch_browse_auth48archive_&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_C93KOmcBXCBnhee2v6PYlc&r=n9aaU9xSQM4- >>>>> mK_yF4tJzi7SeOWS3tTUWut1BhcRBI5vMR5LUWrTKzC_1DF8wC_4&m=pAsO4SBd1jx2YMD675szlMVQpxFD_gwp4mAoHS1u0VqpjTHQyehOyCFjpj- >>>>> zFQuF&s=DYFH5FhiBRn1dEcaTNJ_cMInFtSbaizcDSDv3L8yTWw&e= >>>>> >>>>> * 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, >>>>> [email protected] 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://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc- >>>>> 2Deditor.org_authors_rfc9806.xml&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_C93KOmcBXCBnhee2v6PYlc&r=n9aaU9xSQM4- >>>>> mK_yF4tJzi7SeOWS3tTUWut1BhcRBI5vMR5LUWrTKzC_1DF8wC_4&m=pAsO4SBd1jx2YMD675szlMVQpxFD_gwp4mAoHS1u0VqpjTHQyehOyCFjpj- >>>>> zFQuF&s=cuOLG21PWYltTHNuqUZ29vtnxZ3PACnIFiaVrTnpDvk&e= >>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc- >>>>> 2Deditor.org_authors_rfc9806.html&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_C93KOmcBXCBnhee2v6PYlc&r=n9aaU9xSQM4- >>>>> mK_yF4tJzi7SeOWS3tTUWut1BhcRBI5vMR5LUWrTKzC_1DF8wC_4&m=pAsO4SBd1jx2YMD675szlMVQpxFD_gwp4mAoHS1u0VqpjTHQyehOyCFjpj- >>>>> zFQuF&s=uqYPgbqw3M9XaUsQGx_MCP0GP2AZNgtt1tm-UHkCDAE&e= >>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc- >>>>> 2Deditor.org_authors_rfc9806.pdf&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_C93KOmcBXCBnhee2v6PYlc&r=n9aaU9xSQM4- >>>>> mK_yF4tJzi7SeOWS3tTUWut1BhcRBI5vMR5LUWrTKzC_1DF8wC_4&m=pAsO4SBd1jx2YMD675szlMVQpxFD_gwp4mAoHS1u0VqpjTHQyehOyCFjpj- >>>>> zFQuF&s=RMldRdvlyelNJBDWCFHIthv-zeJaz3fK0khSEWqK0DY&e= >>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc- >>>>> 2Deditor.org_authors_rfc9806.txt&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_C93KOmcBXCBnhee2v6PYlc&r=n9aaU9xSQM4- >>>>> mK_yF4tJzi7SeOWS3tTUWut1BhcRBI5vMR5LUWrTKzC_1DF8wC_4&m=pAsO4SBd1jx2YMD675szlMVQpxFD_gwp4mAoHS1u0VqpjTHQyehOyCFjpj- >>>>> zFQuF&s=o3Tq3lLMEyoHMdNlhBhDbL4q4plKis3va3jfHj_Ytlc&e= >>>>> >>>>> Diff file of the text: >>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc- >>>>> 2Deditor.org_authors_rfc9806- >>>>> 2Ddiff.html&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_C93KOmcBXCBnhee2v6PYlc&r=n9aaU9xSQM4- >>>>> mK_yF4tJzi7SeOWS3tTUWut1BhcRBI5vMR5LUWrTKzC_1DF8wC_4&m=pAsO4SBd1jx2YMD675szlMVQpxFD_gwp4mAoHS1u0VqpjTHQyehOyCFjpj- >>>>> zFQuF&s=XZGGdux7gfLc0YKHJfyz0BU4w6tbIEb2TrvL5n4XgRc&e= >>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc- >>>>> 2Deditor.org_authors_rfc9806- >>>>> 2Drfcdiff.html&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_C93KOmcBXCBnhee2v6PYlc&r=n9aaU9xSQM4- >>>>> mK_yF4tJzi7SeOWS3tTUWut1BhcRBI5vMR5LUWrTKzC_1DF8wC_4&m=pAsO4SBd1jx2YMD675szlMVQpxFD_gwp4mAoHS1u0VqpjTHQyehOyCFjpj- >>>>> zFQuF&s=nSBtZvcg20bknRXlEbwZpM7SAzr_MwnGFGDOPzyi7l8&e= (side by >>>>> side) >>>>> >>>>> Diff of the XML: >>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc- >>>>> 2Deditor.org_authors_rfc9806- >>>>> 2Dxmldiff1.html&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_C93KOmcBXCBnhee2v6PYlc&r=n9aaU9xSQM4- >>>>> mK_yF4tJzi7SeOWS3tTUWut1BhcRBI5vMR5LUWrTKzC_1DF8wC_4&m=pAsO4SBd1jx2YMD675szlMVQpxFD_gwp4mAoHS1u0VqpjTHQyehOyCFjpj- >>>>> zFQuF&s=zrGPUabbiDs1dzFpmi2B5_4zsVwr0Okjf_A4Q_d6o3E&e= >>>>> >>>>> >>>>> Tracking progress >>>>> ----------------- >>>>> >>>>> The details of the AUTH48 status of your document are here: >>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc- >>>>> 2Deditor.org_auth48_rfc9806&d=DwIFaQ&c=q3cDpHe1hF8lXU5EFjNM_C93KOmcBXCBnhee2v6PYlc&r=n9aaU9xSQM4- >>>>> mK_yF4tJzi7SeOWS3tTUWut1BhcRBI5vMR5LUWrTKzC_1DF8wC_4&m=pAsO4SBd1jx2YMD675szlMVQpxFD_gwp4mAoHS1u0VqpjTHQyehOyCFjpj- >>>>> zFQuF&s=ZdHWYEIT0FFRbyf0MmGqF-rtMmpM5BwQdAMH7Rd3xDU&e= >>>>> >>>>> Please let us know if you have any questions. >>>>> >>>>> Thank you for your cooperation, >>>>> >>>>> RFC Editor >>>>> >>>>> -------------------------------------- >>>>> RFC9806 (draft-ietf-sipcore-siprec-fix-mediatype-06) >>>>> >>>>> Title : Updates to SIPREC correcting Metadata Media >>>>> Type >>>>> Author(s) : D. Mongrain >>>>> WG Chair(s) : Brian Rosen, Jean Mahoney >>>>> Area Director(s) : Andy Newton, Orie Steele >>>>> >>>> >>>> >>>> For more information on how and why we collect your personal >>>> information, please visit our Privacy Policy. >>> >>> >>> >>> For more information on how and why we collect your personal >>> information, please visit our Privacy Policy. > -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
