< draft-ietf-payload-tetra-01.txt		draft-ietf-payload-tetra-02.txt >
	payload Reisenbauer		payload Reisenbauer
	Internet-Draft Frequentis		Internet-Draft Frequentis
	Intended status: Standards Track Brandhuber		Intended status: Standards Track Brandhuber
	Expires: April 26, 2019 eurofunk		Expires: July 27, 2019 eurofunk
	Hagedorn		Hagedorn
	Hagedorn		Hagedorn
	Hoehnsch		Hoehnsch
	T-Systems		T-Systems
	Wenk		Wenk
	Frequentis		Frequentis
	October 23, 2018		January 23, 2019
	RTP Payload Format for the TETRA Audio Codec		RTP Payload Format for the TETRA Audio Codec
	draft-ietf-payload-tetra-01		draft-ietf-payload-tetra-02
	Abstract		Abstract
	This document specifies a Real-time Transport Protocol (RTP) payload		This document specifies a Real-time Transport Protocol (RTP) payload
	format for TETRA encoded speech signals. The payload format is		format for TETRA encoded speech signals. The payload format is
	designed to be able to interoperate with existing TETRA transport		designed to be able to interoperate with existing TETRA transport
	formats on non-IP networks. A media type registration is included,		formats on non-IP networks. A media type registration is included,
	specifying the use of the RTP payload format and the storage format.		specifying the use of the RTP payload format and the storage format.
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 41 ¶		skipping to change at page 1, line 41 ¶
	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 April 26, 2019.		This Internet-Draft will expire on July 27, 2019.
	Copyright Notice		Copyright Notice
	Copyright (c) 2018 IETF Trust and the persons identified as the		Copyright (c) 2019 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		Provisions Relating to IETF Documents
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	skipping to change at page 2, line 37 ¶		skipping to change at page 2, line 37 ¶
	4.3.7. S: Spare (7 bits) . . . . . . . . . . . . . . . . . . 7		4.3.7. S: Spare (7 bits) . . . . . . . . . . . . . . . . . . 7
	4.4. Payload Data . . . . . . . . . . . . . . . . . . . . . . 7		4.4. Payload Data . . . . . . . . . . . . . . . . . . . . . . 7
	5. Payload example . . . . . . . . . . . . . . . . . . . . . . . 8		5. Payload example . . . . . . . . . . . . . . . . . . . . . . . 8
	6. Congestion Control Considerations . . . . . . . . . . . . . . 8		6. Congestion Control Considerations . . . . . . . . . . . . . . 8
	7. Payload Format Parameters . . . . . . . . . . . . . . . . . . 9		7. Payload Format Parameters . . . . . . . . . . . . . . . . . . 9
	7.1. Media Type Definition . . . . . . . . . . . . . . . . . . 9		7.1. Media Type Definition . . . . . . . . . . . . . . . . . . 9
	8. Mapping to SDP . . . . . . . . . . . . . . . . . . . . . . . 10		8. Mapping to SDP . . . . . . . . . . . . . . . . . . . . . . . 10
	8.1. Offer/Answer Considerations . . . . . . . . . . . . . . . 11		8.1. Offer/Answer Considerations . . . . . . . . . . . . . . . 11
	8.2. Declarative SDP Considerations . . . . . . . . . . . . . 11		8.2. Declarative SDP Considerations . . . . . . . . . . . . . 11
	9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11		9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
	10. Security Considerations . . . . . . . . . . . . . . . . . . . 11		10. Security Considerations . . . . . . . . . . . . . . . . . . . 12
	11. References . . . . . . . . . . . . . . . . . . . . . . . . . 12		11. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
	11.1. Normative References . . . . . . . . . . . . . . . . . . 12		11.1. Normative References . . . . . . . . . . . . . . . . . . 12
	11.2. Informative References . . . . . . . . . . . . . . . . . 13		11.2. Informative References . . . . . . . . . . . . . . . . . 13
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
	1. Introduction		1. Introduction
	This document specifies the payload format for packetization of		This document specifies the payload format for packetization of
	TErrestial Trunked RAdio (TETRA) encoded speech signals		TErrestial Trunked RAdio (TETRA) encoded speech signals
	[ETSI-TETRA-Codec] into the Real-time Transport Protocol (RTP)		[ETSI-TETRA-Codec] into the Real-time Transport Protocol (RTP)
	[RFC3550]. The payload format supports transmission of multiple		[RFC3550]. The payload format supports transmission of multiple
	channels, multiple frames per payload, robustness against packet		frames per payload, robustness against packet loss, and
	loss, and interoperation with existing TETRA transport formats on		interoperation with existing TETRA transport formats on non-IP
	non-IP networks, as described in Section Section 3.		networks, as described in Section Section 3.
	The payload format itself is specified in Section Section 4.		The payload format itself is specified in Section Section 4.
	2. Conventions Used In This Document		2. Conventions Used In This Document
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in [RFC2119] when they		document are to be interpreted as described in [RFC2119] when they
	appear in ALL CAPS. These words may also appear in this document in		appear in ALL CAPS. These words may also appear in this document in
	lower case as plain English words, absent their normative meanings.		lower case as plain English words, absent their normative meanings.
	skipping to change at page 7, line 38 ¶		skipping to change at page 7, line 38 ¶
	+-------+-----------------------------------------------------------+		+-------+-----------------------------------------------------------+
	| value | relevance |		| value | relevance |
	+-------+-----------------------------------------------------------+		+-------+-----------------------------------------------------------+
	| 00 | no audio signal relevance (level ? -72 dBm0) |		| 00 | no audio signal relevance (level ? -72 dBm0) |
	| 01 | low audio signal relevance (-52dBm0 ? level > -72dBm0) |		| 01 | low audio signal relevance (-52dBm0 ? level > -72dBm0) |
	| 10 | medium audio signal relevance (-32dBm0 ? level > -52dBm0) |		| 10 | medium audio signal relevance (-32dBm0 ? level > -52dBm0) |
	| 11 | high audio signal relevance (0dBm0 ? level > -32dBm0) |		| 11 | high audio signal relevance (0dBm0 ? level > -32dBm0) |
	+-------+-----------------------------------------------------------+		+-------+-----------------------------------------------------------+
			NOTE: Receiver SHOULD consider stolen or erroneous blocks as not
			available for audio decoding as indicated by control bits independent
			of audio signal relevance bits.
	4.3.7. S: Spare (7 bits)		4.3.7. S: Spare (7 bits)
	The S bits bits are reserved for future use and set to "0" currently.		The S bits bits are reserved for future use and set to "0" currently.
	4.4. Payload Data		4.4. Payload Data
	Reference [ETSI-TETRA-ISI] contains the definition for the generation		Reference [ETSI-TETRA-ISI] contains the definition for the generation
	of the codec data. Data bits D1..D137 in chapter 8 correspond to the		of the codec data. Data bits D1..D137 in chapter 8 correspond to the
	"Bit number in speech frame" row of table 4 of [ETSI-TETRA-ISI].		"Bit number in speech frame" row of table 4 of [ETSI-TETRA-ISI].
	skipping to change at page 9, line 4 ¶		skipping to change at page 9, line 7 ¶
	UDP layer RFC8085 [RFC8085] and MAY also implement a transport		UDP layer RFC8085 [RFC8085] and MAY also implement a transport
	circuit breaker RFC8083 [RFC8083]. Work in the RMCAT working group		circuit breaker RFC8083 [RFC8083]. Work in the RMCAT working group
	[RMCAT] describes the interactions and conceptual interfaces		[RMCAT] describes the interactions and conceptual interfaces
	necessary between the application components that relate to		necessary between the application components that relate to
	congestion control, including the RTP layer, the higher-level media		congestion control, including the RTP layer, the higher-level media
	codec control layer, and the lower-level transport interface, as well		codec control layer, and the lower-level transport interface, as well
	as components dedicated to congestion control functions.		as components dedicated to congestion control functions.
	Congestion control for RTP SHALL be used in accordance with RFC 3550		Congestion control for RTP SHALL be used in accordance with RFC 3550
	[RFC3550], and with any applicable RTP profile; e.g., RFC 3551		[RFC3550], and with any applicable RTP profile; e.g., RFC 3551
	[RFC3551]. An additional requirement if best-effort service is being		[RFC3551]. An additional requirement if best-effort service is being
	used is: users of this payload format MUST monitor packet loss to		used is: users of this payload format MUST monitor packet loss to
	ensure that the packet loss rate is within acceptable parameters.		ensure that the packet loss rate is within acceptable parameters.
	7. Payload Format Parameters		7. Payload Format Parameters
	This RTP payload format is identified using one media subtype (audio/		This RTP payload format is identified using one media subtype (audio/
	TETRA) which is registered in accordance with RFC 4855 [RFC4855] and		TETRA) which is registered in accordance with RFC 4855 [RFC4855] and
	per media type registration template from RFC 6838 [RFC6838].		per media type registration template from RFC 6838 [RFC6838].
	7.1. Media Type Definition		7.1. Media Type Definition
	The media type for the TETRA codec is expected to be allocated from		The media type for the TETRA codec is expected to be allocated from
	the IETF tree once this draft turns into an RFC. This media type		the IETF tree once this draft turns into an RFC. This media type
	registration covers both real-time transfer via RTP and non-real-time		registration covers both real-time transfer via RTP and non-real-time
	transfers via stored files.		transfers via stored files.
	Media Type name:		Type name:
	audio		audio
	Media Subtype name:		Subtype name:
	TETRA		TETRA
	Required parameters:		Required parameters:
	none		none
	Optional parameters:		Optional parameters:
			These parameters apply to RTP transfer only.
	These parameters apply to RTP transfer only.		* maxptime: The maximum amount of media which can be encapsulated
			in a payload packet, expressed as time in milliseconds. The
	maxptime:		time is calculated as the sum of the time that the media
	The maximum amount of media which can be encapsulated in a payload		present in the packet represents. The time SHOULD be an
	packet, expressed as time in milliseconds. The time is calculated		integer multiple of the frame size. If this parameter is not
	as the sum of the time that the media present in the packet		present, the sender MAY encapsulate any number of speech frames
	represents. The time SHOULD be an integer multiple of the frame		into one RTP packet.
	size. If this parameter is not present, the sender MAY		* ptime: see RFC 4566 [RFC4566].
	encapsulate any number of speech frames into one RTP packet.		Encoding considerations:
	ptime:		This media type is framed and binary according Section 4.8 of RFC
	see RFC 4566 [RFC4566].		6838 [RFC6838].
	Security considerations:		Security considerations:
	See Section Section 10 of RFC XXXX. [RFC Editor: Upon publication		See Section Section 10 of RFC XXXX. [RFC Editor: Upon publication
	as an RFC, please replace "XXXX" with the number assigned to this		as an RFC, please replace "XXXX" with the number assigned to this
	document and remove this note.]		document and remove this note.]
	Interoperability considerations:		Interoperability considerations: N/A
	Published specification:		Published specification:
			RFC XXXX [RFC Editor: Upon publication as an RFC, please replace
			"XXXX" with the number assigned to this document and remove this
			note.]
	Applications that use this media type:		Applications that use this media type:
			This media type is used in applications needing transport or
			storage of encoded voice. Some examples include; Voice over IP,
			streaming media, voice messaging, and voice recording on recording
			systems.
	This media type is used in applications needing transport or storage		Additional Information:
	of encoded voice. Some examples include; Voice over IP, streaming
	media, voice messaging, and voice recording on recording systems.		- Deprecated alias names for this type: N/A
			- Magic number(s): N/A
			- File extension(s): N/A
			- Macintosh file type code(s): N/A
			Person & email address to contact for further information:
			Andreas Reisenbauer <mailto:andreas.reisenbauer@frequentis.com>
			IETF Payload Working Group <mailto:payload@ietf.org>
	Intended usage:		Intended usage:
	COMMON		COMMON
			Restrictions on usage:
			This media subtype depends on RTP framing and hence is only
			defined for transfer via RTP RFC 3550 [RFC3550]. Transport within
			other framing protocols is not defined at this time.
			Author:
			Andreas Reisenbauer <mailto:andreas.reisenbauer@frequentis.com>
			Change controller:
			The IETF PAYLOAD Working Group, or other party as designated by
			the IESG.
	8. Mapping to SDP		8. Mapping to SDP
	The information carried in the media type specification has a		The information carried in the media type specification has a
	specific mapping to fields in the Session Description Protocol		specific mapping to fields in the Session Description Protocol
	[RFC4566], which is commonly used to describe RTP sessions. When SDP		[RFC4566], which is commonly used to describe RTP sessions. When SDP
	is used to specify sessions employing the TETRA codec, the mapping is		is used to specify sessions employing the TETRA codec, the mapping is
	as follows:		as follows:
	Media Type name:		Media Type name:
End of changes. 20 change blocks.
	28 lines changed or deleted		53 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/