rfc8866v14.txt		rfc8866.txt
	Internet Engineering Task Force (IETF) A. Begen		Internet Engineering Task Force (IETF) A. Begen
	Request for Comments: 8866 Networked Media		Request for Comments: 8866 Networked Media
	Obsoletes: 4566 P. Kyzivat		Obsoletes: 4566 P. Kyzivat
	Category: Standards Track		Category: Standards Track
	ISSN: 2070-1721 C. Perkins		ISSN: 2070-1721 C. Perkins
	University of Glasgow		University of Glasgow
	M. Handley		M. Handley
	UCL		UCL
	September 2020		January 2021
	SDP: Session Description Protocol		SDP: Session Description Protocol
	Abstract		Abstract
	This memo defines the Session Description Protocol (SDP). SDP is		This memo defines the Session Description Protocol (SDP). SDP is
	intended for describing multimedia sessions for the purposes of		intended for describing multimedia sessions for the purposes of
	session announcement, session invitation, and other forms of		session announcement, session invitation, and other forms of
	multimedia session initiation. This document obsoletes RFC 4566.		multimedia session initiation. This document obsoletes RFC 4566.
	skipping to change at line 37 ¶		skipping to change at line 37 ¶
	received public review and has been approved for publication by the		received public review and has been approved for publication by the
	Internet Engineering Steering Group (IESG). Further information on		Internet Engineering Steering Group (IESG). Further information on
	Internet Standards is available in Section 2 of RFC 7841.		Internet Standards is available in Section 2 of RFC 7841.
	Information about the current status of this document, any errata,		Information about the current status of this document, any errata,
	and how to provide feedback on it may be obtained at		and how to provide feedback on it may be obtained at
	https://www.rfc-editor.org/info/rfc8866.		https://www.rfc-editor.org/info/rfc8866.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 IETF Trust and the persons identified as the		Copyright (c) 2021 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 line 1881 ¶		skipping to change at line 1881 ¶
	SDP MUST NOT be used to convey keying material (e.g., using the		SDP MUST NOT be used to convey keying material (e.g., using the
	"a=crypto:" attribute [RFC4568]) unless it can be guaranteed that the		"a=crypto:" attribute [RFC4568]) unless it can be guaranteed that the
	channel over which the SDP is delivered is both private and		channel over which the SDP is delivered is both private and
	authenticated.		authenticated.
	8. IANA Considerations		8. IANA Considerations
	8.1. The "application/sdp" Media Type		8.1. The "application/sdp" Media Type
	One media type registration from [RFC4566] is to be updated, as		One media type registration from [RFC4566] has been updated, as
	defined below.		defined below.
	Type name: application		Type name: application
	Subtype name: sdp		Subtype name: sdp
	Required parameters: None.		Required parameters: None.
	Optional parameters: None.		Optional parameters: None.
	skipping to change at line 1939 ¶		skipping to change at line 1939 ¶
	8.2. Registration of SDP Parameters with IANA		8.2. Registration of SDP Parameters with IANA
	This document specifies IANA parameter registries for six named SDP		This document specifies IANA parameter registries for six named SDP
	subfields. Using the terminology in the SDP specification Augmented		subfields. Using the terminology in the SDP specification Augmented
	Backus-Naur Form (ABNF), they are <media>, <proto>, <attribute-name>,		Backus-Naur Form (ABNF), they are <media>, <proto>, <attribute-name>,
	<bwtype>, <nettype>, and <addrtype>.		<bwtype>, <nettype>, and <addrtype>.
	This document also replaces and updates the definitions of all those		This document also replaces and updates the definitions of all those
	parameters previously defined by [RFC4566].		parameters previously defined by [RFC4566].
	IANA: Please change all references to RFC4566 in these registries to		IANA has changed all references to RFC 4566 in these registries to
	instead refer to this document.		instead refer to this document.
	The contact name and email address for all parameters registered in		The contact name and email address for all parameters registered in
	this document is:		this document is:
	The IETF MMUSIC working group <mmusic@ietf.org> or its successor		The IETF MMUSIC working group <mmusic@ietf.org> or its successor
	as designated by the IESG.		as designated by the IESG.
	All of these registries have a common format:		All of these registries have a common format:
	skipping to change at line 2093 ¶		skipping to change at line 2093 ¶
	| Type | SDP Name | Usage Level | Mux Category | Reference |		| Type | SDP Name | Usage Level | Mux Category | Reference |
	+===========+==========+================+==============+===========+		+===========+==========+================+==============+===========+
	| attribute | lang | session, media | TRANSPORT | [RFC8866] |		| attribute | lang | session, media | TRANSPORT | [RFC8866] |
	| | | | | [RFC8859] |		| | | | | [RFC8859] |
	+-----------+----------+----------------+--------------+-----------+		+-----------+----------+----------------+--------------+-----------+
	Table 5: <attribute-name> Registry Example		Table 5: <attribute-name> Registry Example
	This one <attribute-name> registry combines all of the previous		This one <attribute-name> registry combines all of the previous
	usage-level-specific "att-field" registries, including updates made		usage-level-specific "att-field" registries, including updates made
	by [RFC8859]. IANA is requested to do the necessary reformatting.		by [RFC8859], and renames the "att-field" registry to the "attribute-
			name (formerly "att-field")" registry. IANA has completed the
			necessary reformatting.
	Section 6 of this document replaces the initial set of attribute		Section 6 of this document replaces the initial set of attribute
	definitions made by [RFC4566]. IANA is requested to update the		definitions made by [RFC4566]. IANA has updated the registry
	registry accordingly.		accordingly.
	Documents can define new attributes and can also extend the		Documents can define new attributes and can also extend the
	definitions of previously defined attributes.		definitions of previously defined attributes.
	8.2.4.1. New Attributes		8.2.4.1. New Attributes
	New attribute registrations are accepted according to the		New attribute registrations are accepted according to the
	"Specification Required" policy of [RFC8126], provided that the		"Specification Required" policy of [RFC8126], provided that the
	specification includes the following information:		specification includes the following information:
	skipping to change at line 2251 ¶		skipping to change at line 2253 ¶
	[RFC8859].		[RFC8859].
	The format of the <bwtype> registry is:		The format of the <bwtype> registry is:
	+======+==========+==============+===========+		+======+==========+==============+===========+
	| Type | SDP Name | Mux Category | Reference |		| Type | SDP Name | Mux Category | Reference |
	+======+==========+==============+===========+		+======+==========+==============+===========+
	Table 6: Format of the <bwtype> Registry		Table 6: Format of the <bwtype> Registry
	IANA is requested to update the <bwtype> registry entries for the		IANA has updated the <bwtype> registry entries for the bandwidth
	bandwidth specifiers "CT" and "AS" with the definitions in		specifiers "CT" and "AS" with the definitions in Section 5.8 of this
	Section 5.8 of this memo (these definitions replace those in		memo (these definitions replace those in [RFC4566]).
	[RFC4566]).
	8.2.6. Network Types (<nettype>)		8.2.6. Network Types (<nettype>)
	Network type "IN", representing the Internet, is defined in		Network type "IN", representing the Internet, is defined in
	Section 5.2 and Section 5.7 of this memo (this definition replaces		Section 5.2 and Section 5.7 of this memo (this definition replaces
	that in [RFC4566]).		that in [RFC4566]).
	To enable SDP to reference a new non-Internet environment, a new		To enable SDP to reference a new non-Internet environment, a new
	network type (<nettype> subfield value) MUST be registered with IANA.		network type (<nettype> subfield value) MUST be registered with IANA.
	The registration is subject to the "RFC Required" policy of		The registration is subject to the "RFC Required" policy of
	skipping to change at line 2282 ¶		skipping to change at line 2283 ¶
	type and the address type(s) that may be used with it.		type and the address type(s) that may be used with it.
	The format of the <nettype> registry is:		The format of the <nettype> registry is:
	+======+==========+========================+===========+		+======+==========+========================+===========+
	| Type | SDP Name | Usable addrtype Values | Reference |		| Type | SDP Name | Usable addrtype Values | Reference |
	+======+==========+========================+===========+		+======+==========+========================+===========+
	Table 7: Format of the <nettype> Registry		Table 7: Format of the <nettype> Registry
	IANA is requested to update the <nettype> registry to this new		IANA has updated the <nettype> registry to this new format. The
	format. The following is the updated content of the registry:		following is the updated content of the registry:
	+=========+==========+========================+===========+		+=========+==========+========================+===========+
	| Type | SDP Name | Usable addrtype Values | Reference |		| Type | SDP Name | Usable addrtype Values | Reference |
	+=========+==========+========================+===========+		+=========+==========+========================+===========+
	| nettype | IN | IP4, IP6 | [RFC8866] |		| nettype | IN | IP4, IP6 | [RFC8866] |
	+---------+----------+------------------------+-----------+		+---------+----------+------------------------+-----------+
	| nettype | TN | RFC2543 | [RFC2848] |		| nettype | TN | RFC2543 | [RFC2848] |
	+---------+----------+------------------------+-----------+		+---------+----------+------------------------+-----------+
	| nettype | ATM | NSAP, GWID, E164 | [RFC3108] |		| nettype | ATM | NSAP, GWID, E164 | [RFC3108] |
	+---------+----------+------------------------+-----------+		+---------+----------+------------------------+-----------+
	skipping to change at line 2779 ¶		skipping to change at line 2780 ¶
	[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for		[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
	Writing an IANA Considerations Section in RFCs", BCP 26,		Writing an IANA Considerations Section in RFCs", BCP 26,
	RFC 8126, DOI 10.17487/RFC8126, June 2017,		RFC 8126, DOI 10.17487/RFC8126, June 2017,
	<https://www.rfc-editor.org/info/rfc8126>.		<https://www.rfc-editor.org/info/rfc8126>.
	[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC		[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
	2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,		2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
	May 2017, <https://www.rfc-editor.org/info/rfc8174>.		May 2017, <https://www.rfc-editor.org/info/rfc8174>.
	[RFC8859] Nandakumar, S., "A Framework for Session Description		[RFC8859] Nandakumar, S., "A Framework for Session Description
	Protocol (SDP) Attributes When Multiplexing",		Protocol (SDP) Attributes When Multiplexing", RFC 8859,
	DOI 10.17487/RFC8859, RFC 8859, July 2020,		DOI 10.17487/RFC8859, January 2021,
	<https://www.rfc-editor.org/info/rfc8859>.		<https://www.rfc-editor.org/info/rfc8859>.
	[RFC8864] Drage, K., Makaraju, M., Ejzak, R., Marcon, J., and R.		[RFC8864] Drage, K., Makaraju, M., Ejzak, R., Marcon, J., and R.
	Even, Ed., "SDP-based Data Channel Negotiation", RFC 8864,		Even, Ed., "Negotiation Data Channels Using the Session
	DOI 10.17487/RFC8864, July 2020,		Description Protocol (SDP)", RFC 8864,
	<https://www.rfc-editor.org/rfc/rfc8864>.		DOI 10.17487/RFC8864, January 2021,
			<https://www.rfc-editor.org/info/rfc8864>.
	11.2. Informative References		11.2. Informative References
	[ITU.H332.1998]		[ITU.H332.1998]
	International Telecommunication Union, "H.332 : H.323		International Telecommunication Union, "H.332 : H.323
	extended for loosely coupled conferences", ITU		extended for loosely coupled conferences", ITU
	Recommendation H.332, September 1998,		Recommendation H.332, September 1998,
	<https://www.itu.int/rec/T-REC-H.332-199809-I/en>.		<https://www.itu.int/rec/T-REC-H.332-199809-I/en>.
	[RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail		[RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
	skipping to change at line 2932 ¶		skipping to change at line 2934 ¶
	[RFC8445] Keranen, A., Holmberg, C., and J. Rosenberg, "Interactive		[RFC8445] Keranen, A., Holmberg, C., and J. Rosenberg, "Interactive
	Connectivity Establishment (ICE): A Protocol for Network		Connectivity Establishment (ICE): A Protocol for Network
	Address Translator (NAT) Traversal", RFC 8445,		Address Translator (NAT) Traversal", RFC 8445,
	DOI 10.17487/RFC8445, July 2018,		DOI 10.17487/RFC8445, July 2018,
	<https://www.rfc-editor.org/info/rfc8445>.		<https://www.rfc-editor.org/info/rfc8445>.
	[RFC8839] Petit-Huguenin, M., Nandakumar, S., Holmberg, C., Keränen,		[RFC8839] Petit-Huguenin, M., Nandakumar, S., Holmberg, C., Keränen,
	A., and R. Shpount, "Session Description Protocol (SDP)		A., and R. Shpount, "Session Description Protocol (SDP)
	Offer/Answer Procedures for Interactive Connectivity		Offer/Answer Procedures for Interactive Connectivity
	Establishment (ICE)", RFC 8839, DOI 10.17487/RFC8839, July		Establishment (ICE)", RFC 8839, DOI 10.17487/RFC8839,
	2020, <https://www.rfc-editor.org/info/rfc8839>.		January 2021, <https://www.rfc-editor.org/info/rfc8839>.
	[RFC8843] Holmberg, C., Alvestrand, H., and C. Jennings,		[RFC8843] Holmberg, C., Alvestrand, H., and C. Jennings,
	"Negotiating Media Multiplexing Using the Session		"Negotiating Media Multiplexing Using the Session
	Description Protocol (SDP)", RFC 8843,		Description Protocol (SDP)", RFC 8843,
	DOI 10.17487/RFC8843, July 2020,		DOI 10.17487/RFC8843, January 2021,
	<https://www.rfc-editor.org/info/rfc8843>.		<https://www.rfc-editor.org/info/rfc8843>.
	Acknowledgements		Acknowledgements
	Many people in the IETF Multiparty Multimedia Session Control		Many people in the IETF Multiparty Multimedia Session Control
	(MMUSIC) working group have made comments and suggestions		(MMUSIC) working group have made comments and suggestions
	contributing to this document.		contributing to this document.
	In particular, we would like to thank the following people who		In particular, we would like to thank the following people who
	contributed to the creation of this document or one of its		contributed to the creation of this document or one of its
End of changes. 12 change blocks.
	21 lines changed or deleted		23 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/