An Inquiry into the Nature and the Causes of Web Insecurity
draft-tschofenig-secure-the-web-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-05-09
Stream (None)
Intended RFC status (None)
Formats 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                                          M. Hanson
Internet-Draft                                                   Mozilla
Intended status: Informational                             H. Tschofenig
Expires: November 10, 2012                        Nokia Siemens Networks
                                                               S. Turner
                                                              IECA, Inc.
                                                             May 9, 2012

      An Inquiry into the Nature and the Causes of Web Insecurity
                 draft-tschofenig-secure-the-web-01.txt

Abstract

   The year 2011 has been quite exciting from a Web security point of
   view: a number of high-profile security incidents have gotten a lot
   of press attention but also new initiatives, such as the National
   Strategy for Trusted Identities in Cyberspace (NSTIC), had been
   launched to improve the Web identity eco-system.  The NSTIC strategy
   paper, for example, observes problems with Internet security due to
   the widespread usage of low-entropy passwords and the lack of widely
   deployed authentication and attribute assurance services.

   With this memorandum we try to develop a shared vision for how to
   deal with the most pressing Internet security problems.

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 http://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 November 10, 2012.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Hanson, et al.          Expires November 10, 2012               [Page 1]
Internet-Draft          Memo on Securing the Web                May 2012

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  From Documents to Mobile Code  . . . . . . . . . . . . . .  4
     1.2.  Mashups and Data Sharing . . . . . . . . . . . . . . . . .  4
     1.3.  The Real-Time Web  . . . . . . . . . . . . . . . . . . . .  4
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  6
   3.  Passwords  . . . . . . . . . . . . . . . . . . . . . . . . . .  7
   4.  Roadmap for the Future . . . . . . . . . . . . . . . . . . . .  9
   5.  From Two-Party to N-Party  . . . . . . . . . . . . . . . . . . 12
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 14
   7.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 15
   8.  Open Issues  . . . . . . . . . . . . . . . . . . . . . . . . . 16
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
     9.1.  Normative References . . . . . . . . . . . . . . . . . . . 17
     9.2.  Informative References . . . . . . . . . . . . . . . . . . 17
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19

Hanson, et al.          Expires November 10, 2012               [Page 2]
Internet-Draft          Memo on Securing the Web                May 2012

1.  Introduction

   HTTP is an IETF standard and documented in RFC 2616 [RFC2616] and
   provides the core foundation of the browser-based platform but is
   also widely used for non-browser-based applications.  Like any other
   specification in the IETF HTTP also comes with various security
   mechanims.  Digest authentication support in HTTP was published in
   1997 with RFC 2069 [RFC2069] and later updated in 1999 by RFC 2617
   [RFC2617].  The HTTP state management mechanism, namely cookies, was
   initially published in 1997 with RFC 2109 [RFC2109], and re-written
   in 2000 by RFC 2965 [RFC2965].

   For client side authentication two different solution tracks have
   therefore been offered from the IETF, namely TLS client side
   authenication (at that time using certificates) and also application
Show full document text