<?xml version="1.0" encoding="UTF-8"?>
<!--
    This XML document is the output of clean-for-DTD.xslt; a tool that strips
    extensions to RFC2629(bis) from documents for processing with xml2rfc.
-->
<!--TARGET-GENERATOR: 201706-->
<?xml-stylesheet type='text/xsl' href='lib/myxml2rfc.xslt'?>
<?rfc toc="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes" ?>
<?rfc compact="yes"?>
<?rfc subcompact="no" ?>
<?rfc linkmailto="no" ?>
<?rfc editing="no" ?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc rfcedstyle="yes"?>
<!DOCTYPE rfc
  SYSTEM "rfc2629.dtd">
<rfc category="std" ipr="pre5378Trust200902" docName="draft-ietf-httpbis-auth-01">

<front><title>HTTP Authentication</title><author fullname="Roy T. Fielding" initials="R." surname="Fielding" role="editor">
    <organization>Adobe</organization>
    <address>
      <postal>
        <street>345 Park Ave</street>
        <city>San Jose</city>
        <region>CA</region>
        <code>95110</code>
        <country>USA</country>
      </postal>
      <email>fielding@gbiv.com</email>
      <uri>https://roy.gbiv.com/</uri>
    </address>
  </author><author fullname="Mark Nottingham" initials="M." surname="Nottingham" role="editor">
    <organization>Fastly</organization>
    <address>
      <email>mnot@mnot.net</email>
      <uri>https://www.mnot.net/</uri>
    </address>
  </author><author fullname="Julian F. Reschke" initials="J. F." surname="Reschke" role="editor">
    <organization abbrev="greenbytes">greenbytes GmbH</organization>
    <address>
      <postal>
        <street>Hafenweg 16</street>
        <city>Muenster</city><region>NW</region><code>48155</code>
        <country>Germany</country>
      </postal>
      <email>julian.reschke@greenbytes.de</email>
      <uri>https://greenbytes.de/tech/webdav/</uri>
    </address>
  </author><date month="May" year="2018" day="31"/>

  

  

  

  

  

  <area>Applications and Real-Time</area>
  <workgroup>HTTP Working Group</workgroup>

  <keyword>Hypertext Transfer Protocol</keyword>
  <keyword>HTTP</keyword>
  <keyword>HTTP authentication</keyword>

<abstract>
<t>
   The Hypertext Transfer Protocol (HTTP) is a stateless application-level
   protocol for distributed, collaborative, hypermedia information systems.
   This document formerly defined the HTTP Authentication framework, which
   has since been moved to the core HTTP Semantics document.
</t>
</abstract>

<note title="Editorial Note"><t>This note is to be removed before publishing as an RFC.</t>
  <t>
    Discussion of this draft takes place on the HTTP working group
    mailing list (ietf-http-wg@w3.org), which is archived at
    <eref target="https://lists.w3.org/Archives/Public/ietf-http-wg/"/>.
  </t>
  <t>
    Working Group information can be found at <eref target="https://httpwg.org/"/>;
    source code and issues list for this draft can be found at
    <eref target="https://github.com/httpwg/http-core"/>.
  </t>
  <t>
    The changes in this draft are summarized in <xref target="changes.since.00"/>.
  </t>
</note>
</front>
<middle>
<section anchor="introduction" title="Introduction">
<t>
   HTTP provides a general framework for access control and authentication,
   via an extensible set of challenge-response authentication schemes, which
   can be used by a server to challenge a client request and by a client to
   provide authentication information.
 </t>
 <t>
   The entire content of this document (previously in
   <xref target="RFC2617"/> and <xref target="RFC7235"/>)
   has been moved to <xref target="Semantics"/>.
</t>
</section>
</middle>

<back>

<references title="Normative References">

<reference anchor="Semantics"><front><title>HTTP Semantics</title><author fullname="Roy T. Fielding" initials="R." surname="Fielding" role="editor">
    <organization>Adobe</organization>
    <address>
      <postal>
        <street>345 Park Ave</street>
        <city>San Jose</city>
        <region>CA</region>
        <code>95110</code>
        <country>USA</country>
      </postal>
      <email>fielding@gbiv.com</email>
      <uri>https://roy.gbiv.com/</uri>
    </address>
  </author><author fullname="Mark Nottingham" initials="M." surname="Nottingham" role="editor">
    <organization>Fastly</organization>
    <address>
      <email>mnot@mnot.net</email>
      <uri>https://www.mnot.net/</uri>
    </address>
  </author><author fullname="Julian F. Reschke" initials="J. F." surname="Reschke" role="editor">
    <organization abbrev="greenbytes">greenbytes GmbH</organization>
    <address>
      <postal>
        <street>Hafenweg 16</street>
        <city>Muenster</city><region>NW</region><code>48155</code>
        <country>Germany</country>
      </postal>
      <email>julian.reschke@greenbytes.de</email>
      <uri>https://greenbytes.de/tech/webdav/</uri>
    </address>
  </author><date month="May" year="2018" day="31"/>

  

  

  

  

  

  <area>Applications and Real-Time</area>
  <workgroup>HTTP Working Group</workgroup>

  <keyword>Hypertext Transfer Protocol</keyword>
  <keyword>HTTP</keyword>
  <keyword>HTTP semantics</keyword>
  <keyword>HTTP payload</keyword>
  <keyword>HTTP content</keyword>
  <keyword>HTTP method</keyword>
  <keyword>HTTP status code</keyword>

