Re: [AVTCORE] draft-hsyang-avtcore-rtp-haptics-02: Needs to register "haptics" as an SDP <media>

Jonathan Lennox <jonathan.lennox@8x8.com> Thu, 28 March 2024 15:33 UTC

Return-Path: <jonathan.lennox@8x8.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F551C14CF1C for <avt@ietfa.amsl.com>; Thu, 28 Mar 2024 08:33:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.096
X-Spam-Level:
X-Spam-Status: No, score=-7.096 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=8x8.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dz5Y3FYROxId for <avt@ietfa.amsl.com>; Thu, 28 Mar 2024 08:32:59 -0700 (PDT)
Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C7FEC14F6B8 for <avt@ietf.org>; Thu, 28 Mar 2024 08:32:59 -0700 (PDT)
Received: by mail-lf1-x129.google.com with SMTP id 2adb3069b0e04-515c50dc2afso1026560e87.1 for <avt@ietf.org>; Thu, 28 Mar 2024 08:32:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=8x8.com; s=googlemail; t=1711639977; x=1712244777; 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=plfDOQhCiXEMBsBcCTiqiW/ZchSx0U4i5Lv5JjWWzmY=; b=IhapaZjPMw3bPKBe7x/rf2+Ni4E5WlYbBtRlc31L/G9ITS1PQAHOlZeHNQfhq9XwM9 Mb27vl8nPxsDyy6M+b0n3EaQiNXc69AGl1Nqklr/ZZK0cbAtr+WI3W77Z1V4EIhP6E1o Ea8118J6oVLRluC/fxTRIy2gk3RFMBme8PAEg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711639977; x=1712244777; 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=plfDOQhCiXEMBsBcCTiqiW/ZchSx0U4i5Lv5JjWWzmY=; b=QJRJZsedTXW1kT1uKbPwRokoLCJ5D706XhzqWGdnjtvreAXEtZIa+l37pAsZM1jcUL Ij6FulXI2IDpXnmYkrSBJeqWmWSE0yhbG70gccoA/1jDTWdRxDZHnmU1rdS0uInqSzNy nzTvxauWGoWfuZ9C+bhGlTGJicXyW6AHVmY3D2ssAK5DkbTrxuOfKoSKdDmdClD97pTI tVoAcw2d1xUczEkKS2RLKvYX0k4s07wq2H3RFeESKvFmtHLcwXq/By75cmADQq5Cht4c znVWuEwkRvMSHyrRiCfsUr6nN24A3X2nbbX0f55S0sy4z1wGynCqVCQCSLIYuYzUB0Hz nwdQ==
X-Forwarded-Encrypted: i=1; AJvYcCXAqSDJOOksk1W89uhEmTx4hQRd1wYK8DhjjZZCJtFDSvzOPicnTZRdWud8TSnoNkVFwwFlryExVZi7+dM=
X-Gm-Message-State: AOJu0YycPquSod/ayHSVFIPEkWrbAd0l5vge68QSz5Sj2a+A3Qyrn1e2 qqwrubpPwHRWzfjRCi/Cx1WR9J2K5bPQoJPo8l7iiE1cPynQqEayI2ky20CR1PPvMoVD8wwHJ5k wxCa89kDzHNARcsp+8NPg612+x1cgIAruYOtH
X-Google-Smtp-Source: AGHT+IG070dpcj5sjU/dODsK5FUtVhxeFFBOijO/xbzPlr87UUbis3GgqXooR5mb1yzbW/6iJFxjDoCppAjuAgwT+Fc=
X-Received: by 2002:ac2:5b4b:0:b0:513:a73f:c0ed with SMTP id i11-20020ac25b4b000000b00513a73fc0edmr2168286lfp.51.1711639976742; Thu, 28 Mar 2024 08:32:56 -0700 (PDT)
MIME-Version: 1.0
References: <F58E66C6-4B0E-4E01-838D-427B6D668AC3@8x8.com> <DM6PR10MB3163B6C9C5FDD59D886A9D88EF2A2@DM6PR10MB3163.namprd10.prod.outlook.com> <AS8PR07MB80690675241A024599C02BBB933B2@AS8PR07MB8069.eurprd07.prod.outlook.com>
In-Reply-To: <AS8PR07MB80690675241A024599C02BBB933B2@AS8PR07MB8069.eurprd07.prod.outlook.com>
From: Jonathan Lennox <jonathan.lennox@8x8.com>
Date: Thu, 28 Mar 2024 11:32:45 -0400
Message-ID: <CADUk6txCyYRAd9hcBojHmtXAUF+o2y-O8H=2FU1SA0omS1fS3Q@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: Hyunsik Yang <Hyunsik.Yang=40InterDigital.com@dmarc.ietf.org>, IETF AVTCore WG <avt@ietf.org>, draft-hsyang-avtcore-rtp-haptics@ietf.org, mmusic@ietf.org, Xavier De Foy <Xavier.DeFoy@interdigital.com>
Content-Type: multipart/alternative; boundary="000000000000cc98ae0614ba3c0e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/dvhmW76EEHun9kc-kbNx3ClMGKQ>
Subject: Re: [AVTCORE] draft-hsyang-avtcore-rtp-haptics-02: Needs to register "haptics" as an SDP <media>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Mar 2024 15:33:03 -0000

