[Geopriv] [Editorial Errata Reported] RFC5491 (1888)
RFC Errata System <rfc-editor@rfc-editor.org> Tue, 22 September 2009 05:23 UTC
Return-Path: <web-usrn@ISI.EDU>
X-Original-To: geopriv@core3.amsl.com
Delivered-To: geopriv@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D049F3A68A5 for <geopriv@core3.amsl.com>; Mon, 21 Sep 2009 22:23:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.899
X-Spam-Level:
X-Spam-Status: No, score=-16.899 tagged_above=-999 required=5 tests=[AWL=0.700, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qmi-o9nu0nSU for <geopriv@core3.amsl.com>; Mon, 21 Sep 2009 22:23:32 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 6C85D3A693F for <geopriv@ietf.org>; Mon, 21 Sep 2009 22:23:32 -0700 (PDT)
Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n8M5N0cT002499; Mon, 21 Sep 2009 22:23:01 -0700 (PDT)
Received: (from web-usrn@localhost) by boreas.isi.edu (8.13.8/8.13.8/Submit) id n8M5Mxqp002497; Mon, 21 Sep 2009 22:22:59 -0700 (PDT)
Date: Mon, 21 Sep 2009 22:22:59 -0700
Message-Id: <200909220522.n8M5Mxqp002497@boreas.isi.edu>
To: james.winterbottom@andrew.com, martin.thomson@andrew.com, Hannes.Tschofenig@gmx.net, rjsparks@nostrum.com, fluffy@cisco.com, rbarnes@bbn.com, acooper@cdt.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: web-usrn@boreas.isi.edu
X-Mailman-Approved-At: Tue, 22 Sep 2009 06:28:35 -0700
Cc: geopriv@ietf.org, rfc-editor@rfc-editor.org
Subject: [Geopriv] [Editorial Errata Reported] RFC5491 (1888)
X-BeenThere: geopriv@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Geographic Location/Privacy <geopriv.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 22 Sep 2009 05:23:34 -0000
The following errata report has been submitted for RFC5491, "GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and Recommendations". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5491&eid=1888 -------------------------------------- Type: Editorial Reported by: Martin Thomson <martin.thomson@andrew.com> Section: 3 Original Text ------------- The PIDF format provides for an unbounded number of <tuple>, <device>, and <person> elements. Each of these elements contains a single <status> element that may contain more than one <geopriv> element as a child. Corrected Text -------------- The PIDF format provides for an unbounded number of <tuple>, <device>, and <person> elements. Each of these elements may contain more than one <geopriv> element. Notes ----- <status> only exists in <tuple> [RFC3863], not <device> or <person> [RFC4479]. The proposed text removes the problem. I believe that it was only late that someone pointed out that <status> only applied to <tuple>; this sentence obviously got missed in the edit. 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. -------------------------------------- RFC5491 (draft-ietf-geopriv-pdif-lo-profile-14) -------------------------------------- Title : GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and Recommendations Publication Date : March 2009 Author(s) : J. Winterbottom, M. Thomson, H. Tschofenig Category : PROPOSED STANDARD Source : Geographic Location/Privacy Area : Real-time Applications and Infrastructure Stream : IETF Verifying Party : IESG
- [Geopriv] [Editorial Errata Reported] RFC5491 (18… RFC Errata System