< draft-rosenberg-sip-app-media-tag-03.txt		draft-rosenberg-sip-app-media-tag-04.txt >
	SIP J. Rosenberg		SIP J. Rosenberg
	Internet-Draft Cisco		Internet-Draft Cisco
	Intended status: Standards Track July 29, 2009		Intended status: Standards Track September 10, 2009
	Expires: January 30, 2010		Expires: March 14, 2010
	A Session Initiation Protocol (SIP) Media Feature Tag for MIME		A Session Initiation Protocol (SIP) Media Feature Tag for MIME
	Application Sub-Types		Application Sub-Types
	draft-rosenberg-sip-app-media-tag-03		draft-rosenberg-sip-app-media-tag-04
	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. This document may contain material		provisions of BCP 78 and BCP 79. This document may contain material
	from IETF Documents or IETF Contributions published or made publicly		from IETF Documents or IETF Contributions published or made publicly
	available before November 10, 2008. The person(s) controlling the		available before November 10, 2008. The person(s) controlling the
	copyright in some of this material may not have granted the IETF		copyright in some of this material may not have granted the IETF
	Trust the right to allow modifications of such material outside the		Trust the right to allow modifications of such material outside the
	IETF Standards Process. Without obtaining an adequate license from		IETF Standards Process. Without obtaining an adequate license from
	skipping to change at page 1, line 43 ¶		skipping to change at page 1, line 43 ¶
	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/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	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.
	This Internet-Draft will expire on January 30, 2010.		This Internet-Draft will expire on March 14, 2010.
	Copyright Notice		Copyright Notice
	Copyright (c) 2009 IETF Trust and the persons identified as the		Copyright (c) 2009 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 in effect on the date of		Provisions Relating to IETF Documents in effect on the date of
	publication of this document (http://trustee.ietf.org/license-info).		publication of this document (http://trustee.ietf.org/license-info).
	Please review these documents carefully, as they describe your rights		Please review these documents carefully, as they describe your rights
	skipping to change at page 5, line 22 ¶		skipping to change at page 5, line 22 ¶
	2. Terminology		2. 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 [RFC2119].		document are to be interpreted as described in RFC 2119 [RFC2119].
	3. sip.app-subtype Media Feature Tag		3. sip.app-subtype Media Feature Tag
	The 'sip.app-subtype' media feature tag is of type token with a case-		The 'sip.app-subtype' media feature tag is of type token with a case-
	sensitive equality relationship. Its value can be any registered or		insensitive equality relationship. Its value can be any registered
	private MIME application sub-type. When included in the Contact		or private MIME application sub-type compliant to the subtype-name
	header field of a REGISTER request, an agent SHOULD include all		grammar defined in [RFC4288]. When included in the Contact header
	application subtypes that it can support as streaming formats. An		field of a REGISTER request, an agent SHOULD include all application
	application sub-type is supported if the user agent would be capable		subtypes that it can support as streaming formats. An application
	of processing an Session Description Protocol (SDP) [RFC4566] offer		sub-type is supported if the user agent would be capable of
			processing an Session Description Protocol (SDP) [RFC4566] offer
	[RFC3264] that contained that sub-type as a format in the m-line of		[RFC3264] that contained that sub-type as a format in the m-line of
	the SDP.		the SDP.
	When included in the Accept-Contact or Reject-Contact header field,		When included in the Accept-Contact or Reject-Contact header field,
	it indicates a desire on the part of a UAC to be connected to a UAS		it indicates a desire on the part of a UAC to be connected to a UAS
	which can support, or cannot support respectively, streaming using		which can support, or cannot support respectively, streaming using
	that application sub-type.		that application sub-type.
	It is important to note that this media feature tag is only		It is important to note that this media feature tag is only
	indicating the streaming media types that a user agent is capable of		indicating the streaming media types that a user agent is capable of
	skipping to change at page 7, line 36 ¶		skipping to change at page 7, line 36 ¶
	Feature Tag Registration Tree defined in RFC 3840 [RFC3840].		Feature Tag Registration Tree defined in RFC 3840 [RFC3840].
	Media feature tag name: sip.app-subtype		Media feature tag name: sip.app-subtype
	ASN.1 Identifier: 1.3.6.1.8.4.24		ASN.1 Identifier: 1.3.6.1.8.4.24
	Summary of the media feature indicated by this tag: This feature tag		Summary of the media feature indicated by this tag: This feature tag
	indicates the MIME application sub-types supported by the agent		indicates the MIME application sub-types supported by the agent
	for purposes of streaming media.		for purposes of streaming media.
	Values appropriate for use with this feature tag: Token.		Values appropriate for use with this feature tag: Token (equality
			relationship).
	The feature tag is intended primarily for use in the following		The feature tag is intended primarily for use in the following
	applications, protocols, services, or negotiation mechanisms: This		applications, protocols, services, or negotiation mechanisms: This
	feature tag is most useful in a communications application, for		feature tag is most useful in a communications application, for
	describing the capabilities of a device, such as a phone or PDA.		describing the capabilities of a device, such as a phone or PDA.
	Examples of typical use: Routing a call to a phone that can support		Examples of typical use: Routing a call to a phone that can support
	a multiplayer game.		a multiplayer game.
	Related standards or documents: RFC XXXX [[Note to IANA: Please		Related standards or documents: RFC XXXX [[Note to IANA: Please
	skipping to change at page 8, line 25 ¶		skipping to change at page 8, line 25 ¶
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model		[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model
	with Session Description Protocol (SDP)", RFC 3264,		with Session Description Protocol (SDP)", RFC 3264,
	June 2002.		June 2002.
	[RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat,		[RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat,
	"Indicating User Agent Capabilities in the Session		"Indicating User Agent Capabilities in the Session
	Initiation Protocol (SIP)", RFC 3840, August 2004.		Initiation Protocol (SIP)", RFC 3840, August 2004.
			[RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and
			Registration Procedures", BCP 13, RFC 4288, December 2005.
	[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session		[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
	Description Protocol", RFC 4566, July 2006.		Description Protocol", RFC 4566, July 2006.
	7.2. Informative References		7.2. Informative References
	[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,		[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
	A., Peterson, J., Sparks, R., Handley, M., and E.		A., Peterson, J., Sparks, R., Handley, M., and E.
	Schooler, "SIP: Session Initiation Protocol", RFC 3261,		Schooler, "SIP: Session Initiation Protocol", RFC 3261,
	June 2002.		June 2002.
End of changes. 6 change blocks.
	11 lines changed or deleted		16 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/