Subject: [sipcore] Re: I-D Action: draft-ietf-sipcore-siprec-fix-mediatype-02.txt
From: Roman Shpount <[email-masked]>
To: Dan Mongrain <dan.mongrain=[email-masked]>
Cc: [email-masked]
Date: Wed, 26 Mar 2025 17:32:29 -0400
List-Id: SIP Core Working Group <sipcore.ietf.org>

Hi Dan,

Hate to be the grammar patrol, but here is the introduction with some
missing commas added and a verb fixed:

SIPREC is defined by [RFC7865] and [RFC7866]. The former specifies the use
of 'application/rs-metadata+xml' when identifying metadata content, whereas
the latter uses "application/rs-metadata". Since [RFC7865] defines SIPREC
metadata, it was identified as normative, and errata 7987 (
https://www.rfc-editor.org/errata/eid7987) was created against [RFC7865] to
report the issue. This document resolves the errata.

In addition, as neither document registered the media type with IANA, this
document rectifies this gap.

Best,
_____________
Roman Shpount

On Wed, Mar 26, 2025 at 5:12 PM Dan Mongrain <dan.mongrain=
[email-masked]> wrote:

> I enhanced the introduction to specify the document addresses errata 7987.
>
> Dan
>
>
> *Dan Mongrain, eng.*Principal Engineer,
> VESTA Solutions
> www.VESTAPublicSafety.com
>
> *[image:
> https://www.motorolasolutions.com/content/dam/msi/images/logos/corporate/msiemailsignature.png]*
>
> *o*:  +1.819.931.2129
> *m*: +1.613.558.0764
> e:   [email-masked]
> <[email-masked]>
> www.linkedin.com/in/DanMongrain
>
> <https://batchat.motorolasolutions.com/home/ls/community/mic>
>
>
> On Wed, Mar 26, 2025 at 4:57 PM <[email-masked]> wrote:
>
>> Internet-Draft draft-ietf-sipcore-siprec-fix-mediatype-02.txt is now
>> available. It is a work item of the Session Initiation Protocol Core
>> (SIPCORE)
>> WG of the IETF.
>>
>>    Title:   Updates to SIPREC correcting Metadata Media Type
>>    Author:  Dan Mongrain
>>    Name:    draft-ietf-sipcore-siprec-fix-mediatype-02.txt
>>    Pages:   5
>>    Dates:   2025-03-26
>>
>> Abstract:
>>
>>    SIP-based Media Recording (SIPREC) protocol is defined by both RFC
>>    7865 and RFC 7866.  Unfortunately, both RFCs contradict each other
>>    regarding how recording metadata is to be labeled.  In addition,
>>    neither RFCs registered the new media type.  This document updates
>>    RFC 7866 to align with RFC 7865 when labeling recording metadata and
>>    registers the new media type.
>>
>> The IETF datatracker status page for this Internet-Draft is:
>>
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dietf-2Dsipcore-2Dsiprec-2Dfix-2Dmediatype_&d=DwIGaQ&c=q3cDpHe1hF8lXU5EFjNM_C93KOmcBXCBnhee2v6PYlc&r=n9aaU9xSQM4-mK_yF4tJzi7SeOWS3tTUWut1BhcRBI5vMR5LUWrTKzC_1DF8wC_4&m=0FTuYECR8R2ObR-EvXANWk8kcy8kafvumka783N4hDW2IyH6R3HmXVCw4fLWBWq5&s=qxFBr4XIlo2xuT3L3ssr9PgFC4mVlMOB0ZyLZlwqWLw&e=
>>
>> There is also an HTMLized version available at:
>>
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_html_draft-2Dietf-2Dsipcore-2Dsiprec-2Dfix-2Dmediatype-2D02&d=DwIGaQ&c=q3cDpHe1hF8lXU5EFjNM_C93KOmcBXCBnhee2v6PYlc&r=n9aaU9xSQM4-mK_yF4tJzi7SeOWS3tTUWut1BhcRBI5vMR5LUWrTKzC_1DF8wC_4&m=0FTuYECR8R2ObR-EvXANWk8kcy8kafvumka783N4hDW2IyH6R3HmXVCw4fLWBWq5&s=QomLFcCUXSrPuwJS4kaPFnFMBQEtKPQhnzNSd3cHYvE&e=
>>
>> A diff from the previous version is available at:
>>
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__author-2Dtools.ietf.org_iddiff-3Furl2-3Ddraft-2Dietf-2Dsipcore-2Dsiprec-2Dfix-2Dmediatype-2D02&d=DwIGaQ&c=q3cDpHe1hF8lXU5EFjNM_C93KOmcBXCBnhee2v6PYlc&r=n9aaU9xSQM4-mK_yF4tJzi7SeOWS3tTUWut1BhcRBI5vMR5LUWrTKzC_1DF8wC_4&m=0FTuYECR8R2ObR-EvXANWk8kcy8kafvumka783N4hDW2IyH6R3HmXVCw4fLWBWq5&s=WDZOgA36YzyEpxubOyWNNXNvO31K9PdqP9_Yd85Z0GI&e=
>>
>> Internet-Drafts are also available by rsync at:
>> rsync.ietf.org::internet-drafts
>>
>>
>> _______________________________________________
>> sipcore mailing list -- [email-masked]
>> To unsubscribe send an email to [email-masked]
>>
>
> *For more information on how and why we collect your personal information,
> please visit our Privacy Policy
> <https://www.motorolasolutions.com/en_us/about/privacy-policy.html?elqTrackId=8980d888905940e39a2613a7a3dcb0a7&elqaid=2786&elqat=2#privacystatement>.*
> _______________________________________________
> sipcore mailing list -- [email-masked]
> To unsubscribe send an email to [email-masked]
>