< draft-ietf-ppsp-base-tracker-protocol-09.txt		draft-ietf-ppsp-base-tracker-protocol-10.txt >
	PPSP Rui S. Cruz		PPSP Rui S. Cruz
	INTERNET-DRAFT Mario S. Nunes		INTERNET-DRAFT Mario S. Nunes
	Intended Status: Standards Track IST/INESC-ID/INOV		Intended Status: Standards Track IST/INESC-ID/INOV
	Expires: September 28, 2015 Yingjie Gu		Expires: March 27, 2016 Yingjie Gu
	Jinwei Xia		Jinwei Xia
	Rachel Huang		Rachel Huang
	Huawei		Huawei
	Joao P. Taveira		Joao P. Taveira
	IST/INOV		IST/INOV
	Deng Lingli		Deng Lingli
	China Mobile		China Mobile
	March 27, 2015		September 24, 2015
	PPSP Tracker Protocol-Base Protocol (PPSP-TP/1.0)		PPSP Tracker Protocol-Base Protocol (PPSP-TP/1.0)
	draft-ietf-ppsp-base-tracker-protocol-09		draft-ietf-ppsp-base-tracker-protocol-10
	Abstract		Abstract
	This document specifies the base Peer-to-Peer Streaming Protocol-		This document specifies the base Peer-to-Peer Streaming Protocol-
	Tracker Protocol (PPSP-TP/1.0), an application-layer control		Tracker Protocol (PPSP-TP/1.0), an application-layer control
	(signaling) protocol for the exchange of meta information between		(signaling) protocol for the exchange of meta information between
	trackers and peers. The specification outlines the architecture of		trackers and peers. The specification outlines the architecture of
	the protocol and its functionality, and describes message flows,		the protocol and its functionality, and describes message flows,
	message processing instructions, message formats, formal syntax and		message processing instructions, message formats, formal syntax and
	semantics. The PPSP Tracker Protocol enables cooperating peers to		semantics. The PPSP Tracker Protocol enables cooperating peers to
	skipping to change at page 1, line 41 ¶		skipping to change at page 1, line 41 ¶
	and multi-view (3D) videos, in live, time-shifted and on-demand		and multi-view (3D) videos, in live, time-shifted and on-demand
	modes.		modes.
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with the		This Internet-Draft is submitted to IETF in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as		other groups may also distribute working documents as Internet-
	Internet-Drafts.		Drafts.
	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."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/1id-abstracts.html		http://www.ietf.org/1id-abstracts.html
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html		http://www.ietf.org/shadow.html
	skipping to change at page 4, line 40 ¶		skipping to change at page 4, line 40 ¶
	1.1 Terminology		1.1 Terminology
	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 RFC 2119 [KEYWORDS].		document are to be interpreted as described in RFC 2119 [KEYWORDS].
	ABSOLUTE TIME: Absolute time is expressed as ISO 8601 timestamps,		ABSOLUTE TIME: Absolute time is expressed as ISO 8601 timestamps,
	using zero UTC offset. Fractions of a second may be indicated.		using zero UTC offset. Fractions of a second may be indicated.
	Example for December 25, 2010 at 14h56 and 20.25 seconds: basic		Example for December 25, 2010 at 14h56 and 20.25 seconds: basic
	format 20101225T145620.25Z or extended format		format 20101225T145620.25Z or extended format 2010-12-
	2010-12-25T14:56:20.25Z.		25T14:56:20.25Z.
	CHUNK: A Chunk is a basic unit of data organized in P2P streaming		CHUNK: A Chunk is a basic unit of data organized in P2P streaming
	for storage, scheduling, advertisement and exchange among peers.		for storage, scheduling, advertisement and exchange among peers.
	CHUNK ID: A unique resource identifier for a Chunk. The identifier		CHUNK ID: A unique resource identifier for a Chunk. The identifier
	type depends on the addressing scheme used, i.e., an integer, an		type depends on the addressing scheme used, i.e., an integer, an
	HTTP-URL and possibly a byte-range, and is described in the MPD.		HTTP-URL and possibly a byte-range, and is described in the MPD.
	CONNECTION TRACKER: The node running the tracker service to which		CONNECTION TRACKER: The node running the tracker service to which
	the PPSP peer will connect when it wants to get registered and join		the PPSP peer will connect when it wants to get registered and join
	skipping to change at page 41, line 9 ¶		skipping to change at page 41, line 9 ¶
	can be achieved by standard solutions and facilities.		can be achieved by standard solutions and facilities.
	5.2.1 Interoperability		5.2.1 Interoperability
	Interoperability refers to allowing information sharing and		Interoperability refers to allowing information sharing and
	operations between multiple devices and multiple management		operations between multiple devices and multiple management
	applications. For PPSP-TP, distinct types of devices host PPSP-TP		applications. For PPSP-TP, distinct types of devices host PPSP-TP
	servers (Trackers) and clients (Peers). Therefore, support for		servers (Trackers) and clients (Peers). Therefore, support for
	multiple standard schema languages, management protocols and		multiple standard schema languages, management protocols and
	information models, suited to different purposes, was considered in		information models, suited to different purposes, was considered in
	the PPSP-TP design. Specifically, management functionality for		the PPSP-TP design. Specifically, management functionality for PPSP-
	PPSP-TP devices can be achieved with Simple Network Management		TP devices can be achieved with Simple Network Management Protocol
	Protocol (SNMP) [RFC3410], syslog [RFC5424] and NETCONF [RFC6241].		(SNMP) [RFC3410], syslog [RFC5424] and NETCONF [RFC6241].
	5.2.2 Management Information		5.2.2 Management Information
	PPSP Trackers may implement SNMP management interfaces, namely the		PPSP Trackers may implement SNMP management interfaces, namely the
	Application Management MIB [RFC2564] without the need to instrument		Application Management MIB [RFC2564] without the need to instrument
	the Tracker application itself. The channel, connections and		the Tracker application itself. The channel, connections and
	transaction objects of the the Application Management MIB can be used		transaction objects of the the Application Management MIB can be used
	to report the basic behavior of the PPSP Tracker service.		to report the basic behavior of the PPSP Tracker service.
	The Application Performance Measurement MIB (APM-MIB) [RFC3729] and		The Application Performance Measurement MIB (APM-MIB) [RFC3729] and
	skipping to change at page 51, line 33 ¶		skipping to change at page 51, line 33 ¶
	+ corrections in the specifications of protocol elements		+ corrections in the specifications of protocol elements
	+ section 5 specification of protocol elements semantics		+ section 5 specification of protocol elements semantics
	+ introduced a IANA MIME Type registry		+ introduced a IANA MIME Type registry
	-08 2015-01-08 Major Revision		-08 2015-01-08 Major Revision
	* merge sections 5 and 4 with section 3; renumbered all other		* merge sections 5 and 4 with section 3; renumbered all other
	+ refined the protocol elements definitions for consistency		+ refined the protocol elements definitions for consistency
	with the JSON data structures		with the JSON data structures
	+ revised protocol messages encoding examples		+ revised protocol messages encoding examples
	+ additional IANA registry for protocol version		+ additional IANA registry for protocol version
	* editorial corrections		* editorial corrections
	-09 (Current version) Major Revision		-09 (2015-3-27) Major Revision
	+ Add concurrent_link in the stream_stats specification.		+ Add concurrent_link in the stream_stats specification.
	+ Remove "PROXY" value from "ability_nat" specification.		+ Remove "PROXY" value from "ability_nat" specification.
	+ Dividing attributes by "," in the example		+ Dividing attributes by "," in the example
	* editorial corrections		* editorial corrections
			-10 (Current version) Major Revision
			+ Update dates
	Authors' Addresses		Authors' Addresses
	Rui Santos Cruz		Rui Santos Cruz
	IST/INESC-ID/INOV		IST/INESC-ID/INOV
	Phone: +351.939060939		Phone: +351.939060939
	Email: rui.cruz@ieee.org		Email: rui.cruz@ieee.org
	Mario Serafim Nunes		Mario Serafim Nunes
	IST/INESC-ID/INOV		IST/INESC-ID/INOV
End of changes. 8 change blocks.
	11 lines changed or deleted		13 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/