HTTP Resources with User Names
draft-vanrein-http-unauth-user-05

Document Type Active Internet-Draft (individual)
Last updated 2020-02-03
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        R. Van Rein
Internet-Draft                                          InternetWide.org
Intended status: Standards Track                        February 3, 2020
Expires: August 6, 2020

                     HTTP Resources with User Names
                   draft-vanrein-http-unauth-user-05

Abstract

   Many protocols support users under domain names, but HTTP does not.

   This specification defines a header for user names, independent of
   authenticated identities, and a link to userinfo in HTTP URIs.  This
   intergrates naturally with HTTP, and results in a more refined
   resource authentication model, in support of advanced usage
   scenarios.

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 August 6, 2020.

Copyright Notice

   Copyright (c) 2020 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 Simplified BSD License text as described in Section 4.e of

Van Rein                 Expires August 6, 2020                 [Page 1]
Internet-Draft                 HTTP user@                  February 2020

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Definition of the HTTP User Header  . . . . . . . . . . . . .   3
   3.  URI with Resource User  . . . . . . . . . . . . . . . . . . .   3
   4.  Protocol Handling of URI and User Header  . . . . . . . . . .   4
   5.  The Logic of User in HTTP . . . . . . . . . . . . . . . . . .   5
   6.  Environment Variable with Local User  . . . . . . . . . . . .   6
   7.  Orthogonality of Authentication (Example) . . . . . . . . . .   6
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   8
     10.2.  Informative References . . . . . . . . . . . . . . . . .   9
   Appendix A.  Compatibility with Basic Authentication  . . . . . .   9
   Appendix B.  Compatibility with RESTful Patterns  . . . . . . . .  10
   Appendix C.  Compatibility with Caching . . . . . . . . . . . . .  10
   Appendix D.  Acknowledgements . . . . . . . . . . . . . . . . . .  11
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   Many protocols support global identities like john@example.com to
   represent users like john under domains such as example.com.  The URI
   format for HTTP can express [Section 2.7.1 of [RFC7230]] such
   authority components (with a userid named "resource user" herein),
   with an intended interpretation of locating user-specific resources.
   Many online applications publish resources on individual users, but
   there is no standard in HTTP to express user names to address them.
   This specification adds that through a header "User", closely
   paralleling the "Host" header.

   Some current URIs for HTTP have used the userinfo field in the URI to
   express an authentication user (named "client identity" herein), in
   spite of the intended use to refine the authority information.  This
   conflates the resource user with the client identity.  This
   specification defines client identity and resource user as orthogonal
   concepts, and specifies a clear relation to the URI format.

   Orthogonality yields a generalisation, but voluntary conflation of
   client identity and resource user remains possible.  In fact,
   software may use it as default behaviour.  Servers can be configured
   with resource users that demand authentication with the same client
   identity; they may even accept authentication with a client identity
   as a bypass to the same resource user.  Clients may accept

Van Rein                 Expires August 6, 2020                 [Page 2]
Show full document text