Return-Path: X-Original-To: sipcore@mail2.ietf.org Delivered-To: sipcore@mail2.ietf.org Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id A76A912D19B4 for ; Wed, 26 Mar 2025 14:32:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at ietf.org X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=telurix.com Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gv8Y7JrdOQr7 for ; Wed, 26 Mar 2025 14:32:46 -0700 (PDT) Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id B200712D19A4 for ; Wed, 26 Mar 2025 14:32:46 -0700 (PDT) Received: by mail-lf1-x12a.google.com with SMTP id 2adb3069b0e04-5498d73ff88so33654e87.3 for ; Wed, 26 Mar 2025 14:32:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix.com; s=google; t=1743024765; x=1743629565; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=qDhDHKdrBKD2+zW7eFJ/6HfZeDwGlQDzxHZlL/I7hDQ=; b=jglkXteonPl+//q0UfYTS0+OF96SJCuGXYS2VIHa/QENhsI2tyRchkgbA+MPy3lasW 9uIeB9dca5CHsjQIrPUyBONaQJ2v8la6nQr7j1Es/Fgo66U0qEvbR5ZP67TAm3LHYUQi MFKXtQY9tYk15OL+OFmabaVvGxa7y0NQ5XHmg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1743024765; x=1743629565; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=qDhDHKdrBKD2+zW7eFJ/6HfZeDwGlQDzxHZlL/I7hDQ=; b=Fwg1cpzMiq8tjXFdsVsRhTY1Og/S8AKPHu2V2ozn7BgMYT3TmoLPXp5kaV1lcWV5vC srAYURea5ABhHtOwVxfnFquJlzexxfnr1Miz88kSoYe4UYiFkKayywOaCY+GdjH36xek TZIMrzFq5Mnh2D67SUwyQ5kz2gYfHAega18B9ZDZVpVG+tAnN/SOh5Qv8ggDySdpVEpO Q5VodWQXWuzA2AA5Z2XMWAMdcOLyhuBUwlcFuaX625Ioq2JyLUpiKrJ/IUXkH+loSV6+ dDYwAlbuQsXHa3arkKobxfzT6k4T9+Vispj0awk3QRVsxUSFRGY4FGy5fKAX7q1nPLXC cUOA== X-Gm-Message-State: AOJu0Yxn18nEdjd+Y/gE1ffbOtwNwXoKNdC/5e0eOYcqtoipl4Fh7gF7 guTQ1GEGIYlCYCnPajxor6DbEsohxsII5F0RYqaAvXmqaGvab9Hgalofmyl7qZuiQMPFn2SH3sJ nWx8= X-Gm-Gg: ASbGncubmO0w8LZUEay9hbpPvgmOkEJIyCsU7GoMiOBbuG/ZiCQKCaSUPdLhBm0NvQM y7VkCtONAp0OStFeraDkIDMItr/Cp9p7uJD+zHnzgMlCys9sMPYaaZ1j7xXh21OPHeSVBBSTXOs nB448L9hYW2Q/+ldBNfqXoMz0ylxBgZ9w7Vh3uQcNgjKgFRnhePnfOWkw++FxA5FYpNKloV/EUN XtvdbDsHnMKFJluBj5FVnM+5saxtpLPE9oYNdXF0mRigL0c8bCcZG0+eR2hPjqWnmc7OWv74+XR 8r7V7SQpiVzBRG8oqAOzRw5mbVUPldN0ArUiyJhcjhFzY2VnU19nlsE/VazxD526sCxiRX9vXU4 kW91jS7k= X-Google-Smtp-Source: AGHT+IG6AoC0CNVvUDPEIa8esocbuxUwkWMxk8WNt2HnOeV4VscBeMNX5HF0uR1Unb4vk1tT5LmYIA== X-Received: by 2002:a05:6512:31cd:b0:54a:edba:c904 with SMTP id 2adb3069b0e04-54b02c39ce0mr43277e87.7.1743024764732; Wed, 26 Mar 2025 14:32:44 -0700 (PDT) Received: from mail-lj1-f175.google.com (mail-lj1-f175.google.com. [209.85.208.175]) by smtp.gmail.com with ESMTPSA id 2adb3069b0e04-54ad6508287sm1873354e87.186.2025.03.26.14.32.44 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 26 Mar 2025 14:32:44 -0700 (PDT) Received: by mail-lj1-f175.google.com with SMTP id 38308e7fff4ca-30762598511so3954321fa.0 for ; Wed, 26 Mar 2025 14:32:44 -0700 (PDT) X-Received: by 2002:a05:6512:2354:b0:549:3b4f:4b39 with SMTP id 2adb3069b0e04-54b011cf9b8mr439651e87.10.1743024763798; Wed, 26 Mar 2025 14:32:43 -0700 (PDT) MIME-Version: 1.0 References: <174302256380.1781280.17872042307310179657@dt-datatracker-5b9b68c5b6-zxk6z> In-Reply-To: From: Roman Shpount Date: Wed, 26 Mar 2025 17:32:29 -0400 X-Gmail-Original-Message-ID: X-Gm-Features: AQ5f1JrY_z5wdJqiuGV2SM8_u5ZITwq8jXzKoes8l40x1ugpm-fara47IUegQRc Message-ID: To: Dan Mongrain Content-Type: multipart/alternative; boundary="000000000000e195ff0631459316" Message-ID-Hash: UUGMOS6W4GCMU6UBGD5QPBC4T75YVWED X-Message-ID-Hash: UUGMOS6W4GCMU6UBGD5QPBC4T75YVWED X-MailFrom: roman@telurix.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-sipcore.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: sipcore@ietf.org X-Mailman-Version: 3.3.9rc6 Precedence: list Subject: =?utf-8?q?=5Bsipcore=5D_Re=3A_I-D_Action=3A_draft-ietf-sipcore-siprec-fix-me?= =?utf-8?q?diatype-02=2Etxt?= List-Id: SIP Core Working Group Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --000000000000e195ff0631459316 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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=E2=80=AFPM Dan Mongrain 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: Dan.Mongrain@MotorolaSolutions.com > > www.linkedin.com/in/DanMongrain > > > > > On Wed, Mar 26, 2025 at 4:57=E2=80=AFPM 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=3Dhttps-3A__datatracker.ietf.= org_doc_draft-2Dietf-2Dsipcore-2Dsiprec-2Dfix-2Dmediatype_&d=3DDwIGaQ&c=3Dq= 3cDpHe1hF8lXU5EFjNM_C93KOmcBXCBnhee2v6PYlc&r=3Dn9aaU9xSQM4-mK_yF4tJzi7SeOWS= 3tTUWut1BhcRBI5vMR5LUWrTKzC_1DF8wC_4&m=3D0FTuYECR8R2ObR-EvXANWk8kcy8kafvumk= a783N4hDW2IyH6R3HmXVCw4fLWBWq5&s=3DqxFBr4XIlo2xuT3L3ssr9PgFC4mVlMOB0ZyLZlwq= WLw&e=3D >> >> There is also an HTMLized version available at: >> >> https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__datatracker.ietf.= org_doc_html_draft-2Dietf-2Dsipcore-2Dsiprec-2Dfix-2Dmediatype-2D02&d=3DDwI= GaQ&c=3Dq3cDpHe1hF8lXU5EFjNM_C93KOmcBXCBnhee2v6PYlc&r=3Dn9aaU9xSQM4-mK_yF4t= Jzi7SeOWS3tTUWut1BhcRBI5vMR5LUWrTKzC_1DF8wC_4&m=3D0FTuYECR8R2ObR-EvXANWk8kc= y8kafvumka783N4hDW2IyH6R3HmXVCw4fLWBWq5&s=3DQomLFcCUXSrPuwJS4kaPFnFMBQEtKPQ= hnzNSd3cHYvE&e=3D >> >> A diff from the previous version is available at: >> >> https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__author-2Dtools.ie= tf.org_iddiff-3Furl2-3Ddraft-2Dietf-2Dsipcore-2Dsiprec-2Dfix-2Dmediatype-2D= 02&d=3DDwIGaQ&c=3Dq3cDpHe1hF8lXU5EFjNM_C93KOmcBXCBnhee2v6PYlc&r=3Dn9aaU9xSQ= M4-mK_yF4tJzi7SeOWS3tTUWut1BhcRBI5vMR5LUWrTKzC_1DF8wC_4&m=3D0FTuYECR8R2ObR-= EvXANWk8kcy8kafvumka783N4hDW2IyH6R3HmXVCw4fLWBWq5&s=3DWDZOgA36YzyEpxubOyWNN= XNvO31K9PdqP9_Yd85Z0GI&e=3D >> >> Internet-Drafts are also available by rsync at: >> rsync.ietf.org::internet-drafts >> >> >> _______________________________________________ >> sipcore mailing list -- sipcore@ietf.org >> To unsubscribe send an email to sipcore-leave@ietf.org >> > > *For more information on how and why we collect your personal information= , > please visit our Privacy Policy > .* > _______________________________________________ > sipcore mailing list -- sipcore@ietf.org > To unsubscribe send an email to sipcore-leave@ietf.org > --000000000000e195ff0631459316 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Dan,

