draft-nottingham-safe-hint-03.txt   draft-nottingham-safe-hint-04.txt 
Network Working Group M. Nottingham Network Working Group M. Nottingham
Internet-Draft Internet-Draft
Intended status: Standards Track August 6, 2014 Intended status: Standards Track September 2, 2014
Expires: February 7, 2015 Expires: March 6, 2015
The "safe" HTTP Preference The "safe" HTTP Preference
draft-nottingham-safe-hint-03 draft-nottingham-safe-hint-04
Abstract Abstract
This specification defines a "safe" preference for HTTP requests, This specification defines a "safe" preference for HTTP requests,
expressing a desire to avoid "objectionable" content. expressing a desire to avoid "objectionable" content.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 31 skipping to change at page 1, line 31
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 7, 2015. This Internet-Draft will expire on March 6, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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
skipping to change at page 5, line 5 skipping to change at page 4, line 49
to note that other implementations may exist. to note that other implementations may exist.
o Microsoft Internet Explorer - see http://support.microsoft.com/ o Microsoft Internet Explorer - see http://support.microsoft.com/
kb/2980016 kb/2980016
o Microsoft Bing o Microsoft Bing
o Mozilla Firefox - see https://bugzilla.mozilla.org/ o Mozilla Firefox - see https://bugzilla.mozilla.org/
show_bug.cgi?id=995070 show_bug.cgi?id=995070
o Cisco - see http://blogs.cisco.com/security/filtering-explicit-
content
4. Security Considerations 4. Security Considerations
The "safe" preference is not a secure mechanism; it can be inserted The "safe" preference is not a secure mechanism; it can be inserted
or removed by intermediaries with access to the request stream. Its or removed by intermediaries with access to the request stream. Its
presence reveals limited information about the user, which may be of presence reveals limited information about the user, which may be of
small assistance in "fingerprinting" the user. small assistance in "fingerprinting" the user.
By its nature, including "safe" in requests does not assure that all By its nature, including "safe" in requests does not assure that all
content will actually be safe; it is only when servers elect to honor content will actually be safe; it is only when servers elect to honor
it that content might be "safe". it that content might be "safe".
 End of changes. 4 change blocks. 
4 lines changed or deleted 7 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/