[http-state] [Technical Errata Reported] RFC6265 (4043)

RFC Errata System <rfc-editor@rfc-editor.org> Sun, 06 July 2014 14:32 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: http-state@ietfa.amsl.com
Delivered-To: http-state@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54FF71A0328 for <http-state@ietfa.amsl.com>; Sun, 6 Jul 2014 07:32:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level:
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9xewZk5B9Bh0 for <http-state@ietfa.amsl.com>; Sun, 6 Jul 2014 07:32:14 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id DBE551A031F for <http-state@ietf.org>; Sun, 6 Jul 2014 07:32:14 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id F350F180015; Sun, 6 Jul 2014 07:31:52 -0700 (PDT)
To: abarth@eecs.berkeley.edu, barryleiba@computer.org, presnick@qti.qualcomm.com, Jeff.Hodges@kingsmountain.com
X-PHP-Originating-Script: 6000:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20140706143152.F350F180015@rfc-editor.org>
Date: Sun, 6 Jul 2014 07:31:52 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/http-state/Q_ozU-T_XpzhRBPC0KEedlvAFZ0
Cc: plepropre@gmail.com, rfc-editor@rfc-editor.org, http-state@ietf.org
Subject: [http-state] [Technical Errata Reported] RFC6265 (4043)
X-BeenThere: http-state@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discuss HTTP State Management Mechanism <http-state.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/http-state>, <mailto:http-state-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/http-state/>
List-Post: <mailto:http-state@ietf.org>
List-Help: <mailto:http-state-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-state>, <mailto:http-state-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Jul 2014 14:32:16 -0000

The following errata report has been submitted for RFC6265,
"HTTP State Management Mechanism".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6265&eid=4043

--------------------------------------
Type: Technical
Reported by: Pierre Lepropre <plepropre@gmail.com>;

Section: 5.1.4

Original Text
-------------
The user agent MUST use an algorithm equivalent to the following
algorithm to compute the default-path of a cookie:

Corrected Text
--------------
The user agent MUST use an algorithm equivalent to the following
algorithm to compute the default value for a cookie-path 
(and thereby matching the server-side semantics as defined in 4.1.2.4):

Notes
-----
The term "default-path" is not formally defined before and is quite misleading for the reader 
  A. going through the section 5.1.4 as it's only used there once and not again
     until section 5.2.4 (once again) and 5.3 (once again).
  B. not being a native English speaker

Furthermore, the true meaning of the "default-path" only appears sometime after at section 5.2.4 where it's finally bound altogether. Therefore, my personal recommendation would be to also replace the other occurrences of the "default-path" terms by "default cookie-path"

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC6265 (draft-ietf-httpstate-cookie-23)
--------------------------------------
Title               : HTTP State Management Mechanism
Publication Date    : April 2011
Author(s)           : A. Barth
Category            : PROPOSED STANDARD
Source              : HTTP State Management Mechanism
Area                : Applications
Stream              : IETF
Verifying Party     : IESG