<abstract>
<t>
   The Hypertext Transfer Protocol (HTTP) is a stateless application-level
   protocol for distributed, collaborative, hypertext information systems.
   This document defines the semantics of HTTP: its architecture,
   terminology, the "http" and "https" Uniform Resource Identifier (URI)
   schemes, core request methods, request header fields, response status
   codes, response header fields, and content negotiation.
</t>
<t>
   This document obsoletes RFC 7231, RFC 7232, RFC 7233,
   RFC 7235, and portions of RFC 7230.
</t>
</abstract>

<note title="Editorial Note"><t>This note is to be removed before publishing as an RFC.</t>
  <t>
    Discussion of this draft takes place on the HTTP working group
    mailing list (ietf-http-wg@w3.org), which is archived at
    <eref target="https://lists.w3.org/Archives/Public/ietf-http-wg/"/>.
  </t>
  <t>
    Working Group information can be found at <eref target="https://httpwg.org/"/>;
    source code and issues list for this draft can be found at
    <eref target="https://github.com/httpwg/http-core"/>.
  </t>
  <t>
    The changes in this draft are summarized in <xref target="changes.since.00"/>.
  </t>
</note>
</front><seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-semantics-01"/></reference>

</references>

<references title="Informative References">

<reference anchor="RFC2617" target="https://www.rfc-editor.org/info/rfc2617"><front><title abbrev="HTTP Authentication">HTTP Authentication: Basic and Digest Access Authentication</title><author initials="J." surname="Franks" fullname="John Franks">
      <organization>Northwestern University, Department of Mathematics</organization>
      <address><email>john@math.nwu.edu</email></address>
    </author><author initials="P.M." surname="Hallam-Baker" fullname="Phillip M. Hallam-Baker">
      <organization>Verisign Inc.</organization>
      <address><email>pbaker@verisign.com</email></address>
    </author><author initials="J.L." surname="Hostetler" fullname="Jeffery L. Hostetler">
      <organization>AbiSource, Inc.</organization>
      <address><email>jeff@AbiSource.com</email></address>
    </author><author initials="S.D." surname="Lawrence" fullname="Scott D. Lawrence">
      <organization>Agranat Systems, Inc.</organization>
      <address><email>lawrence@agranat.com</email></address>
    </author><author initials="P.J." surname="Leach" fullname="Paul J. Leach">
      <organization>Microsoft Corporation</organization>
      <address><email>paulle@microsoft.com</email></address>
    </author><author initials="A." surname="Luotonen" fullname="Ari Luotonen">
      <organization>Netscape Communications Corporation</organization>
    </author><author initials="L." surname="Stewart" fullname="Lawrence C. Stewart">
      <organization>Open Market, Inc.</organization>
      <address><email>stewart@OpenMarket.com</email></address>
    </author><date month="June" year="1999"/>
    
    
    
    
    
    
    
    
    
  </front><seriesInfo name="RFC" value="2617"/><seriesInfo name="DOI" value="10.17487/RFC2617"/></reference>

<reference anchor="RFC7235" target="https://www.rfc-editor.org/info/rfc7235"><front><title>Hypertext Transfer Protocol (HTTP/1.1): Authentication</title><author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
      <organization>Adobe</organization>
      <address><email>fielding@gbiv.com</email></address>
    </author><author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
      <organization abbrev="greenbytes">greenbytes GmbH</organization>
      <address><email>julian.reschke@greenbytes.de</email></address>
    </author><date month="June" year="2014"/>
    
    
    
    
  </front><seriesInfo name="RFC" value="7235"/><seriesInfo name="DOI" value="10.17487/RFC7235"/></reference>
</references>

<section anchor="changes.since.00" title="Changes from RFC 7235">
<t>
  All content has been moved to <xref target="Semantics"/>.
</t>
</section>

<section anchor="acks" numbered="false" title="Acknowledgments">
<t>
  See Appendix "Acknowledgments" of <xref target="Semantics"/>.
</t>
</section>
</back>
</rfc>