Re: [Geopriv] WG Review: Recharterof GeographicLocation/Privacy (geopriv)
"James M. Polk" <jmpolk@cisco.com> Thu, 18 June 2009 06:04 UTC
Return-Path: <jmpolk@cisco.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 56B633A6B2E; Wed, 17 Jun 2009 23:04:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.805
X-Spam-Level:
X-Spam-Status: No, score=-5.805 tagged_above=-999 required=5 tests=[AWL=-0.602, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
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 Pr+evAA30Csa; Wed, 17 Jun 2009 23:04:52 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id C0ED23A689A; Wed, 17 Jun 2009 23:04:52 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,242,1243814400"; d="scan'208";a="170917158"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-3.cisco.com with ESMTP; 18 Jun 2009 06:05:05 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n5I652DK020704; Wed, 17 Jun 2009 23:05:02 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n5I652kL019041; Thu, 18 Jun 2009 06:05:02 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 17 Jun 2009 23:05:01 -0700
Received: from jmpolk-wxp01.cisco.com ([10.89.2.90]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 17 Jun 2009 23:05:01 -0700
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 18 Jun 2009 01:04:59 -0500
To: "Dawson, Martin" <Martin.Dawson@andrew.com>, Brian Rosen <br@brianrosen.net>, "Thomson, Martin" <Martin.Thomson@andrew.com>, Cullen Jennings <fluffy@cisco.com>, g.caron@bell.ca
From: "James M. Polk" <jmpolk@cisco.com>
In-Reply-To: <EB921991A86A974C80EAFA46AD428E1E05E5D26C@aopex4.andrew.com >
References: <20090609160001.E4AF63A69D1@core3.amsl.com> <0FEAC1C09868B34A982F4FB40254B37C2744BA720A@MBX02.bell.corp.bce.ca> <3BD20D56-D50F-4DB8-8961-573FB63CB20B@cisco.com> <E51D5B15BFDEFD448F90BDD17D41CFF105E7D335@AHQEX1.andrew.com> <01d101c9efa0$26af5380$740dfa80$@net> <EB921991A86A974C80EAFA46AD428E1E05E5D26C@aopex4.andrew.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Message-ID: <XFE-SJC-212dsnvUFcx000010b7@xfe-sjc-212.amer.cisco.com>
X-OriginalArrivalTime: 18 Jun 2009 06:05:01.0255 (UTC) FILETIME=[B7378D70:01C9EFDA]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=12359; t=1245305105; x=1246169105; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jmpolk@cisco.com; z=From:=20=22James=20M.=20Polk=22=20<jmpolk@cisco.com> |Subject:=20Re=3A=20[Geopriv]=20WG=20Review=3A=0A=20=20Rech arterof=09GeographicLocation/Privacy=09(geopriv) |Sender:=20; bh=91cGrf9RycyPiyJ7qriWW8dpgdawn9iwZ9TWy190hiQ=; b=FTP2Lq/WRYl2NQ1YRhEWjtMl1XkPqB+6ACgGfZdz9M56cQln8Tr4TekJxz nv4BDBAoi3fM40dXdDhtPtBzycVkikpNN6nDKXndQCzcUUvp8FZMwBpT+eBa IsMxL8zxll;
Authentication-Results: sj-dkim-2; header.From=jmpolk@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; );
Cc: geopriv@ietf.org, iesg@ietf.org
Subject: Re: [Geopriv] WG Review: Recharterof GeographicLocation/Privacy (geopriv)
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: Thu, 18 Jun 2009 06:04:54 -0000
Martin Thinking out loud - what's preventing those stakeholders from implementing what's in the identity ext work? Surely it's not because it's not an RFC..? James At 11:36 PM 6/17/2009, Dawson, Martin wrote: >While that matter of degree is open to >interpretation, we've heard from a number of >stakeholders who actually need to implement the >identity extension work. Can the same be said for filters? > >Cheers, >Martin > >-----Original Message----- >From: geopriv-bounces@ietf.org >[mailto:geopriv-bounces@ietf.org] On Behalf Of Brian Rosen >Sent: Thursday, 18 June 2009 9:06 AM >To: Thomson, Martin; 'Cullen Jennings'; g.caron@bell.ca >Cc: geopriv@ietf.org; iesg@ietf.org >Subject: Re: [Geopriv] WG Review: Recharterof >GeographicLocation/Privacy (geopriv) > >Although the XML is undergoing substantial >change, the basic filter mechanisms have, I >believe, stabilized. In conjunction with the >throttle and basic 4661 filter, when we get the >XML right (meaning, in alignment with 4661), then I think we're done. > >So, I don't think it's far less mature. > >Brian > > > -----Original Message----- > > From: geopriv-bounces@ietf.org [mailto:geopriv-bounces@ietf.org] On > > Behalf Of Thomson, Martin > > Sent: Tuesday, June 16, 2009 9:32 PM > > To: Cullen Jennings; g.caron@bell.ca > > Cc: geopriv@ietf.org; iesg@ietf.org > > Subject: Re: [Geopriv] WG Review: Recharter of > > GeographicLocation/Privacy (geopriv) > > > > The work on filters is far less mature than the identity work. Unless > > Brian has hidden wonders in store, I'd suggest that that work can wait. > > > > --Martin > > > > > -----Original Message----- > > > From: geopriv-bounces@ietf.org [mailto:geopriv-bounces@ietf.org] On > > > Behalf Of Cullen Jennings > > > Sent: Wednesday, 17 June 2009 8:27 AM > > > To: <g.caron@bell.ca> > > > Cc: geopriv@ietf.org; iesg@ietf.org > > > Subject: Re: [Geopriv] WG Review: Recharter of > > > GeographicLocation/Privacy (geopriv) > > > > > > > > > Would people advise that we remove any of the currently proposed > > > milestones until after the identity and work it depends on got > > > completed? > > > > > > On Jun 16, 2009, at 7:33 , <g.caron@bell.ca> <g.caron@bell.ca> wrote: > > > > > > > Hi, > > > > > > > > I kindly ask that draft-winterbottom-geopriv-held-identity- > > > > extensions be considered for inclusion in the rechartered geopriv > > > > Goals and Milestones. As discussed at the June 2008 geopriv interim > > > > meeting, this extension to the basic HELD protocol is required for > > > > some deployments. > > > > > > > > Thanks, > > > > > > > > Guy > > > > > > > > -----Message d'origine----- > > > > De : geopriv-bounces@ietf.org [mailto:geopriv-bounces@ietf.org] De > > > > la part de IESG Secretary > > > > Envoyé : 9 juin 2009 12:00 > > > > À : ietf-announce@ietf.org > > > > Cc : geopriv@ietf.org > > > > Objet : [Geopriv] WG Review: Recharter of Geographic Location/ > > > > Privacy (geopriv) > > > > > > > > A modified charter has been submitted for the Geographic Location/ > > > > Privacy > > > > (geopriv) working group in the Real-time Applications and > > > > Infrastructure > > > > Area of the IETF. The IESG has not made any determination as yet. > > > > The > > > > modified charter is provided below for informational purposes only. > > > > Please send your comments to the IESG mailing list (iesg@ietf.org) > > by > > > > Tuesday, June 16, 2009. > > > > > > > > > > > > Geographic Location/Privacy (geopriv) > > > > -------------------------------------- > > > > Last Modified: 2009-05-29 > > > > > > > > Chair(s): > > > > - Richard Barnes <rbarnes@bbn.com> > > > > - Alissa Cooper <acooper@cdt.org> > > > > > > > > Real-time Applications and Infrastructure Area Director(s): > > > > - Robert Sparks <rjsparks@nostrum.com> > > > > - Cullen Jennings <fluffy@cisco.com> > > > > > > > > Real-time Applications and Infrastructure Area Advisor: > > > > - Cullen Jennings <fluffy@cisco.com> > > > > > > > > Technical Advisor(s): > > > > - Lisa Dusseault <Lisa.Dusseault@messagingarchitects.com> > > > > > > > > Mailing Lists: > > > > General Discussion: geopriv@ietf.org > > > > To Subscribe: geopriv-request@ietf.org > > > > In Body: subscribe > > > > Archive: http://www.ietf.org/mail-archive/web/geopriv/index.html > > > > > > > > Description of Working Group: > > > > > > > > The IETF has recognized that many applications are emerging that > > > > require geographic and civic location information about resources > > and > > > > entities, and that the representation and transmission of that > > > > information has significant privacy and security implications. We > > > have > > > > created a suite of protocols that allow such applications to > > > represent > > > > and transmit such location objects and to allow users to express > > > > policies on how these representations are exposed and used. The > > IETF > > > > has also begun working on creating applications that use these > > > > capabilities, for emergency services, general real-time > > > communication, > > > > and other usages. > > > > > > > > The GEOPRIV working group is chartered to continue to develop and > > > > refine representations of location in Internet protocols, and to > > > > analyze the authorization, integrity, and privacy requirements that > > > > must be met when these representations of location are created, > > > > stored, and used. The group will create and refine mechanisms for > > the > > > > transmission of these representations that address the requirements > > > > that have been identified. > > > > > > > > The working group will work with other IETF working groups and > > other > > > > standards development organizations that are building applications > > > > that use location information to ensure that the requirements are > > > well > > > > understood and met, and that no additional security or privacy > > issues > > > > related to location are left unaddressed as these location > > > information > > > > is incorporated into other protocols. > > > > > > > > It remains a goal of the GEOPRIV working group to deliver > > > > specifications of broad applicability that will become mandatory to > > > > implement for IETF protocols that are location aware. > > > > > > > > This working group will not develop location-determining > > technology. > > > > However, the IETF acknowledges that information used in the > > location- > > > > determination process will in some cases need to be carried over > > the > > > > Internet. Where necessary, this working group will develop > > protocols > > > > or protocol extensions to encode location-determination data > > > > structures defined elsewhere. This working group will not develop > > > > technologies to directly address any particular regulatory > > > > requirements (e.g. 9-1-1). The group will continue to coordinate > > with > > > > any other IETF entities that are working on those problems to > > ensure > > > > the technologies created here meet the needs of those entities, and > > > > that the authorization, integrity, and privacy requirements on the > > > > mechanisms provided by these technologies continue to be met. > > > > > > > > Goals and Milestones: > > > > > > > > Done Discuss initial geopriv scenarios and application requirements > > > > i-d's > > > > Done Discuss initial geographic location privacy and security > > > > requirements i-d. > > > > Done Initial i-d on geographic information protocol design, > > including > > > > privacy and security techniques. > > > > Done Review charter and initial i-ds with AD, and have IESG > > consider > > > > rechartering if necessary. > > > > Done Submit geopriv scenarios and application requirements to IESG > > > for > > > > publication as Informational RFCs > > > > Done Submit security/privacy requirements I-D to IESG for > > publication > > > > As Informational RFC. > > > > Done Submit PIDF-LO basic geopriv object draft as a PS > > > > Done Initial Common Rules base object draft > > > > Done Initial Common Rules GEOPRIV object draft > > > > Done Submit DHCP Civil draft as a PS > > > > Done Resubmit Conveying Location Objects in RADIUS and Diameter to > > > > the IESG for publication as PS > > > > Done Submit Additional Civic PIDF-LO types (updating 4119) to the > > > > IESG for publication as PS > > > > Done Submit minimal HTTP based protocol satisfying baseline > > > > requirements specified in the Layer 7 Location Conveyance > > > Protocol > > > > Problem Statement and Requirements to the IESG for publication > > as > > > > PS > > > > Done Submit PIDF-LO Usage Clarifications and Recommendations > > > > (updating 4119) to the IESG for publication as PS > > > > Done Submit Layer 7 Location Conveyance Protocol Problem Statement > > > > and Requirements to the IESG for publication as Informational > > > > Done Submit recommendations for representing civic addresses in > > > > PIDF-LO to the IESG for publication as BCP > > > > Done Submit Recommendations for Retransmission in SIP Location > > > > Conveyance to the IESG for publication as Informational > > > > Done Submit Requirements for Location by Reference Protocols to > > > > the IESG for publication as Informational > > > > Done Submit a LIS Discovery Mechanism to the IESG for publication > > as > > > a > > > > PS > > > > Jun 2009 Resubmit Geolocation Policy to the IESG for publication as > > > PS > > > > Sep 2009 Submit an draft for DHCP geodetic location to the IESG for > > > > publication as PS to obsolete 3825 > > > > Sep 2009 Submit an Architecture for Location and Location Privacy > > > > to the IESG for publication as Informational > > > > Dec 2009 Submit a URI scheme for directly expressing geodetic > > > location > > > > to the IESG for publication as PS > > > > Dec 2009 Submit a DHCP Option for a Location Uniform Resource > > > > Identifier (URI) to the IESG for publication as PS > > > > Dec 2009 Submit a Document Format for Filtering and Reporting PIDF- > > LO > > > > Location Notifications to the IESG for publication as PS > > > > _______________________________________________ > > > > Geopriv mailing list > > > > Geopriv@ietf.org > > > > https://www.ietf.org/mailman/listinfo/geopriv > > > > _______________________________________________ > > > > Geopriv mailing list > > > > Geopriv@ietf.org > > > > https://www.ietf.org/mailman/listinfo/geopriv > > > > > > _______________________________________________ > > > Geopriv mailing list > > > Geopriv@ietf.org > > > https://www.ietf.org/mailman/listinfo/geopriv > > > > ----------------------------------------------------------------------- > > ------------------------- > > This message is for the designated recipient only and may > > contain privileged, proprietary, or otherwise private information. > > If you have received it in error, please notify the sender > > immediately and delete the original. Any unauthorized use of > > this email is prohibited. > > ----------------------------------------------------------------------- > > ------------------------- > > [mf2] > > _______________________________________________ > > Geopriv mailing list > > Geopriv@ietf.org > > https://www.ietf.org/mailman/listinfo/geopriv > >_______________________________________________ >Geopriv mailing list >Geopriv@ietf.org >https://www.ietf.org/mailman/listinfo/geopriv >------------------------------------------------------------------------------------------------ >This message is for the designated recipient only and may >contain privileged, proprietary, or otherwise private information. >If you have received it in error, please notify the sender >immediately and delete the original. Any unauthorized use of >this email is prohibited. >------------------------------------------------------------------------------------------------ >[mf2] > >_______________________________________________ >Geopriv mailing list >Geopriv@ietf.org >https://www.ietf.org/mailman/listinfo/geopriv
- Re: [Geopriv] WG Review: Recharter of Geographic … Cullen Jennings
- [Geopriv] WG Review: Recharter of Geographic Loca… IESG Secretary
- Re: [Geopriv] WG Review: Recharter of GeographicL… Thomson, Martin
- Re: [Geopriv] WG Review: Recharter of GeographicL… Brian Rosen
- Re: [Geopriv] WG Review: Recharter of Geographic … g.caron
- Re: [Geopriv] WG Review: Recharter of Geographic … Ray.Bellis
- Re: [Geopriv] WG Review: Recharter ofGeographic L… Tschofenig, Hannes (NSN - FI/Espoo)
- Re: [Geopriv] WG Review: RecharterofGeographic Lo… Winterbottom, James
- Re: [Geopriv] WG Review: Recharter of Geographic … Bernard Aboba
- Re: [Geopriv] WG Review: Recharterof GeographicLo… Dawson, Martin
- Re: [Geopriv] WG Review: Recharterof GeographicLo… James M. Polk
- Re: [Geopriv] WG Review: Recharterof GeographicLo… Dawson, Martin
- Re: [Geopriv] WG Review: Recharterof GeographicLo… Ray.Bellis
- Re: [Geopriv] WG Review: Recharterof GeographicLo… Brian Rosen
- Re: [Geopriv] WG Review:Recharterof GeographicLoc… Cullen Jennings
- Re: [Geopriv] WGReview:Recharterof GeographicLoca… Winterbottom, James