draft-ietf-avtext-splicing-for-rtp-02.txt		draft-ietf-avtext-splicing-for-rtp-03.txt
	AVTEXT Working Group J. Xia		AVTEXT Working Group J. Xia
	Internet-Draft Huawei		Internet-Draft Huawei
	Intended status: Informational November 15, 2011		Intended status: Informational December 22, 2011
	Expires: May 18, 2012		Expires: June 24, 2012
	Content Splicing for RTP Sessions		Content Splicing for RTP Sessions
	draft-ietf-avtext-splicing-for-rtp-02		draft-ietf-avtext-splicing-for-rtp-03
	Abstract		Abstract
	This memo outlines RTP splicing. Splicing is a process that replaces		This memo outlines RTP splicing. Splicing is a process that replaces
	the content of the main multimedia stream with other multimedia		the content of the main multimedia stream with other multimedia
	content, and delivers the substitutive multimedia content to receiver		content, and delivers the substitutive multimedia content to receiver
	for a period of time. This memo provides some RTP splicing use		for a period of time. This memo provides some RTP splicing use
	cases, then we enumerate a set of requirements and analyze whether an		cases, then we enumerate a set of requirements and analyze whether an
	existing RTP level middlebox can meet these requirements, at last we		existing RTP level middlebox can meet these requirements, at last we
	provide concrete guidelines for how the chosen middlebox works to		provide concrete guidelines for how the chosen middlebox works to
	skipping to change at page 1, line 37		skipping to change at page 1, line 37
	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 May 18, 2012.		This Internet-Draft will expire on June 24, 2012.
	Copyright Notice		Copyright Notice
	Copyright (c) 2011 IETF Trust and the persons identified as the		Copyright (c) 2011 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
	skipping to change at page 4, line 41		skipping to change at page 4, line 41
	Splicing In Point		Splicing In Point
	A virtual point in the RTP stream, suitable for substitutive		A virtual point in the RTP stream, suitable for substitutive
	content entry, that exists in the boundary of two independently		content entry, that exists in the boundary of two independently
	decodable frames.		decodable frames.
	Splicing Out Point		Splicing Out Point
	A virtual point in the RTP stream, suitable for substitutive		A virtual point in the RTP stream, suitable for substitutive
	content exist, that exists in the boundary of two independently		content exit, that exists in the boundary of two independently
	decodable frames.		decodable frames.
	Splicer		Splicer
	An intermediary node that inserts substitutive content into main		An intermediary node that inserts substitutive content into main
	RTP stream. Splicer sends substitutive content to RTP receiver		RTP stream. Splicer sends substitutive content to RTP receiver
	instead of main content during splicing. It is also responsible		instead of main content during splicing. It is also responsible
	for processing RTCP traffic between media source and RTP receiver.		for processing RTCP traffic between media source and RTP receiver.
	3. RTP Splicing Discussion and Requirements		3. RTP Splicing Discussion and Requirements
	skipping to change at page 15, line 42		skipping to change at page 15, line 42
	with Feedback (AVPF)", RFC 5104, February 2008.		with Feedback (AVPF)", RFC 5104, February 2008.
	[RFC5117] Westerlund, M. and S. Wenger, "RTP Topologies", RFC 5117,		[RFC5117] Westerlund, M. and S. Wenger, "RTP Topologies", RFC 5117,
	January 2008.		January 2008.
	[RFC6051] Perkins, C. and T. Schierl, "Rapid Synchronisation of RTP		[RFC6051] Perkins, C. and T. Schierl, "Rapid Synchronisation of RTP
	Flows", RFC 6051, November 2010.		Flows", RFC 6051, November 2010.
	[I-D.ietf-avtcore-ecn-for-rtp]		[I-D.ietf-avtcore-ecn-for-rtp]
	Westerlund, M., "Explicit Congestion Notification (ECN)		Westerlund, M., "Explicit Congestion Notification (ECN)
	for RTP over UDP", draft-ietf-avtcore-ecn-for-rtp-02 (work		for RTP over UDP", draft-ietf-avtcore-ecn-for-rtp-05 (work
	in progress), October 2010.		in progress), October 2011.
	10.2. Informative References		10.2. Informative References
	[RFC5348] Floyd, S., Handley, M., Padhye, J., and J. Widmer, "TCP		[RFC5348] Floyd, S., Handley, M., Padhye, J., and J. Widmer, "TCP
	Friendly Rate Control (TFRC): Protocol Specification",		Friendly Rate Control (TFRC): Protocol Specification",
	RFC 5348, September 2008.		RFC 5348, September 2008.
	[RFC5760] Ott, J., Chesterfield, J., and E. Schooler, "RTP Control		[RFC5760] Ott, J., Chesterfield, J., and E. Schooler, "RTP Control
	Protocol (RTCP) Extensions for Single-Source Multicast		Protocol (RTCP) Extensions for Single-Source Multicast
	Sessions with Unicast Feedback", RFC 5760, February 2010.		Sessions with Unicast Feedback", RFC 5760, February 2010.
End of changes. 5 change blocks.
	7 lines changed or deleted		7 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/