[apps-discuss] Apps area review: draft-ietf-geopriv-rfc3825bis-14
"Vijay K. Gurbani" <vkg@bell-labs.com> Wed, 01 December 2010 22:17 UTC
Return-Path: <vkg@bell-labs.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 52F743A67E5 for <apps-discuss@core3.amsl.com>; Wed, 1 Dec 2010 14:17:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.137
X-Spam-Level:
X-Spam-Status: No, score=-106.137 tagged_above=-999 required=5 tests=[AWL=0.462, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 PadweByKS1es for <apps-discuss@core3.amsl.com>; Wed, 1 Dec 2010 14:17:50 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id C290C3A67DF for <apps-discuss@ietf.org>; Wed, 1 Dec 2010 14:17:49 -0800 (PST)
Received: from umail.lucent.com (h135-3-40-63.lucent.com [135.3.40.63]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id oB1MJ1iJ012350 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Dec 2010 16:19:01 -0600 (CST)
Received: from shoonya.ih.lucent.com (Knoppix-135185238233.ih.lucent.com [135.185.238.233]) by umail.lucent.com (8.13.8/TPES) with ESMTP id oB1MJ1Wo016767; Wed, 1 Dec 2010 16:19:01 -0600 (CST)
Message-ID: <4CF6CA50.6000005@bell-labs.com>
Date: Wed, 01 Dec 2010 16:21:04 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.15) Gecko/20101027 Fedora/3.0.10-1.fc12 Thunderbird/3.0.10
MIME-Version: 1.0
To: draft-ietf-geopriv-rfc3825bis@tools.ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: [apps-discuss] Apps area review: draft-ietf-geopriv-rfc3825bis-14
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Dec 2010 22:17:51 -0000
I have been selected as the Applications Area Review Team reviewer for this draft (for background on apps-review, please see http://www.apps.ietf.org/content/applications-area-review-team). Please resolve these comments along with any other Last Call comments you may receive. Please wait for direction from your document shepherd or AD before posting a new version of the draft. Document: draft-ietf-geopriv-rfc3825bis-14 Title: Dynamic Host Configuration Protocol Options for Coordinate-based Location Configuration Information Reviewer: Vijay K. Gurbani Review Date: Dec-1-2010 IETF Last Call Date: Not known IESG Telechat Date: Dec-2-2010 Summary: This draft is ready for publication as a Proposed Standard. I have some nits that could possibly be addressed. Nits: 1) S1: s/has a range of/is useful for a range of/ 2) In S1, the phrase "where retrieving it might be difficult in practice" --- what is it qualifying? The fact that the information is stored on the end device? or the fact that location information is stored somewhere else on the network? I suspect it is the latter, but just wanted to make sure. It could possibly be reworded as: OLD: An important feature of this specification is that after the relevant DHCP exchanges have taken place, the location information is stored on the end device rather than somewhere else, where retrieving it might be difficult in practice. NEW: An important feature of this specification is that after the relevant DHCP exchanges have taken place, the location information is stored on the end device rather than somewhere else. Storing this information at a place other than the end device makes retrieving it difficult in practice. 3) S1.2, suggested re-write: s/In this document, each of the three axes can be/In this document, each of the three axes --- Latitude, Longitude and Altitude --- can be/ Thanks, - vijay -- Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA) Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org} Web: http://ect.bell-labs.com/who/vkg/
- [apps-discuss] Apps area review: draft-ietf-geopr… Vijay K. Gurbani
- Re: [apps-discuss] Apps area review: draft-ietf-g… Claudio Allocchio