[Geopriv] [Errata Held for Document Update] RFC3693 (4621)

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 18 February 2016 22:52 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: geopriv@ietfa.amsl.com
Delivered-To: geopriv@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 653031B3671; Thu, 18 Feb 2016 14:52:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.908
X-Spam-Level:
X-Spam-Status: No, score=-106.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.006, 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 p0aKhP3qUFq1; Thu, 18 Feb 2016 14:52:37 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E30911B3390; Thu, 18 Feb 2016 14:52:37 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id C56BE181D1F; Thu, 18 Feb 2016 14:52:20 -0800 (PST)
To: jra@baylink.com, Jorge.Cuellar@siemens.com, jmorris@cdt.org, dmulligan@law.berkeley.edu, jon.peterson@neustar.biz, jmpolk@cisco.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20160218225220.C56BE181D1F@rfc-editor.org>
Date: Thu, 18 Feb 2016 14:52:20 -0800 (PST)
Archived-At: <http://mailarchive.ietf.org/arch/msg/geopriv/jEWge4PRELtwMf-Ob7hqGn0SzXk>
X-Mailman-Approved-At: Wed, 02 Mar 2016 08:02:22 -0800
Cc: geopriv@ietf.org, iesg@ietf.org, rfc-editor@rfc-editor.org
Subject: [Geopriv] [Errata Held for Document Update] RFC3693 (4621)
X-BeenThere: geopriv@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Geographic Location/Privacy <geopriv.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/geopriv>, <mailto:geopriv-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/geopriv/>
List-Post: <mailto:geopriv@ietf.org>
List-Help: <mailto:geopriv-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Feb 2016 22:52:39 -0000

The following errata report has been held for document update 
for RFC3693, "Geopriv Requirements". 

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

--------------------------------------
Status: Held for Document Update
Type: Editorial

Reported by: Jay R. Ashworth <jra@baylink.com>;
Date Reported: 2016-02-17
Held by: Alissa Cooper (IESG)

Section: 8.1

Original Text
-------------
This means that Geopriv may not as a general matter, 
secure the Target against general traffic analysis attacks 
or other forms of privacy violations.

Corrected Text
--------------
This means that Geopriv might not, as a general matter, 
secure the Target against general traffic analysis attacks 
or other forms of privacy violations.

Notes
-----
Aside from the missing comma on the parenthetical, the use of MAY NOT, even uncapitalized, appears to collide with RFC 2119: It's pretty clear the authors intended to say that there may exist conditions in which Geopriv won't secure targets, but the chosen wording, interpreted in context of 2119, means that Geopriv *will not* or *must not* secure Targets, and that interpretation is sort of bogus.

In short: May here is directive, rather than predictive/descriptive, which seems what was intended.

--------------------------------------
RFC3693 (draft-ietf-geopriv-reqs-04)
--------------------------------------
Title               : Geopriv Requirements
Publication Date    : February 2004
Author(s)           : J. Cuellar, J. Morris, D. Mulligan, J. Peterson, J. Polk
Category            : INFORMATIONAL
Source              : Geographic Location/Privacy
Area                : Real-time Applications and Infrastructure
Stream              : IETF
Verifying Party     : IESG