< draft-nottingham-how-did-that-get-into-the-repo-00.txt		draft-nottingham-how-did-that-get-into-the-repo-01.txt >
	Network Working Group M. Nottingham		Network Working Group M. Nottingham
	Internet-Draft August 16, 2018		Internet-Draft November 7, 2018
	Intended status: Standards Track		Intended status: Informational
	Expires: February 17, 2019		Expires: May 11, 2019
	The secret-token URI Scheme		The secret-token URI Scheme
	draft-nottingham-how-did-that-get-into-the-repo-00		draft-nottingham-how-did-that-get-into-the-repo-01
	Abstract		Abstract
	This document registers the "secret-token" URI scheme, to aid in the		This document registers the "secret-token" URI scheme, to aid in the
	identification of authentication tokens.		identification of authentication tokens.
	Note to Readers		Note to Readers
	_RFC EDITOR: please remove this section before publication_		_RFC EDITOR: please remove this section before publication_
	skipping to change at page 1, line 49 ¶		skipping to change at page 1, line 49 ¶
	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 https://datatracker.ietf.org/drafts/current/.		Drafts is at https://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 February 17, 2019.		This Internet-Draft will expire on May 11, 2019.
	Copyright Notice		Copyright Notice
	Copyright (c) 2018 IETF Trust and the persons identified as the		Copyright (c) 2018 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
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://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 23 ¶		skipping to change at page 3, line 23 ¶
	1.1. Notational Conventions		1.1. 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", "NOT RECOMMENDED", "MAY", and		"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
	"OPTIONAL" in this document are to be interpreted as described in BCP		"OPTIONAL" in this document are to be interpreted as described in BCP
	14 [RFC2119] [RFC8174] when, and only when, they appear in all		14 [RFC2119] [RFC8174] when, and only when, they appear in all
	capitals, as shown here.		capitals, as shown here.
	This document uses ABNF [RFC5234], including by reference the		This document uses ABNF [RFC5234], including by reference the
	following rules: ALPHA, DIGIT.		following rules: ALPHA, DIGIT. It also uses the pchar rule from
			[RFC3986].
	2. The secret-token URI scheme		2. The secret-token URI scheme
	The secret-token URI scheme identifies a token that is intended to be		The secret-token URI scheme identifies a token that is intended to be
	a secret.		a secret.
	secret-token-URI = secret-token-scheme ":" token		secret-token-URI = secret-token-scheme ":" token
	secret-token-scheme = "secret-token"		secret-token-scheme = "secret-token"
	token = 1*tchar		token = 1*pchar
	tchar = ALPHA / DIGIT / "-" / "_" / "." / "~"
	Note that characters outside the range allowed by tchar MUST be		See [RFC3986], Section 3.3 for a definition of pchar. Disallowed
	percent-encoded ([RFC3986], Section 2.1.		characters - including non-ASCII characters - MUST be encoded into
			UTF-8 [RFC3629] and then percent-encoded ([RFC3986], Section 2.1).
	When a token is both generated and presented for authentication, the		When a token is both generated and presented for authentication, the
	entire URI MUST be used, without changes.		entire URI MUST be used, without changes.
	For example, given the URI:		For example, given the URI:
	secret-token:E92FB7EB-D882-47A4-A265-A0B6135DC842%20foo		secret-token:E92FB7EB-D882-47A4-A265-A0B6135DC842%20foo
	This string (character-for-character, case-sensitive) will both be		This string (character-for-character, case-sensitive) will both be
	issued by the token authority, and required for later access.		issued by the token authority, and required for later access.
	3. IANA Considerations		3. IANA Considerations
	This document registers the following value in the URI Scheme		This document registers the following value in the URI Scheme
	registry:		registry:
	o Scheme name: secret-token		o Scheme name: secret-token
	o Status: permanent		o Status: provisional
	o Applications / protocols that use this scheme: none yet		o Applications / protocols that use this scheme: none yet
	o Contact: iesg@iesg.org		o Contact: iesg@iesg.org
	o Change Controller: IESG		o Change Controller: IESG
	o References: [this document]		o References: [this document]
	4. Security Considerations		4. Security Considerations
	skipping to change at page 4, line 46 ¶		skipping to change at page 4, line 46 ¶
	5. References		5. References
	5.1. Normative References		5.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,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<https://www.rfc-editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
			[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
			10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November
			2003, <https://www.rfc-editor.org/info/rfc3629>.
	[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform		[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
	Resource Identifier (URI): Generic Syntax", STD 66,		Resource Identifier (URI): Generic Syntax", STD 66,
	RFC 3986, DOI 10.17487/RFC3986, January 2005,		RFC 3986, DOI 10.17487/RFC3986, January 2005,
	<https://www.rfc-editor.org/info/rfc3986>.		<https://www.rfc-editor.org/info/rfc3986>.
	[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax		[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
	Specifications: ABNF", STD 68, RFC 5234,		Specifications: ABNF", STD 68, RFC 5234,
	DOI 10.17487/RFC5234, January 2008,		DOI 10.17487/RFC5234, January 2008,
	<https://www.rfc-editor.org/info/rfc5234>.		<https://www.rfc-editor.org/info/rfc5234>.
End of changes. 8 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/