[Geopriv] [Technical Errata Reported] RFC3693 (4621)
RFC Errata System <rfc-editor@rfc-editor.org> Wed, 17 February 2016 19:56 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 83E591A8A51 for <geopriv@ietfa.amsl.com>; Wed, 17 Feb 2016 11:56:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.908
X-Spam-Level:
X-Spam-Status: No, score=-101.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 P3Ss88fr7GXe for <geopriv@ietfa.amsl.com>; Wed, 17 Feb 2016 11:56:40 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3770C1A882F for <geopriv@ietf.org>; Wed, 17 Feb 2016 11:56:40 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 8C343180471; Wed, 17 Feb 2016 11:56:26 -0800 (PST)
To: Jorge.Cuellar@siemens.com, jmorris@cdt.org, dmulligan@law.berkeley.edu, jon.peterson@neustar.biz, jmpolk@cisco.com, ben@nostrum.com, alissa@cooperw.in, ray.bellis@nominet.org.uk
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20160217195626.8C343180471@rfc-editor.org>
Date: Wed, 17 Feb 2016 11:56:26 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/geopriv/Hg32mioLXGw76-rciq9BU1vYPNw>
X-Mailman-Approved-At: Wed, 02 Mar 2016 08:02:22 -0800
Cc: geopriv@ietf.org, jra@baylink.com, rfc-editor@rfc-editor.org
Subject: [Geopriv] [Technical Errata Reported] 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: Wed, 17 Feb 2016 19:56:41 -0000
The following errata report has been submitted for RFC3693, "Geopriv Requirements". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=3693&eid=4621 -------------------------------------- Type: Technical Reported by: Jay R. Ashworth <jra@baylink.com> 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. Instructions: ------------- This erratum 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. -------------------------------------- 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
- [Geopriv] [Technical Errata Reported] RFC3693 (46… RFC Errata System
- [Geopriv] [Errata Held for Document Update] RFC36… RFC Errata System