draft-ietf-mmusic-sdp-mux-attributes-11.txt		draft-ietf-mmusic-sdp-mux-attributes-12.txt
	Network Working Group S. Nandakumar		Network Working Group S. Nandakumar
	Internet-Draft Cisco		Internet-Draft Cisco
	Intended status: Standards Track January 4, 2016		Intended status: Standards Track January 14, 2016
	Expires: July 7, 2016		Expires: July 17, 2016
	A Framework for SDP Attributes when Multiplexing		A Framework for SDP Attributes when Multiplexing
	draft-ietf-mmusic-sdp-mux-attributes-11		draft-ietf-mmusic-sdp-mux-attributes-12
	Abstract		Abstract
	The Session Description Protocol (SDP) provides mechanisms to		The Session Description Protocol (SDP) provides mechanisms to
	describe attributes of multimedia sessions and of individual media		describe attributes of multimedia sessions and of individual media
	streams (e.g., Real-time Transport Protocol (RTP) sessions) within a		streams (e.g., Real-time Transport Protocol (RTP) sessions) within a
	multimedia session. Typically media associated with individual media		multimedia session. Typically media associated with individual media
	descriptions ("m=" lines) represent RTP sessions and are thus carried		descriptions ("m=" lines) represent RTP sessions and are thus carried
	over individual underlying transport layer flows. For scenarios		over individual underlying transport layer flows. For scenarios
	where SDP is used to negotiate the usage of single 5-tuple for		where SDP is used to negotiate the usage of single 5-tuple for
	skipping to change at page 1, line 45		skipping to change at page 1, line 45
	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 http://datatracker.ietf.org/drafts/current/.		Drafts is at http://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 July 7, 2016.		This Internet-Draft will expire on July 17, 2016.
	Copyright Notice		Copyright Notice
	Copyright (c) 2016 IETF Trust and the persons identified as the		Copyright (c) 2016 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
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://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
	described in the Simplified BSD License.		described in the Simplified BSD License.
	This document may contain material from IETF Documents or IETF
	Contributions published or made publicly available before November
	10, 2008. The person(s) controlling the copyright in some of this
	material may not have granted the IETF Trust the right to allow
	modifications of such material outside the IETF Standards Process.
	Without obtaining an adequate license from the person(s) controlling
	the copyright in such materials, this document may not be modified
	outside the IETF Standards Process, and derivative works of it may
	not be created outside the IETF Standards Process, except to format
	it for publication as an RFC or to translate it into languages other
	than English.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
	3. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . 6		3. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . 6
	4. SDP Attribute Analysis Framework . . . . . . . . . . . . . . 7		4. SDP Attribute Analysis Framework . . . . . . . . . . . . . . 6
	4.1. Category: NORMAL . . . . . . . . . . . . . . . . . . . . 7		4.1. Category: NORMAL . . . . . . . . . . . . . . . . . . . . 7
	4.2. Category: NOT RECOMMENDED . . . . . . . . . . . . . . . . 8		4.2. Category: NOT RECOMMENDED . . . . . . . . . . . . . . . . 7
	4.3. Category: IDENTICAL . . . . . . . . . . . . . . . . . . . 8		4.3. Category: IDENTICAL . . . . . . . . . . . . . . . . . . . 8
	4.4. Category: SUM . . . . . . . . . . . . . . . . . . . . . . 9		4.4. Category: SUM . . . . . . . . . . . . . . . . . . . . . . 8
	4.5. Category: TRANSPORT . . . . . . . . . . . . . . . . . . . 9		4.5. Category: TRANSPORT . . . . . . . . . . . . . . . . . . . 9
	4.6. Category: INHERIT . . . . . . . . . . . . . . . . . . . . 10		4.6. Category: INHERIT . . . . . . . . . . . . . . . . . . . . 10
	4.7. Category: IDENTICAL-PER-PT . . . . . . . . . . . . . . . 11		4.7. Category: IDENTICAL-PER-PT . . . . . . . . . . . . . . . 11
	4.8. Category: SPECIAL . . . . . . . . . . . . . . . . . . . . 12		4.8. Category: SPECIAL . . . . . . . . . . . . . . . . . . . . 12
	4.9. Category: TBD . . . . . . . . . . . . . . . . . . . . . . 12		4.9. Category: TBD . . . . . . . . . . . . . . . . . . . . . . 12
	5. Analysis of Existing Attributes . . . . . . . . . . . . . . . 12		5. Analysis of Existing Attributes . . . . . . . . . . . . . . . 12
	5.1. RFC4566: SDP . . . . . . . . . . . . . . . . . . . . . . 13		5.1. RFC4566: SDP . . . . . . . . . . . . . . . . . . . . . . 13
	5.2. RFC4585: RTP/AVPF . . . . . . . . . . . . . . . . . . . . 14		5.2. RFC4585: RTP/AVPF . . . . . . . . . . . . . . . . . . . . 14
	5.3. RFC5761: Multiplexing RTP and RTCP . . . . . . . . . . . 15		5.3. RFC5761: Multiplexing RTP and RTCP . . . . . . . . . . . 15
	5.4. RFC3312: Integration of Resource Management and SIP . . . 15		5.4. RFC3312: Integration of Resource Management and SIP . . . 15
	skipping to change at page 6, line 25		skipping to change at page 6, line 15
	2. Terminology		2. Terminology
	5-tuple: A collection of the following values: source address, source		5-tuple: A collection of the following values: source address, source
	port, destination address, destination port, and transport-layer		port, destination address, destination port, and transport-layer
	protocol.		protocol.
	3GPP: Third Generation Partnership Project; see http://www.3gpp.org		3GPP: Third Generation Partnership Project; see http://www.3gpp.org
	for more information about this organization.		for more information about this organization.
	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].		document are to be interpreted as described in [RFC2119].
	3. Motivation		3. Motivation
	The time and complications of setting up ICE [RFC5245] and Datagram		The time and complications of setting up ICE [RFC5245] and Datagram
	Transport Layer Security (DTLS) based Secure Real-time Transport		Transport Layer Security (DTLS) based Secure Real-time Transport
	Protocol (SRTP) [RFC5763] transports for use by RTP, and conservation		Protocol (SRTP) [RFC5763] transports for use by RTP, and conservation
	of ports (to avoid maintaining large number of Network Address		of ports (to avoid maintaining large number of Network Address
	Translator (NAT) bindings open, reduce time/ports needed for ICE to		Translator (NAT) bindings open, reduce time/ports needed for ICE to
	detect connectivity), forms a requirement to try and reduce the		detect connectivity), forms a requirement to try and reduce the
	skipping to change at page 63, line 45		skipping to change at page 63, line 45
	| | transport | | |		| | transport | | |
	| | | | |		| | | | |
	+-------+--------------------------------------+-------+------------+		+-------+--------------------------------------+-------+------------+
	RFC5432 Attribute Analysis		RFC5432 Attribute Analysis
	NOTE: A single Differentiated Services Code Point (DSCP) code point		NOTE: A single Differentiated Services Code Point (DSCP) code point
	per flow being multiplexed doesn't impact multiplexing since QOS		per flow being multiplexed doesn't impact multiplexing since QOS
	mechanisms are signaled/scoped per flow. For scenarios that involve		mechanisms are signaled/scoped per flow. For scenarios that involve
	having different DSCP code points for packets being transmitted over		having different DSCP code points for packets being transmitted over
	the same 5-tuple, issues as discussed in [I-D.ietf-dart-dscp-rtp]		the same 5-tuple, issues as discussed in [RFC7657] need to be taken
	need to be taken into consideration.		into consideration.
	11. k= Attribute Analysis		11. k= Attribute Analysis
	11.1. RFC4566: SDP		11.1. RFC4566: SDP
	[RFC4566] defines SDP that is intended for describing multimedia		[RFC4566] defines SDP that is intended for describing multimedia
	sessions for the purposes of session announcement, session		sessions for the purposes of session announcement, session
	invitation, and other forms of multimedia session initiation.		invitation, and other forms of multimedia session initiation.
	+------+------------------------------------+-------+---------------+		+------+------------------------------------+-------+---------------+
	| Name | Notes | Level | Mux Category |		| Name | Notes | Level | Mux Category |
	skipping to change at page 88, line 28		skipping to change at page 88, line 28
	o Added new section for dealing with FEC payload types.		o Added new section for dealing with FEC payload types.
	19. References		19. References
	19.1. Normative References		19.1. Normative References
	[I-D.ietf-mmusic-sdp-bundle-negotiation]		[I-D.ietf-mmusic-sdp-bundle-negotiation]
	Holmberg, C., Alvestrand, H., and C. Jennings,		Holmberg, C., Alvestrand, H., and C. Jennings,
	"Negotiating Media Multiplexing Using the Session		"Negotiating Media Multiplexing Using the Session
	Description Protocol (SDP)", draft-ietf-mmusic-sdp-bundle-		Description Protocol (SDP)", draft-ietf-mmusic-sdp-bundle-
	negotiation-23 (work in progress), July 2015.		negotiation-24 (work in progress), January 2016.
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session		[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
	Description Protocol", RFC 4566, DOI 10.17487/RFC4566,		Description Protocol", RFC 4566, DOI 10.17487/RFC4566,
	July 2006, <http://www.rfc-editor.org/info/rfc4566>.		July 2006, <http://www.rfc-editor.org/info/rfc4566>.
	19.2. Informative References		19.2. Informative References
	[H.248.15]		[H.248.15]
	"Gateway control protocol: SDP H.248 package attribute",		"Gateway control protocol: SDP H.248 package attribute",
	<http://www.itu.int/rec/T-REC-H.248.15>.		<http://www.itu.int/rec/T-REC-H.248.15>.
	[I-D.ietf-dart-dscp-rtp]
	Black, D. and P. Jones, "Differentiated Services
	(DiffServ) and Real-time Communication", draft-ietf-dart-
	dscp-rtp-10 (work in progress), November 2014.
	[IANA] "Session Description Protocol (SDP) Parameters",		[IANA] "Session Description Protocol (SDP) Parameters",
	<http://www.iana.org/assignments/sdp-parameters/		<http://www.iana.org/assignments/sdp-parameters/
	sdp-parameters.xml>.		sdp-parameters.xml>.
	[Q.1970] "Q.1970 : BICC IP bearer control protocol",		[Q.1970] "Q.1970 : BICC IP bearer control protocol",
	<https://www.itu.int/rec/T-REC-Q.1970-200609-I/en>.		<https://www.itu.int/rec/T-REC-Q.1970-200609-I/en>.
	[R3GPPTS183.063]		[R3GPPTS183.063]
	"TISPAN - IMS based ITPV Stage 3 specification.",		"TISPAN - IMS based ITPV Stage 3 specification.",
	<http://www.etsi.org/deliver/		<http://www.etsi.org/deliver/
	skipping to change at page 96, line 34		skipping to change at page 96, line 34
	Boronat, F., Montagud, M., and K. Gross, "Inter-		Boronat, F., Montagud, M., and K. Gross, "Inter-
	Destination Media Synchronization (IDMS) Using the RTP		Destination Media Synchronization (IDMS) Using the RTP
	Control Protocol (RTCP)", RFC 7272, DOI 10.17487/RFC7272,		Control Protocol (RTCP)", RFC 7272, DOI 10.17487/RFC7272,
	June 2014, <http://www.rfc-editor.org/info/rfc7272>.		June 2014, <http://www.rfc-editor.org/info/rfc7272>.
	[RFC7273] Williams, A., Gross, K., van Brandenburg, R., and H.		[RFC7273] Williams, A., Gross, K., van Brandenburg, R., and H.
	Stokking, "RTP Clock Source Signalling", RFC 7273, DOI		Stokking, "RTP Clock Source Signalling", RFC 7273, DOI
	10.17487/RFC7273, June 2014,		10.17487/RFC7273, June 2014,
	<http://www.rfc-editor.org/info/rfc7273>.		<http://www.rfc-editor.org/info/rfc7273>.
			[RFC7657] Black, D., Ed. and P. Jones, "Differentiated Services
			(Diffserv) and Real-Time Communication", RFC 7657, DOI
			10.17487/RFC7657, November 2015,
			<http://www.rfc-editor.org/info/rfc7657>.
	[T.38] "Procedures for real-time Group 3 facsimile communication		[T.38] "Procedures for real-time Group 3 facsimile communication
	over IP networks", <http://www.itu.int/rec/T-REC-T.38/e>.		over IP networks", <http://www.itu.int/rec/T-REC-T.38/e>.
	Author's Address		Author's Address
	Suhas Nandakumar		Suhas Nandakumar
	Cisco		Cisco
	170 West Tasman Drive		170 West Tasman Drive
	San Jose, CA 95134		San Jose, CA 95134
	USA		USA
End of changes. 12 change blocks.
	28 lines changed or deleted		16 lines changed or added
This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/