rfc8959v2.txt		rfc8959.txt
	skipping to change at line 134 ¶		skipping to change at line 134 ¶
	secret-token:E92FB7EB-D882-47A4-A265-A0B6135DC842%20foo		secret-token:E92FB7EB-D882-47A4-A265-A0B6135DC842%20foo
	This (character-for-character, case-sensitive) string will both be		This (character-for-character, case-sensitive) string will both be
	issued by the token authority and required for later access.		issued by the token authority and required for later access.
	Therefore, if the example above were used as a bearer token in		Therefore, if the example above were used as a bearer token in
	[RFC6750], a client might send:		[RFC6750], a client might send:
	GET /authenticated/stuff HTTP/1.1		GET /authenticated/stuff HTTP/1.1
	Host: www.example.com		Host: www.example.com
	Authorization: Bearer		Authorization: Bearer
	secret-token:E92FB7EB-D882-47A4-A265-A0B6135DC842%20foo		secret-token:E92FB7EB-D882-47A4-A265-A0B6135DC842%20foo
	3. IANA Considerations		3. IANA Considerations
	This document registers the following value in the "Uniform Resource		This document registers the following value in the "Uniform Resource
	Identifier (URI) Schemes" registry:		Identifier (URI) Schemes" registry:
	Scheme name: secret-token		Scheme name: secret-token
	Status: provisional		Status: provisional
	Applications/protocols that use this scheme: none yet		Applications/protocols that use this scheme: none yet
	Contact: iesg@iesg.org		Contact: iesg@iesg.org
End of changes. 1 change blocks.
	1 lines changed or deleted		1 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/