The "safe" HTTP Preference
draft-nottingham-safe-hint-11

Document Type Active Internet-Draft (individual)
Last updated 2019-08-02
Stream ISE
Intended RFC status Informational
Formats plain text xml pdf html bibtex
Reviews
IETF conflict review conflict-review-nottingham-safe-hint
Stream ISE state In IESG Review
Consensus Boilerplate Yes
Document shepherd Adrian Farrel
Shepherd write-up Show (last changed 2019-04-18)
IESG IESG state I-D Exists (IESG: Dead)
Telechat date
Responsible AD Barry Leiba
Send notices to Adrian Farrel <rfc-ise@rfc-editor.org>
IANA IANA review state IANA OK - Actions Needed
IANA action state None
Network Working Group                                      M. Nottingham
Internet-Draft                                            August 2, 2019
Intended status: Informational
Expires: February 3, 2020

                       The "safe" HTTP Preference
                     draft-nottingham-safe-hint-11

Abstract

   This specification defines a "safe" preference for HTTP requests that
   expresses a desire to avoid objectionable content, according to the
   definition of that term by the origin server.

   This specification does not define a precise semantic for "safe".
   Rather, the term is interpreted by the server and within the scope of
   each Web site that chooses to act upon this information.

   Support for this preference by clients and servers is optional.

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 February 3, 2020.

Copyright Notice

   Copyright (c) 2019 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

Nottingham              Expires February 3, 2020                [Page 1]
Internet-Draft        Preference for Safe Browsing           August 2019

   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  The "safe" Preference . . . . . . . . . . . . . . . . . . . .   4
   3.  Implementation Status . . . . . . . . . . . . . . . . . . . .   5
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .   8
   Appendix B.  Sending "safe" from Web Browsers . . . . . . . . . .   8
   Appendix C.  Supporting "safe" on Web Sites . . . . . . . . . . .   8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   Many Web sites have a "safe" mode, to assist those who don't want to
   be exposed (or have their children exposed) to content to which they
   might object.

   However, that goal is often difficult to achieve, because of the need
   to go to every Web site that might be used, navigate to the
   appropriate page (possibly creating an account along the way) to get
   a cookie [RFC6265] set in the browser, for each browser on every
   device used.

   A more manageable approach is for the browser to proactively indicate
   a preference for safe content.  A user agent that supports doing so
   (whether it be an individual browser, or through an Operating System
   HTTP library) need only be configured once to assure that the
   preference is advertised to a set of sites, or even all sites.

   This specification defines how to declare this desire in requests as
   a HTTP Preference [RFC7240].

   Note that this specification does not define what content might be
   considered objectionable, and so the concept of "safe" is also not
   precisely defined.  Rather, the term is interpreted by the server and
   within the scope of each Web site that chooses to act upon this
   information.

   That said, the intent of "safe" is to allow end users (or those
   acting on their behalf) to express a desire to avoid content that is
   considered objectionable within the cultural context of that site;

Nottingham              Expires February 3, 2020                [Page 2]
Internet-Draft        Preference for Safe Browsing           August 2019

   usually (but not always) content that is unsuitable for minors.  The
   "safe" preference is not intended to be used for other purposes.

   Furthermore, sending "safe" does not guarantee that the Web site will
   use it, nor that it will apply a concept of "objectionable" that is
   consistent with the requester's views.  As such, its effect can be
Show full document text