draft-hsyang-avtcore-rtp-haptics-02.txt		draft-hsyang-avtcore-rtp-haptics-03.txt
	avtcore HS Yang		avtcore HS Yang
	Internet-Draft X. de Foy		Internet-Draft X. de Foy
	Intended status: Standards Track InterDigital		Intended status: Standards Track InterDigital
	Expires: 5 September 2024 4 March 2024		Expires: 26 September 2024 25 March 2024
	RTP Payload for Haptics		RTP Payload for Haptics
	draft-hsyang-avtcore-rtp-haptics-02		draft-hsyang-avtcore-rtp-haptics-03
	Abstract		Abstract
	This memo describes an RTP payload format for the MPEG-I haptic data.		This memo describes an RTP payload format for the MPEG-I haptic data.
	A haptic media stream is composed of MIHS units including a		A haptic media stream is composed of MIHS units including a
	MIHS(MPEG-I Haptic Stream) unit header and zero or more MIHS packets.		MIHS(MPEG-I Haptic Stream) unit header and zero or more MIHS packets.
	The RTP payload header format allows for packetization of a MIHS unit		The RTP payload header format allows for packetization of a MIHS unit
	in an RTP packet payload as well as fragmentation of a MIHS unit into		in an RTP packet payload as well as fragmentation of a MIHS unit into
	multiple RTP packets.		multiple RTP packets.
	skipping to change at page 1, line 35 ¶		skipping to change at page 1, line 35 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at https://datatracker.ietf.org/drafts/current/.		Drafts is at https://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on 5 September 2024.		This Internet-Draft will expire on 26 September 2024.
	Copyright Notice		Copyright Notice
	Copyright (c) 2024 IETF Trust and the persons identified as the		Copyright (c) 2024 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents (https://trustee.ietf.org/		Provisions Relating to IETF Documents (https://trustee.ietf.org/
	license-info) in effect on the date of publication of this document.		license-info) in effect on the date of publication of this document.
	Please review these documents carefully, as they describe your rights		Please review these documents carefully, as they describe your rights
	skipping to change at page 2, line 23 ¶		skipping to change at page 2, line 23 ¶
	5. Payload format for haptics . . . . . . . . . . . . . . . . . 5		5. Payload format for haptics . . . . . . . . . . . . . . . . . 5
	5.1. RTP header Usage . . . . . . . . . . . . . . . . . . . . 5		5.1. RTP header Usage . . . . . . . . . . . . . . . . . . . . 5
	5.2. Payload Header . . . . . . . . . . . . . . . . . . . . . 6		5.2. Payload Header . . . . . . . . . . . . . . . . . . . . . 6
	5.3. Payload Structures . . . . . . . . . . . . . . . . . . . 7		5.3. Payload Structures . . . . . . . . . . . . . . . . . . . 7
	5.3.1. Single Unit Payload Structure . . . . . . . . . . . . 8		5.3.1. Single Unit Payload Structure . . . . . . . . . . . . 8
	5.3.2. Fragmented Unit Payload Structure . . . . . . . . . . 8		5.3.2. Fragmented Unit Payload Structure . . . . . . . . . . 8
	5.4. MIHS Units Transmission Considerations . . . . . . . . . 10		5.4. MIHS Units Transmission Considerations . . . . . . . . . 10
	6. Payload Format Parameters . . . . . . . . . . . . . . . . . . 10		6. Payload Format Parameters . . . . . . . . . . . . . . . . . . 10
	6.1. Media Type Registration Update . . . . . . . . . . . . . 10		6.1. Media Type Registration Update . . . . . . . . . . . . . 10
	6.2. Optional Parameters Definition . . . . . . . . . . . . . 11		6.2. Optional Parameters Definition . . . . . . . . . . . . . 11
	7. SDP Considerations . . . . . . . . . . . . . . . . . . . . . 12		6.3. SDP Parameter Registration . . . . . . . . . . . . . . . 12
	7.1. SDP Offer/Answer Considerations . . . . . . . . . . . . . 13		7. SDP Considerations . . . . . . . . . . . . . . . . . . . . . 13
	7.2. Declarative SDP considerations . . . . . . . . . . . . . 14		7.1. SDP Offer/Answer Considerations . . . . . . . . . . . . . 14
	8. Congestion control consideration . . . . . . . . . . . . . . 14		7.2. Declarative SDP considerations . . . . . . . . . . . . . 15
			8. Congestion control consideration . . . . . . . . . . . . . . 15
	9. Security Considerations . . . . . . . . . . . . . . . . . . . 15		9. Security Considerations . . . . . . . . . . . . . . . . . . . 15
	10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16		10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
	11. References . . . . . . . . . . . . . . . . . . . . . . . . . 16		11. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
	11.1. Normative References . . . . . . . . . . . . . . . . . . 16		11.1. Normative References . . . . . . . . . . . . . . . . . . 17
	11.2. Informative References . . . . . . . . . . . . . . . . . 16		11.2. Informative References . . . . . . . . . . . . . . . . . 17
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
	1. Introduction		1. Introduction
	Haptics provides users with tactile effects in addition to audio and		Haptics provides users with tactile effects in addition to audio and
	video, allowing them to experience sensory immersion. Haptic data is		video, allowing them to experience sensory immersion. Haptic data is
	mainly transmitted to devices that act as actuators and provides them		mainly transmitted to devices that act as actuators and provides them
	with information to operate according to the values defined in haptic		with information to operate according to the values defined in haptic
	effects. The IETF is registering haptics as a primary media type		effects. The IETF is registering haptics as a primary media type
	akin to audio and video [I-D.ietf-mediaman-haptics].		akin to audio and video [I-D.ietf-mediaman-haptics].
	skipping to change at page 10, line 35 ¶		skipping to change at page 10, line 35 ¶
	resources. Since, from a receiver standpoint, a missed MIHS unit may		resources. Since, from a receiver standpoint, a missed MIHS unit may
	originate from a not-sent silent unit, or a lost packet, a sender MAY		originate from a not-sent silent unit, or a lost packet, a sender MAY
	send one, or a few, MIHS silent units at the beginning of a haptic		send one, or a few, MIHS silent units at the beginning of a haptic
	silence. If a media receiver receives a MIHS silent unit, the		silence. If a media receiver receives a MIHS silent unit, the
	receiver SHOULD assume that silence is intended until the reception		receiver SHOULD assume that silence is intended until the reception
	of a non-silent MIHS unit. This can reduce the number of false		of a non-silent MIHS unit. This can reduce the number of false
	detection of lost RTP packets by the decoder.		detection of lost RTP packets by the decoder.
	6. Payload Format Parameters		6. Payload Format Parameters
			This section describes payload format parameters. Section 6.1
			updates the 'haptics' Media Type Registration and Section 6.2
			specifies new optional parameters. Section 6.3 further registers a
			new token in the media sub-registry of the Session Description
			Protocols (SDP) Parameters registry.
			6.1. Media Type Registration Update
	This memo updates the 'hmpg' haptic subtype defined in section 4.3.3		This memo updates the 'hmpg' haptic subtype defined in section 4.3.3
	of [I-D.ietf-mediaman-haptics] for use with the MPEG-I haptics		of [I-D.ietf-mediaman-haptics] for use with the MPEG-I haptics
	streamable binary coding format described in ISO/IEC DIS 23090-31:		streamable binary coding format described in ISO/IEC DIS 23090-31:
	Haptics coding [ISO.IEC.23090-31]. This memo especially defines		Haptics coding [ISO.IEC.23090-31]. This memo especially defines
	optional parameters for this type in Section 6.2. A mapping of the		optional parameters for this type in Section 6.2. A mapping of the
	parameters into the Session Description Protocol (SDP) [RFC8866] is		parameters into the Session Description Protocol (SDP) [RFC8866] is
	also provided for applications that use SDP. Equivalent parameters		also provided for applications that use SDP. Equivalent parameters
	could be defined elsewhere for use with control protocols that do not		could be defined elsewhere for use with control protocols that do not
	use SDP. The receiver MUST ignore any parameter unspecified in this		use SDP. The receiver MUST ignore any parameter unspecified in this
	memo.		memo.
	6.1. Media Type Registration Update
	The following entries identify the media type being updated:		The following entries identify the media type being updated:
	Type name: haptics		Type name: haptics
	Subtype name: hmpg		Subtype name: hmpg
	The following entries are replaced by this memo:		The following entries are replaced by this memo:
	Optional parameters: see section 6.2 of RFC XXX (note to RFC editor:		Optional parameters: see section 6.2 of RFC XXX (note to RFC editor:
	replace with this RFC's number).		replace with this RFC's number).
	Person & email address to contact for further information: Yeshwant		Person & email address to contact for further information: Yeshwant
	Muthusamy (yeshwant@yeshvik.com) and Hyunsik Yang		Muthusamy (yeshwant@yeshvik.com) and Hyunsik Yang
	(hyunsik.yang@interdigital.com)		(hyunsik.yang@interdigital.com)
	6.2. Optional Parameters Definition		6.2. Optional Parameters Definition
	skipping to change at page 12, line 44 ¶		skipping to change at page 12, line 44 ¶
	_hmpg-dvctypes_ indicates, using a coma-separated list, the types of		_hmpg-dvctypes_ indicates, using a coma-separated list, the types of
	actuators. The device type is defined in [ISO.IEC.23090-31]:		actuators. The device type is defined in [ISO.IEC.23090-31]:
	MPEG_haptics.reference_device object.type is a string which may in		MPEG_haptics.reference_device object.type is a string which may in
	the initial release of the specifications hold values among "LRA",		the initial release of the specifications hold values among "LRA",
	"VCA", "ERM", "Piezo" or "Unknown".		"VCA", "ERM", "Piezo" or "Unknown".
	_hmpg-silencesupp_ indicates whether silence suppression should be		_hmpg-silencesupp_ indicates whether silence suppression should be
	used (1) or not (0). The default value shall be 1.		used (1) or not (0). The default value shall be 1.
			6.3. SDP Parameter Registration
			This memo registers an 'haptics' token in the media sub-registry of
			the Session Description Protocols (SDP) Parameters registry. This
			registration contains the required information elements outlined in
			the SDP registration procedure defined in section 8.2 of [RFC8866].
			(1) Contact Information:
			Name: Hyunsik Yang
			Email: hyunsikyang@interdigital.com
			(2) Name being registered (as it will appear in SDP): haptics
			(3) Long-form name in English: haptics
			(4) Type of name ('media', 'proto', 'fmt', 'bwtype', 'nettype', or
			'addrtype'): media
			(5) Purpose of the registered name:
			The 'haptics' media type for the Session Description Protocol
			is used to describe a media stream whose content can be
			rendered as touch-related sensations.
			The media subtype further describes the specific
			format of the haptics stream. The 'haptics' media type for
			SDP is used to establish haptics media streams.
			(6) Specification for the registered name: RFC XXXX
			RFC Editor Note: Replace RFC XXXX with the published RFC number.
	7. SDP Considerations		7. SDP Considerations
	The mapping of above defined payload format media type to the		The mapping of above defined payload format media type to the
	corresponding fields in the Session Description Protocol (SDP) is		corresponding fields in the Session Description Protocol (SDP) is
	done according to [RFC8866].		done according to [RFC8866].
	The media name in the "m=" line of SDP MUST be haptics.		The media name in the "m=" line of SDP MUST be haptics.
	The encoding name in the "a=rtpmap" line of SDP MUST be hmpg		The encoding name in the "a=rtpmap" line of SDP MUST be hmpg
	The clock rate in the "a=rtpmap" line may be any sampling rate,		The clock rate in the "a=rtpmap" line may be any sampling rate,
	typically 8000.		typically 8000.
	The OPTIONAL parameters (defined in Section 6.2), when present, MUST		The OPTIONAL parameters (defined in Section 6.2), when present, MUST
	be included in the "a=fmtp" line of SDP. This is expressed as a		be included in the "a=fmtp" line of SDP. This is expressed as a
	media type string, in the form of a semicolon-separated list of		media type string, in the form of a semicolon-separated list of
	parameter=value pairs.		parameter=value pairs.
	An example of media representation corresponding to the hmpg RTP		An example of media representation corresponding to the hmpg RTP
	payload in SDP is as follows:		payload in SDP is as follows:
	skipping to change at page 16, line 23 ¶		skipping to change at page 17, line 8 ¶
	(MANE) from performing media-aware operations other than discarding		(MANE) from performing media-aware operations other than discarding
	complete packets. In the case of confidentiality protection, it will		complete packets. In the case of confidentiality protection, it will
	even be prevented from discarding packets in a media-aware way. To		even be prevented from discarding packets in a media-aware way. To
	be allowed to perform such operations, a MANE is required to be a		be allowed to perform such operations, a MANE is required to be a
	trusted entity that is included in the security context		trusted entity that is included in the security context
	establishment.		establishment.
	10. IANA Considerations		10. IANA Considerations
	This memo updates the media type registration of haptics/hmpg with		This memo updates the media type registration of haptics/hmpg with
	IANA, in Section 6.		IANA, in Section 6.1.
	11. References		11. References
	11.1. Normative References		11.1. Normative References
	[ISO.IEC.23090-31]		[ISO.IEC.23090-31]
	ISO/IEC, "Text of ISO/IEC FDIS 23090-31 MPEG Haptics		ISO/IEC, "Text of ISO/IEC FDIS 23090-31 MPEG Haptics
	Coding", ISO/IEC 23090-31, 2024,		Coding", ISO/IEC 23090-31, 2024,
	<https://isotc.iso.org/livelink/livelink/open/		<https://isotc.iso.org/livelink/livelink/open/
	jtc1sc29wg7>.		jtc1sc29wg7>.
End of changes. 11 change blocks.
	14 lines changed or deleted		55 lines changed or added
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/