Cookie Extention Limitting Its Availability to User Agent Components
draft-pietrak-cookie-scope-00

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00

Network Working Group                                         R. Pietrak
Internet-Draft                                          February 4, 2021
Intended status: Standards Track
Expires: August 8, 2021

  Cookie Extention Limitting Its Availability to User Agent Components
                     draft-pietrak-cookie-scope-00

Abstract

   This memo addresses cookies security by introduction of an additional
   constraints, web application designer may impose on cookie
   availability for localhost applications components.

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 8, 2021.

Copyright Notice

   Copyright (c) 2021 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Pietrak                  Expires August 8, 2021                 [Page 1]
Internet-Draft             Cookies Local Scope             February 2021

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  CookieRadius attribute  . . . . . . . . . . . . . . . . . . .   4
   4.  Security  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   As of current standard, HTTP state management mechanism RFC 6265
   [refs.RFC6265], provide tools (in the form of cookie attributes) to
   limit the dissemination of any particular cookie.  Those constraints
   are:

   o  Cookie domain

   o  Cookie expiration time

   o  HttpOnly attribute

   o  SecureOnly attribute

   But, current standard doesn't provide means to control the scope
   cookies are available to localhost components, like user agent
   software.  These days search engines provide host of evidence that
   programmers continuesly look for such means.  Usually, the question
   is: "How do I limit my session cookie to just a single tab?".

   The questions comes from evident need to move away out off user
   session-ID (acquired after login/pass veryfication) visible in plain
   sight as part of URL referring to the access limitted pages.  Usually
   such modyfications are evaluated under strict requirement, that
   current functionality remains unaltered.  Here the required
   functionality usually boils down to having such session-ID not shared

Pietrak                  Expires August 8, 2021                 [Page 2]
Internet-Draft             Cookies Local Scope             February 2021

   among interface components which waren't involved in credencials
   veryfication.  Meaning, that only the tab that provided credencials
   (login/pass) will be authorised to access those particular resources.
   In other words: since currently every window and every tab may have a
   diffrent URL retrieved, it should also be possible for it to have
   different (from other tabs) session login credencials.

   This is considered a desired (even required) feature.

   As of now, storing such login session credencials within a Cookie