HyperText Transfer Protocol L. Pardue Internet-Draft Cloudflare Intended status: Standards Track 8 March 2023 Expires: 9 September 2023 HTTP Identity Digest draft-pardue-http-identity-digest-00 Abstract TODO Abstract About This Document This note is to be removed before publishing as an RFC. The latest revision of this draft can be found at https://LPardue.github.io/draft-pardue-http-identity-digest/draft- pardue-http-identity-digest.html. Status information for this document may be found at https://datatracker.ietf.org/doc/draft- pardue-http-identity-digest/. Discussion of this document takes place on the HyperText Transfer Protocol Working Group mailing list (mailto:http-wg@hplb.hp.com), which is archived at https://www.ics.uci.edu/pub/ietf/http/hypermail. Source for this draft and an issue tracker can be found at https://github.com/LPardue/draft-pardue-http-identity-digest. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on 9 September 2023. Pardue Expires 9 September 2023 [Page 1] Internet-Draft HTTP Identity Digest March 2023 Copyright Notice Copyright (c) 2023 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/ license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Conventions and Definitions . . . . . . . . . . . . . . . . . 2 3. Security Considerations . . . . . . . . . . . . . . . . . . . 2 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 5. Normative References . . . . . . . . . . . . . . . . . . . . 2 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 3 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction TODO Introduction 2. Conventions and Definitions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. 3. Security Considerations TODO Security 4. IANA Considerations This document has no IANA actions. 5. Normative References Pardue Expires 9 September 2023 [Page 2] Internet-Draft HTTP Identity Digest March 2023 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . Acknowledgments TODO acknowledge. Author's Address Lucas Pardue Cloudflare Email: lucaspardue.24.7@gmail.com Pardue Expires 9 September 2023 [Page 3]