draft-ietf-httpapi-link-hint-01.unpg.txt   draft-ietf-httpapi-link-hint-latest.txt 
Network Working Group M. Nottingham Network Working Group M. Nottingham
Internet-Draft February 25, 2024 Internet-Draft August 22, 2024
Intended status: Standards Track Intended status: Standards Track
Expires: August 28, 2024 Expires: February 23, 2025
HTTP Link Hints HTTP Link Hints
draft-ietf-httpapi-link-hint-01 draft-ietf-httpapi-link-hint-latest
Abstract Abstract
This memo specifies "HTTP Link Hints", a mechanism for annotating Web This memo specifies "HTTP Link Hints", a mechanism for annotating Web
links to HTTP(S) resources with information that otherwise might be links to HTTP(S) resources with information that otherwise might be
discovered by interacting with them. discovered by interacting with them.
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 February 23, 2025.
This Internet-Draft will expire on August 28, 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 . . . . . . . . . . . . . . . . . 3
2. HTTP Link Hints 2. HTTP Link Hints . . . . . . . . . . . . . . . . . . . . . . . 4
3. Pre-Defined HTTP Link Hints 3. Pre-Defined HTTP Link Hints . . . . . . . . . . . . . . . . . 4
3.1. allow 3.1. allow . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2. formats 3.2. formats . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.3. links 3.3. links . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.4. accept-post 3.4. accept-post . . . . . . . . . . . . . . . . . . . . . . . 6
3.5. accept-patch 3.5. accept-patch . . . . . . . . . . . . . . . . . . . . . . 7
3.6. accept-ranges 3.6. accept-ranges . . . . . . . . . . . . . . . . . . . . . . 7
3.7. accept-prefer 3.7. accept-prefer . . . . . . . . . . . . . . . . . . . . . . 7
3.8. precondition-req 3.8. precondition-req . . . . . . . . . . . . . . . . . . . . 8
3.9. auth-schemes 3.9. auth-schemes . . . . . . . . . . . . . . . . . . . . . . 8
3.10. status 3.10. status . . . . . . . . . . . . . . . . . . . . . . . . . 9
4. Security Considerations 4. Security Considerations . . . . . . . . . . . . . . . . . . . 9
5. IANA Considerations 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
5.1. HTTP Link Hint Registry 5.1. HTTP Link Hint Registry . . . . . . . . . . . . . . . . . 9
6. References 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
6.1. Normative References 6.1. Normative References . . . . . . . . . . . . . . . . . . 10
6.2. Informative References 6.2. Informative References . . . . . . . . . . . . . . . . . 11
Appendix A. Representing Link Hints in Link Headers Appendix A. Representing Link Hints in Link Headers . . . . . . 11
Appendix B. Acknowledgements Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 12
Author's Address Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction 1. Introduction
HTTP [HTTP] clients can discover a variety of information about a HTTP [HTTP] clients can discover a variety of information about a
resource by interacting with it. For example, the methods supported resource by interacting with it. For example, the methods supported
can be learned through the Allow response header field, and the need can be learned through the Allow response header field, and the need
for authentication is conveyed with a 401 (Authentication Required) for authentication is conveyed with a 401 (Authentication Required)
status code. status code.
Often, it can be beneficial to know this information before Often, it can be beneficial to know this information before
 End of changes. 5 change blocks. 
28 lines changed or deleted 27 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/