The document making "haptics" a new top-level media type, coming out of the
mediaman WG, has IETF consensus (see
https://datatracker.ietf.org/doc/draft-ietf-mediaman-haptics/).

Since RTP payload types follow media types, I don't think that decision
needs be revisited here for SDP specifically.


On Thu, Mar 28, 2024, 5:46 AM Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
> If this work is adopted I think there should be a discussion e.g., with
> MMUSIC whether the registration of a new media-type for this is the correct
> way, instead of using e.g., "application" (or even "data"). There should be
> some justification for using a new media type.
>
> Regards,
>
> Christer
>
> > -----Original Message-----
> > From: mmusic <mmusic-bounces@ietf.org> On Behalf Of Hyunsik Yang
> > Sent: Wednesday, 13 March 2024 17.16
> > To: Jonathan Lennox <jonathan.lennox@8x8.com>; IETF AVTCore WG
> > <avt@ietf.org>; draft-hsyang-avtcore-rtp-haptics@ietf.org
> > Cc: mmusic@ietf.org; Xavier De Foy <Xavier.DeFoy@InterDigital.com>
> > Subject: Re: [MMUSIC] draft-hsyang-avtcore-rtp-haptics-02: Needs to
> register
> > "haptics" as an SDP <media>
> >
> > [Some people who received this message don't often get email from
> > hyunsik.yang=40interdigital.com@dmarc.ietf.org. Learn why this is
> important
> > at https://aka.ms/LearnAboutSenderIdentification ]
> >
> > Hello Jonathan!
> >
> > First of all, Thanks for reviewing our draft and sharing feedback.
> >
> > After our presentation during the IETF 118 meeting, we realized that the
> > 'haptics' Top-level Media Type
> > (https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatat
> > racker.ietf.org%2Fdoc%2Fdraft-ietf-mediaman-
> > haptics%2F&data=05%7C02%7Cchrister.holmberg%40ericsson.com%7C4a91
> > ee75e14f47a8b76608dc43708ea5%7C92e84cebfbfd47abbe52080c6b87953f
> > %7C0%7C0%7C638459397909128782%7CUnknown%7CTWFpbGZsb3d8eyJW
> > IjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7
> > C0%7C%7C%7C&sdata=d99fvcbNTS3Kqs8FkscBCPMD0Zy%2F6%2BdFZ%2B7i
> > 4u1JB9w%3D&reserved=0) was actually registering the haptic top-level type
> > and multiple haptic subtypes (including HMPG) with IANA. That is why we
> > modified the draft to update the HMPG subtype registration with IANA (in
> > section 6) and refer to the mediaman draft.
> >
> > Please let us know if there are any issues with this approach. It's
> based on our
> > best guess, but we may miss something.
> > Thanks
> > Best regards
> >
> > -----Original Message-----
> > From: Jonathan Lennox <jonathan.lennox@8x8.com>
> > Sent: Tuesday, March 12, 2024 5:25 PM
> > To: IETF AVTCore WG <avt@ietf.org>; draft-hsyang-avtcore-rtp-
> > haptics@ietf.org
> > Cc: mmusic@ietf.org
> > Subject: draft-hsyang-avtcore-rtp-haptics-02: Needs to register
> "haptics" as an
> > SDP <media>
> >
> > Hi - I’ve read over the rtp-haptics draft, and wanted to send in e-mail
> one
> > comment I’ve made verbally in meetings (but probably not too coherently):
> >
> > This draft also needs to register the SDP <media> value “haptics”, so
> > “m=haptics” can be sent in SDP.
> >
> > See RFC 8866 section 8.2 (specifically 8.2.2) for the details on how
> this is
> > done; see also RFC 6466 which registered “image” as an SDP <media>
> > (though that was done under the previous version of the process from RFC
> > 4566, which was slightly different).
> >
> > I don’t see any reason this registration can’t be done as part of the
> current
> > draft, but I’ve cc’d mmusic to keep that group aware that this is
> happening.
> >
> > --
> > Jonathan Lennox (as an individual)
> >
> > _______________________________________________
> > mmusic mailing list
> > mmusic@ietf.org
> > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.i
> > etf.org%2Fmailman%2Flistinfo%2Fmmusic&data=05%7C02%7Cchrister.holm
> > berg%40ericsson.com%7C4a91ee75e14f47a8b76608dc43708ea5%7C92e84c
> > ebfbfd47abbe52080c6b87953f%7C0%7C0%7C638459397909152140%7CUnk
> > nown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6I
> > k1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=IpQGbWcbFncI%2Biqp
> > ZRlgGMdHp2zKDyKTeS7HPiuSrAs%3D&reserved=0
>