draft-ietf-httpapi-link-template-04.unpg.txt		draft-ietf-httpapi-link-template-latest.txt
	Building Blocks for HTTP APIs M. Nottingham		Building Blocks for HTTP APIs M. Nottingham
	Internet-Draft April 1, 2024		Internet-Draft October 04, 2024
	Intended status: Standards Track		Intended status: Standards Track
	Expires: October 3, 2024		Expires: April 7, 2025
	The Link-Template HTTP Header Field		The Link-Template HTTP Header Field
	draft-ietf-httpapi-link-template-04		draft-ietf-httpapi-link-template-latest
	Abstract		Abstract
	This specification defines the Link-Template HTTP header field,		This specification defines the Link-Template HTTP header field,
	providing a means for describing the structure of a link between two		providing a means for describing the structure of a link between two
	resources, so that new links can be generated.		resources, so that new links can be generated.
	About This Document		About This Document
	This note is to be removed before publishing as an RFC.		This note is to be removed before publishing as an RFC.
	skipping to change at line 48 ¶		skipping to change at page 2, line 4 ¶
	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 April 7, 2025.
	This Internet-Draft will expire on October 3, 2024.
	Copyright Notice		Copyright Notice
	Copyright (c) 2024 IETF Trust and the persons identified as the		Copyright (c) 2024 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
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	1.1. Notational Conventions		1.1. Notational Conventions . . . . . . . . . . . . . . . . . 2
	2. The Link-Template Header Field		2. The Link-Template Header Field . . . . . . . . . . . . . . . 3
	2.1. The 'var-base' parameter		2.1. The 'var-base' parameter . . . . . . . . . . . . . . . . 4
	3. Security Considerations		3. Security Considerations . . . . . . . . . . . . . . . . . . . 5
	4. IANA Considerations		4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
	5. Normative References		5. Normative References . . . . . . . . . . . . . . . . . . . . 5
	Author's Address		Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
	1. Introduction		1. Introduction
	[URI-TEMPLATE] defines a syntax for templates that, when expanded		[URI-TEMPLATE] defines a syntax for templates that, when expanded
	using a set of variables, results in a URI [URI].		using a set of variables, results in a URI [URI].
	This specification defines a HTTP header field [HTTP] for conveying		This specification defines a HTTP header field [HTTP] for conveying
	templates for links in the headers of a HTTP message. It is		templates for links in the headers of a HTTP message. It is
	complimentary to the Link header field defined in Section 3 of		complimentary to the Link header field defined in Section 3 of
	[WEB-LINKING], which carries links directly.		[WEB-LINKING], which carries links directly.
	skipping to change at line 230 ¶		skipping to change at page 5, line 45 ¶
	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>.
	[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC		[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
	2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,		2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
	May 2017, <https://www.rfc-editor.org/info/rfc8174>.		May 2017, <https://www.rfc-editor.org/info/rfc8174>.
	[STRUCTURED-FIELDS]		[STRUCTURED-FIELDS]
	Nottingham, M. and P. Kamp, "Structured Field Values for		Nottingham, M. and P. Kamp, "Structured Field Values for
	HTTP", draft-ietf-httpbis-sfbis-05 (work in progress),		HTTP", draft-ietf-httpbis-sfbis-06 (work in progress),
	January 2024.		April 2024.
	[UNICODE-SECURITY]		[UNICODE-SECURITY]
	Davis, M. and M. Suignard, "Unicode Security		Davis, M. and M. Suignard, "Unicode Security
	Considerations", Unicode Technical Report #16, September		Considerations", Unicode Technical Report #16, September
	2014, <http://www.unicode.org/reports/tr36/>.		2014, <http://www.unicode.org/reports/tr36/>.
	[URI] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform		[URI] 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>.
End of changes. 6 change blocks.
	15 lines changed or deleted		14 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/