[dhcwg] Re: Two companion IDs for consideration

nabbott@telcordia.com Tue, 12 November 2002 19:18 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10917 for <dhcwg-archive@odin.ietf.org>; Tue, 12 Nov 2002 14:18:38 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gACJKjM23067 for dhcwg-archive@odin.ietf.org; Tue, 12 Nov 2002 14:20:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACJKjv23064 for <dhcwg-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 14:20:45 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10850 for <dhcwg-web-archive@ietf.org>; Tue, 12 Nov 2002 14:18:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACJIPv22930; Tue, 12 Nov 2002 14:18:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACJ76v22092 for <dhcwg@optimus.ietf.org>; Tue, 12 Nov 2002 14:07:06 -0500
Received: from dnsmx2pya.telcordia.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10545 for <dhcwg@ietf.org>; Tue, 12 Nov 2002 14:04:25 -0500 (EST)
From: nabbott@telcordia.com
Received: from notes900.cc.telcordia.com (notes900.cc.telcordia.com [128.96.79.7]) by dnsmx2pya.telcordia.com (8.9.3/8.9.3) with ESMTP id OAA05315; Tue, 12 Nov 2002 14:06:27 -0500 (EST)
To: dhcwg@ietf.org, geopriv@mail.apps.ietf.org, "James M. Polk" <jmpolk@cisco.com>
X-Mailer: Lotus Notes Release 5.0.5 September 22, 2000
Message-ID: <OFCD86286F.3AAAED4E-ON85256C6F.00682455@cc.telcordia.com>
Date: Tue, 12 Nov 2002 14:06:47 -0500
X-MIMETrack: Serialize by Router on notes900/Telcordia(Release 5.0.6a |January 17, 2001) at 11/12/2002 02:06:48 PM
MIME-Version: 1.0
Content-type: text/plain; charset="us-ascii"
Subject: [dhcwg] Re: Two companion IDs for consideration
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>

All,
I believe the approach described in the afore-mentioned Internet Drafts is
dependent upon both LAN switch and DHCP server support of Circuit-ID RAIO
defined (as SubOpt 1) in RFC 3046, Patrick M., "DHCP Relay Agent
Information Option",  January2001.  Does anyone have any idea how widely
supported these functions are by LAN switches and by DHCP servers?
Thanks,
Nadine Abbott
Telcordia Technologies



                                                                                                
                    "James M.                                                                   
                    Polk"                To:     geopriv@mail.apps.ietf.org                     
                    <jmpolk@cisco        cc:     dhcwg@ietf.org, (bcc: Nadine B.                
                    .com>                Abbott/Telcordia)                                      
                                         Subject:     Two companion IDs for consideration       
                    10/30/2002                                                                  
                    03:44 PM                                                                    
                                                                                                
                                                                                                





All

A few of us have written two companion Drafts for consideration into 2 WGs
(GEOPRIV and DHC).

The first ID (into the DHC WG) is at:
http://www.ietf.org/internet-drafts/draft-polk-dhcp-geo-loc-option-00.txt
and defines a Location Object format that satisfies (we hope) the basic
required elements to represent  a Target as well as the requirement for
granular resolution. This ID in no way affects the GEOPRIV Protocol and
it's goal for security or user control (ie rules for actively responding to
a Location request). It provides a mechanism for getting the location
information to an (wired) IP device which can then use the eventual GEOPRIV
Protocol as that WG specifies. There are no semantics written into the DHC
ID, and leaves some questions as to why the authors made certain choices.
Hence the reason for the second ID.

The second ID (into the GEOPRIV WG) is the semantics ID for the DHC ID.
It's at:
http://www.ietf.org/internet-drafts/draft-polk-geopriv-loc-object-semantics-

00.txt
and shows (with many examples) why the meaning of "resolution" is better
suited to meet the requirement of granular (im)precision than "accuracy".
The examples of how the location Target device can simply alter the
resolution presented to a location request from within 3.11mm x 2.62mm to
as much as 1/6th that of the earth. Neither ID talks about the
circumstances of these choices - the authors believe this normative text
should reside elsewhere in GEOPRIV efforts with whatever rules that WG
places on its Protocol efforts and output.

Questions and comments have already been raised on the IEPREP WG list in
the Transport Area, so this combined effort looks like it will have
multiple lists with comments on them regarding these two IDs.

Comments are encouraged


cheers,
James

              *************************************
"People generally demand more respect for their own rights than
                         they are willing to allow for others"





_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg