rfc7865v3.txt		rfc7865.txt
	skipping to change at page 6, line 17		skipping to change at page 6, line 17
	a single SRC at a particular instant in time. Metadata changes from		a single SRC at a particular instant in time. Metadata changes from
	one snapshot to another reflect changes in what is being recorded.		one snapshot to another reflect changes in what is being recorded.
	For example, if a participant joins a conference, then the SRC sends		For example, if a participant joins a conference, then the SRC sends
	the SRS a snapshot of metadata having that participant information		the SRS a snapshot of metadata having that participant information
	(with attributes like (Name, AoR) tuple and associate-time). (Note:		(with attributes like (Name, AoR) tuple and associate-time). (Note:
	"AoR" means "Address-of-Record".)		"AoR" means "Address-of-Record".)
	Some of the metadata is not required to be conveyed explicitly from		Some of the metadata is not required to be conveyed explicitly from
	the SRC to the SRS, if it can be obtained contextually by the SRS		the SRC to the SRS, if it can be obtained contextually by the SRS
	(e.g., from SIP or Session Description Protocol (SDP) signaling).		(e.g., from SIP or Session Description Protocol (SDP) signaling).
	For example, the "label" attribute within the 'stream' XML element		For example, the 'label' attribute within the 'stream' XML element
	references an SDP "a=label" attribute that identifies an m-line		references an SDP "a=label" attribute that identifies an m-line
	within the Recording Session (RS) SDP. The SRS would learn the media		within the Recording Session (RS) SDP. The SRS would learn the media
	properties from the media line.		properties from the media line.
	5. Recording Metadata Format from SRC to SRS		5. Recording Metadata Format from SRC to SRS
	This section gives an overview of the recording metadata format.		This section gives an overview of the recording metadata format.
	Some data from the metadata model is assumed to be made available to		Some data from the metadata model is assumed to be made available to
	the SRS through SDP [RFC4566], and therefore this data is not		the SRS through SDP [RFC4566], and therefore this data is not
	represented in the XML document format specified in this document.		represented in the XML document format specified in this document.
	skipping to change at page 18, line 9		skipping to change at page 18, line 9
	be sent whenever there is a change in media (e.g., a direction		be sent whenever there is a change in media (e.g., a direction
	change, like pause/resume, codec change, and/or participant change).		change, like pause/resume, codec change, and/or participant change).
	The MS object is represented in the XML schema using the 'stream'		The MS object is represented in the XML schema using the 'stream'
	element.		element.
	6.7.1. Attributes		6.7.1. Attributes
	A MS class has the following attributes:		A MS class has the following attributes:
	o label - The "label" attribute within the 'stream' XML element		o label - The 'label' attribute within the 'stream' XML element
	references an SDP "a=label" attribute that identifies an m-line		references an SDP "a=label" attribute that identifies an m-line
	within the RS SDP. That m-line carries the media stream from the		within the RS SDP. That m-line carries the media stream from the
	SRC to the SRS.		SRC to the SRS.
	o content-type - The content of a MS element will be described in		o content-type - The content of a MS element will be described in
	terms of the "a=content" attribute defined in Section 5 of		terms of the "a=content" attribute defined in Section 5 of
	[RFC4796]. If the SRC wishes to convey the content-type to the		[RFC4796]. If the SRC wishes to convey the content-type to the
	SRS, it does so by including an "a=content" attribute with the		SRS, it does so by including an "a=content" attribute with the
	m-line in the RS SDP.		m-line in the RS SDP.
End of changes. 2 change blocks.
	2 lines changed or deleted		2 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/