[Geopriv] Draft publication request for draft-ietf-geopriv-civic-address-recommendations
Richard Barnes <rbarnes@bbn.com> Wed, 25 February 2009 02:58 UTC
Return-Path: <rbarnes@bbn.com>
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 270B83A6911 for <geopriv@core3.amsl.com>; Tue, 24 Feb 2009 18:58:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 DHwON-+3+EXV for <geopriv@core3.amsl.com>; Tue, 24 Feb 2009 18:58:37 -0800 (PST)
Received: from mx3.bbn.com (mx3.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id E6FB53A67AF for <geopriv@ietf.org>; Tue, 24 Feb 2009 18:58:36 -0800 (PST)
Received: from [128.89.254.79] (helo=Richard-Barnes-Laptop.local) by mx3.bbn.com with esmtp (Exim 4.63) (envelope-from <rbarnes@bbn.com>) id 1Lc9z4-0004uW-B5 for geopriv@ietf.org; Tue, 24 Feb 2009 21:58:54 -0500
Message-ID: <49A4B3ED.80901@bbn.com>
Date: Tue, 24 Feb 2009 21:58:53 -0500
From: Richard Barnes <rbarnes@bbn.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: 'GEOPRIV' <geopriv@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [Geopriv] Draft publication request for draft-ietf-geopriv-civic-address-recommendations
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: Wed, 25 Feb 2009 02:58:38 -0000
Please submit comments on the below publication request to the list by Friday, 27 Feb. --RB --------------- The GEOPRIV working group requests publication of draft-ietf-geopriv- civic-address-recommendations-02 as a BCP. (1.a) The Document Shepherd for draft-ietf-geopriv-civic-address-recommendations is Richard Barnes. I have reviewed this version of the document and believe it is ready for IESG consideration. (1.b) The document appears to have had adequate review from people that both deal with civic addresses in different countries and are familiar with the RFC 4776/5139 civic address format. (1.c) I don't believe the document requires focused review from a different perspective. The focus of the document is mapping local data sources (often in different languages) into a common XML format. Calling attention to it from the XML and internalization communities during IETF last call would be appropriate. (1.d) I am not aware of any special concerns the IESG needs to take into consideration. No IPR disclosures have been filed against this document. (1.e) There seems to be solid WG consensus behind this document. Comments on the mailing list have been consistently supportive, and when it was last presented at a GEOPRIV meeting (at IETF 72), several participants spoke in favor. (1.f) I am not aware of any extreme discontent over this document. (1.g) The document satisfies the idnits requirements. (1.h) References are split into normative and informative. All normative references are RFCs. (1.i) The IANA considerations section requests the creation of a registry to store pointers to local civic address standards, consistent with the discussion in the main body of the document. The document does not specify protocol extensions. The IANA registry to be created is clearly identified and described. The shepherd has discussed the expert review requirement with Cullen Jennings, the responsible AD. (1.j) The only formal language used in the document is XML. The shepherd has validated the one complete document (a PIDF-LO example) using the tools at validate.openlaboratory.net, and the snippets given as examples illustrate correct syntax. (1.k) Announcement Text Technical Summary This document provides a guideline for creating civic address consideration documents for individual countries, as required by RFC 4776. Since civic addresses may have a different format in individual countries, such address considerations are necessary in order to map the civic address fields to the PIDF Location Object (PIDF-LO) elements. Working Group Summary This document was reviewed by the GEOPRIV working group, where it has reached consensus for publication as an IETF RFC. Document Quality XML examples in the document validate against relevant schemas. The document itself defines one implementation of its recommendations: In addition to defining guidelines for mappings between local civic address standards and the format of RFC 4776, the document describes such a mapping for addresses within Austria.
- [Geopriv] Draft publication request for draft-iet… Richard Barnes