Hate to be the gramm= ar 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&= #39; when identifying metadata content, whereas the latter uses "appli= cation/rs-metadata". Since [RFC7865] defines SIPREC metadata, it was i= dentified as normative, and errata 7987 (https://www.rfc-editor.org/errata/eid7987) was crea= ted against [RFC7865] to report the issue. This document resolves the errat= a.

In addition, as neither document registered the media type with I= ANA, this document rectifies this gap.

Best,
_____________
Roman Shpount


On Wed, Mar 26, 2025 at 5:12=E2=80=AFPM Dan Mongrain <dan.mongrain= =3D40motorolasolu= tions.com@dmarc.ietf.org> wrote:
I enhanced the introduction t= o specify the document addresses errata 7987.

Dan<= /div>

Dan Mongrain, eng.
Principal Engineer,
VESTA Solut= ions
www.VESTAPu= blicSafety.com

3D"https://www.motorolasolutions.com/conte=

o:=C2=A0 +1.= 819.931.2129=C2=A0
m: +1.613.558.0764
e:=C2=A0 =C2=A0Dan.Mongrain@MotorolaSolutions.= com
www.linkedin.com/in/DanMongrain

<= a href=3D"https://batchat.motorolasolutions.com/home/ls/community/mic" targ= et=3D"_blank">

