< draft-ietf-oauth-urn-sub-ns-03.txt		draft-ietf-oauth-urn-sub-ns-04.txt >
	OAuth Working Group B. Campbell		OAuth Working Group B. Campbell
	Internet-Draft Ping Identity Corp.		Internet-Draft Ping Identity Corp.
	Intended status: Standards Track H. Tschofenig		Intended status: Standards Track H. Tschofenig
	Expires: December 23, 2012 Nokia Siemens Networks		Expires: December 24, 2012 Nokia Siemens Networks
	June 21, 2012		June 22, 2012
	An IETF URN Sub-Namespace for OAuth		An IETF URN Sub-Namespace for OAuth
	draft-ietf-oauth-urn-sub-ns-03		draft-ietf-oauth-urn-sub-ns-04
	Abstract		Abstract
	This document establishes an IETF URN Sub-namespace for use with		This document establishes an IETF URN Sub-namespace for use with
	OAuth related specifications.		OAuth related specifications.
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	skipping to change at page 1, line 32 ¶		skipping to change at page 1, line 32 ¶
	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 December 23, 2012.		This Internet-Draft will expire on December 24, 2012.
	Copyright Notice		Copyright Notice
	Copyright (c) 2012 IETF Trust and the persons identified as the		Copyright (c) 2012 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 3, line 24 ¶		skipping to change at page 3, line 24 ¶
	2. Notational Conventions		2. Notational Conventions
	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. Registration Template		3. Registration Template
	If a registrant wishes to have a OAuth URI registered, then a URN of		If a registrant wishes to have a OAuth URI registered, then a URN of
	the form urn:ietf:params:oauth:<class>:<id> will be requested where		the form urn:ietf:params:oauth:<value> will be requested where
	<class> is the category of the functionality being registered and		<value> is a suitable representation of the functionality or concept
	<id> is a unique id for the functionality within that class.		being registered.
	The registration procedure for new entries requires a request in the		The registration procedure for new entries requires a request in the
	form of the following template and is subject to Expert Review per		form of the following template and is subject to Expert Review per
	RFC 5226 [RFC5226].		RFC 5226 [RFC5226].
	URN:		URN:
	The URI that identifies the registered functionality.		The URI that identifies the registered functionality.
	Common Name:		Common Name:
	The name by which the functionality being registered is generally		The name by which the functionality being registered is generally
	skipping to change at page 5, line 9 ¶		skipping to change at page 5, line 9 ¶
	5.1. IETF URN Sub-namespace Registration urn:ietf:params:oauth		5.1. IETF URN Sub-namespace Registration urn:ietf:params:oauth
	Per RFC 3553 [RFC3553], IANA is requested to please register a new		Per RFC 3553 [RFC3553], IANA is requested to please register a new
	URN sub-namespace, urn:ietf:params:oauth.		URN sub-namespace, urn:ietf:params:oauth.
	o Registry name: oauth		o Registry name: oauth
	o Specification: [[this document]]		o Specification: [[this document]]
	o Repository: [[not sure about this? this document or		o Repository: [[The registry created in Section 3.]]
	http://www.iana.org/assignments/oauth]]
	o Index value: values subordinate to urn:ietf:params:oauth are of		o Index value: values subordinate to urn:ietf:params:oauth are of
	the from urn:ietf:params:oauth:<class>:<id> with <class>:<id> as		the from urn:ietf:params:oauth:<value> with <value> as the index
	the index value.		value. It is suggested that <value> include both a "class" and an
			"identifier-within-class" component, with the two components being
			separated by a colon (":"); other compositions of the <value> may
			also be used.
	6. References		6. References
	6.1. Normative References		6.1. Normative References
	[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.
	[RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997.		[RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997.
	skipping to change at page 5, line 48 ¶		skipping to change at page 6, line 4 ¶
	in progress), June 2012.		in progress), June 2012.
	Appendix A. Acknowledgements		Appendix A. Acknowledgements
	The authors thank the following for their helpful contributions:		The authors thank the following for their helpful contributions:
	Stephen Farrell, Barry Leiba, Peter Saint-Andre and Michael B. Jones.		Stephen Farrell, Barry Leiba, Peter Saint-Andre and Michael B. Jones.
	Appendix B. Document History		Appendix B. Document History
	[[ to be removed by RFC editor before publication as an RFC ]]		[[ to be removed by RFC editor before publication as an RFC ]]
			o Changed the Index value (and Registration Template into paragraph)
			from <class><id> to just <value> with a suggestion that it have
			both a "class" and an "identifier-within-class" parts per
			http://www.ietf.org/mail-archive/web/oauth/current/msg09381.html
			so as to be less restrictive
	draft-ietf-oauth-urn-sub-ns-03		draft-ietf-oauth-urn-sub-ns-03
	o Changes to address comments in the message "AD review of		o Changes to address comments in the message "AD review of
	draft-ietf-oauth-urn-sub-ns-02" at		draft-ietf-oauth-urn-sub-ns-02" at
	http://www.ietf.org/mail-archive/web/oauth/current/msg09350.html		http://www.ietf.org/mail-archive/web/oauth/current/msg09350.html
	and subsequent messages in that thread		and subsequent messages in that thread
	o Update area and workgroup (now Security and OAuth was Internet and		o Update area and workgroup (now Security and OAuth was Internet and
	nothing)		nothing)
	o Change from informational to standards-track		o Change from informational to standards-track
	skipping to change at page 6, line 43 ¶		skipping to change at page 7, line 5 ¶
	o fix typo: "The registration procedure for new entries to the		o fix typo: "The registration procedure for new entries to the
	requires a request ..." --> "The registration procedure for new		requires a request ..." --> "The registration procedure for new
	entries requires a request ..."		entries requires a request ..."
	draft-ietf-oauth-urn-sub-ns-01		draft-ietf-oauth-urn-sub-ns-01
	o security considerations now points to RFC 2141 rather than RFC		o security considerations now points to RFC 2141 rather than RFC
	3553 per		3553 per
	http://www.ietf.org/mail-archive/web/oauth/current/msg07880.html		http://www.ietf.org/mail-archive/web/oauth/current/msg07880.html
	draft-ietf-oauth-urn-sub-ns-00
	o change doc name from draft-campbell-oauth-urn-sub-ns to		o change doc name from draft-campbell-oauth-urn-sub-ns to
	draft-ietf-oauth-urn-sub-ns per		draft-ietf-oauth-urn-sub-ns per
	http://www.ietf.org/mail-archive/web/oauth/current/msg07384.html		http://www.ietf.org/mail-archive/web/oauth/current/msg07384.html
	draft-campbell-oauth-urn-sub-ns-01		draft-campbell-oauth-urn-sub-ns-01
	o minor editorial changes		o minor editorial changes
	draft-campbell-oauth-urn-sub-ns-00		draft-campbell-oauth-urn-sub-ns-00
	o initial draft based on		o initial draft based on
	http://www.ietf.org/mail-archive/web/oauth/current/msg06949.html		http://www.ietf.org/mail-archive/web/oauth/current/msg06949.html
	Authors' Addresses		Authors' Addresses
	Brian Campbell		Brian Campbell
End of changes. 10 change blocks.
	13 lines changed or deleted		20 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/