< draft-nottingham-rfc5785bis-02.txt		draft-nottingham-rfc5785bis-03.txt >
	Network Working Group M. Nottingham		Network Working Group M. Nottingham
	Internet-Draft February 5, 2018		Internet-Draft February 7, 2018
	Obsoletes: 5785 (if approved)		Obsoletes: 5785 (if approved)
	Intended status: Standards Track		Intended status: Standards Track
	Expires: August 9, 2018		Expires: August 11, 2018
	Defining Well-Known Uniform Resource Identifiers (URIs)		Defining Well-Known Uniform Resource Identifiers (URIs)
	draft-nottingham-rfc5785bis-02		draft-nottingham-rfc5785bis-03
	Abstract		Abstract
	This memo defines a path prefix for "well-known locations", "/.well-		This memo defines a path prefix for "well-known locations", "/.well-
	known/", in selected Uniform Resource Identifier (URI) schemes.		known/", in selected Uniform Resource Identifier (URI) schemes.
	Note to Readers		Note to Readers
	_RFC EDITOR: please remove this section before publication_		_RFC EDITOR: please remove this section before publication_
	This draft is a proposed revision of RFC5875.		This draft is a proposed revision of RFC5875.
	The issues list for this draft can be found at		The issues list for this draft can be found at
	https://github.com/mnot/I-D/labels/5785bis [1].		https://github.com/mnot/I-D/labels/rfc5785bis [1].
	The most recent (often, unpublished) draft is at		The most recent (often, unpublished) draft is at
	https://mnot.github.io/I-D/5785bis/ [2].		https://mnot.github.io/I-D/rfc5785bis/ [2].
	Recent changes are listed at https://github.com/mnot/I-D/commits/gh-		Recent changes are listed at https://github.com/mnot/I-D/commits/gh-
	pages/5785bis [3].		pages/rfc5785bis [3].
	See also the draft's current status in the IETF datatracker, at		See also the draft's current status in the IETF datatracker, at
	https://datatracker.ietf.org/doc/draft-nottingham-5785bis/ [4].		https://datatracker.ietf.org/doc/draft-nottingham-rfc5785bis/ [4].
	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.
	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 August 9, 2018.		This Internet-Draft will expire on August 11, 2018.
	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 7, line 39 ¶		skipping to change at page 7, line 39 ¶
	<https://www.rfc-editor.org/info/rfc7231>.		<https://www.rfc-editor.org/info/rfc7231>.
	[W3C.REC-P3P-20020416]		[W3C.REC-P3P-20020416]
	Marchiori, M., "The Platform for Privacy Preferences 1.0		Marchiori, M., "The Platform for Privacy Preferences 1.0
	(P3P1.0) Specification", World Wide Web Consortium		(P3P1.0) Specification", World Wide Web Consortium
	Recommendation REC-P3P-20020416, April 2002,		Recommendation REC-P3P-20020416, April 2002,
	<http://www.w3.org/TR/2002/REC-P3P-20020416>.		<http://www.w3.org/TR/2002/REC-P3P-20020416>.
	6.3. URIs		6.3. URIs
	[1] https://github.com/mnot/I-D/labels/5785bis		[1] https://github.com/mnot/I-D/labels/rfc5785bis
	[2] https://mnot.github.io/I-D/5785bis/		[2] https://mnot.github.io/I-D/rfc5785bis/
	[3] https://github.com/mnot/I-D/commits/gh-pages/5785bis		[3] https://github.com/mnot/I-D/commits/gh-pages/rfc5785bis
	[4] https://datatracker.ietf.org/doc/draft-nottingham-5785bis/		[4] https://datatracker.ietf.org/doc/draft-nottingham-rfc5785bis/
	[5] http://www.robotstxt.org/		[5] http://www.robotstxt.org/
	Appendix A. Frequently Asked Questions		Appendix A. Frequently Asked Questions
	1. Aren't well-known locations bad for the Web?		1. Aren't well-known locations bad for the Web?
	They are, but for various reasons - both technical and social -		They are, but for various reasons - both technical and social -
	they are sometimes necessary. This memo defines a "sandbox" for		they are sometimes necessary. This memo defines a "sandbox" for
	them, to reduce the risks of collision and to minimise the impact		them, to reduce the risks of collision and to minimise the impact
End of changes. 12 change blocks.
	12 lines changed or deleted		12 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/