=


On Wed, Mar 26, 2025 at 4:57=E2=80=AFPM &= lt;internet-d= rafts@ietf.org> 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 (SIPCO= RE)
WG of the IETF.

=C2=A0 =C2=A0Title:=C2=A0 =C2=A0Updates to SIPREC correcting Metadata Media= Type
=C2=A0 =C2=A0Author:=C2=A0 Dan Mongrain
=C2=A0 =C2=A0Name:=C2=A0 =C2=A0 draft-ietf-sipcore-siprec-fix-mediatype-02.= txt
=C2=A0 =C2=A0Pages:=C2=A0 =C2=A05
=C2=A0 =C2=A0Dates:=C2=A0 =C2=A02025-03-26

Abstract:

=C2=A0 =C2=A0SIP-based Media Recording (SIPREC) protocol is defined by both= RFC
=C2=A0 =C2=A07865 and RFC 7866.=C2=A0 Unfortunately, both RFCs contradict e= ach other
=C2=A0 =C2=A0regarding how recording metadata is to be labeled.=C2=A0 In ad= dition,
=C2=A0 =C2=A0neither RFCs registered the new media type.=C2=A0 This documen= t updates
=C2=A0 =C2=A0RFC 7866 to align with RFC 7865 when labeling recording metada= ta and
=C2=A0 =C2=A0registers the new media type.

The IETF datatracker status page for this Internet-Draft is:
https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__datatracker.ietf= .org_doc_draft-2Dietf-2Dsipcore-2Dsiprec-2Dfix-2Dmediatype_&d=3DDwIGaQ&= amp;c=3Dq3cDpHe1hF8lXU5EFjNM_C93KOmcBXCBnhee2v6PYlc&r=3Dn9aaU9xSQM4-mK_= yF4tJzi7SeOWS3tTUWut1BhcRBI5vMR5LUWrTKzC_1DF8wC_4&m=3D0FTuYECR8R2ObR-Ev= XANWk8kcy8kafvumka783N4hDW2IyH6R3HmXVCw4fLWBWq5&s=3DqxFBr4XIlo2xuT3L3ss= r9PgFC4mVlMOB0ZyLZlwqWLw&e=3D

There is also an HTMLized version available at:
https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__d= atatracker.ietf.org_doc_html_draft-2Dietf-2Dsipcore-2Dsiprec-2Dfix-2Dmediat= ype-2D02&d=3DDwIGaQ&c=3Dq3cDpHe1hF8lXU5EFjNM_C93KOmcBXCBnhee2v6PYlc= &r=3Dn9aaU9xSQM4-mK_yF4tJzi7SeOWS3tTUWut1BhcRBI5vMR5LUWrTKzC_1DF8wC_4&a= mp;m=3D0FTuYECR8R2ObR-EvXANWk8kcy8kafvumka783N4hDW2IyH6R3HmXVCw4fLWBWq5&= ;s=3DQomLFcCUXSrPuwJS4kaPFnFMBQEtKPQhnzNSd3cHYvE&e=3D

A diff from the previous version is available at:
https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3= A__author-2Dtools.ietf.org_iddiff-3Furl2-3Ddraft-2Dietf-2Dsipcore-2Dsiprec-= 2Dfix-2Dmediatype-2D02&d=3DDwIGaQ&c=3Dq3cDpHe1hF8lXU5EFjNM_C93KOmcB= XCBnhee2v6PYlc&r=3Dn9aaU9xSQM4-mK_yF4tJzi7SeOWS3tTUWut1BhcRBI5vMR5LUWrT= KzC_1DF8wC_4&m=3D0FTuYECR8R2ObR-EvXANWk8kcy8kafvumka783N4hDW2IyH6R3HmXV= Cw4fLWBWq5&s=3DWDZOgA36YzyEpxubOyWNNXNvO31K9PdqP9_Yd85Z0GI&e=3D=

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


_______________________________________________
sipcore mailing list -- sipcore@ietf.org
To unsubscribe send an email to sipcore-leave@ietf.org

<= font size=3D"2">For more information on how and why we col= lect your personal information, please visit our Privacy Policy.

= _______________________________________________
sipcore mailing list -- sipcore@ietf.org
To unsubscribe send an email to sipcore-leave@ietf.org
--000000000000e195ff0631459316--