Re: [Geopriv] Strawman charter

["Winterbottom, James" <[e-mail]>]

That is 2 for 2 now, I think I am going to go back to bed.
Thanks Robert, the text you have quite adequately addresses my request.

Cheers
James


> -----Original Message-----
> From: Robert Sparks [mailto:[e-mail]]
> Sent: Thursday, 17 July 2008 8:06 AM
> To: Winterbottom, James
> Cc: GEOPRIV
> Subject: Re: [Geopriv] Strawman charter
> 
> Note that that sentence actually happened twice in what I sent.
> The one in isolation should be deleted - the copy that was intended
> to be there is the one at the beginning of the next paragraph. If you
> could, propose text in that context.
> 
> RjS
> 
> On Jul 16, 2008, at 4:49 PM, Winterbottom, James wrote:
> 
> >
> > Hi Robert,
> >
> > I would like to see some additional words put around :
> >
> > "This working group will not develop location-determining
technology."
> >
> > I believe that we need to provide a framework that will support the
> > exchange of messages between an end-point and a LIS to better enable
> > location-determination.
> >
> > I also think that we need to provide a document that allows an end-
> > point to provide identifiers beyond just IP address.
> > And yes, I am going to open the OBO can of worms again because these
> > are going to be the early deployments and we need to support them
> > with as reasonable way to to do this as is possible.
> >
> > Cheers
> > James
> >
> >
> >
> > -----Original Message-----
> > From: [e-mail] on behalf of Robert Sparks
> > Sent: Wed 7/16/2008 1:52 PM
> > To: GEOPRIV
> > Subject: [Geopriv] Strawman charter
> >
> > Folks -
> >
> > GEOPRIV has covered a lot of ground since its inception. We're
getting
> > stuff done and (as sluggish as it sometimes feels) beginning to
> > build up
> > some speed.
> >
> > It would be a good time to reflect on the charter and make sure its
> > in proper shape to guide our work going forward.
> >
> > Below is a strawman proposal to stimulate conversation.
> > Please send comments to the list
> >
> > RjS
> >
> > ----------
> >
> > The IETF has recognized that applications requiring geopraphic
> > and civil location information about resources and entities
> > are emerging, 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 a to allow users to express policies
> > on how these representations are exposed and used.
> > The IETF has also begun working on creating applicaitons
> > that use these capabilities, in general real-time
> > communication, emergency services, and other areas.
> >
> > The GEOPRIV working group is chartered to continue
> > to analyse 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 using these mechanisms to ensure
> > that the requirements are well understood and met, and
> > that no additional security or privacy issues related
> > to location are left unaddred as these mechanisms are
> > 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.
> >
> > This working group will not develop location-determining
> > technology. However, the IETF acknowledges that information
> > used in the location-determination process may need to be
> > carried over the Internet. Where necessary, this working group
> > will develop a extensions to IETF protocols to encode
> > location-determination data structures defined elsewhere.
> > This working group will not develop technologies to directly
> > address any particular regulatory requirements (e.g. E.911).
> > The group will coordinate with any other IETF entities that
> > are working on those problems to ensure the technologies created
> > here meets that entities needs and that the authorization,
> > integrity, and privacy requirements on the mechanisms provided
> > by these techbologies continue to be met.
> >
> > This working group is tasked with several immediate high-level
> > goals, as reflected in the milestones. These include
> >
> > * Completion of layer-7 location conveyance protocol
> > * Providing a Location Information Server discovery protocol
> > * Providing an analysis of proposed migration technologies
> >   used to bring location-aware applications into the existing
> >   Internet environment. Specifically, this analysis will
> >   explore the restrictions or additional mechanisms that
> >   would need to exist to ensure the above authorization,
> >   integrity, and privacy requirements are met if a third
> >   party were allowed to obtain location on behalf of an end-user.
> >
> > 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
> >      publicaiton 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 Ruels 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
> >
> > Aug 2008 Submit Recommendations for Retransmission in SIP Location
> > Conveyance
> >          to the IESG for publication as Informational
> >
> > Aug 2008 Submit Layer 7 Location Conveyance Protocol Problem
Statement
> > and
> >          Requirements to the IESG for publication as Informational
> >
> > Sep 2008 Resubmit Geolocation Policy to the IESG for publication as
PS
> >
> > Sep 2008 Submit a LIS Discovery Mechanism to the IESG for
publication
> > as a PS
> >
> > Nov 2008 Submit recommendations for representing civic addresses in
> > PIDF-LO
> >          to the IESG for publication as BCP
> >
> > Nov 2008 Submit Requirements for Location by Reference Protocols to
> > the IESG
> >          for publication as Informational
> >
> > Dec 2008 Submit an update to RFC3825 separating hiding and bounding
> > goals to
> >          the IESG for publication as PS
> >
> > Jan 2009 Submit a Document Format for Filtering and Reporting
PIDF-LO
> > Location
> >          Notifications to the IESG for publication as PS
> >
> > Feb 2009 Submit an update to the GEOPRIV Requirements and Threat
> > Analysis
> >          documents to the IESG for publication as Informational
> >
> > _______________________________________________
> > Geopriv mailing list
> > [e-mail]
> > 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]
> >
> 

------------------------------------------------------------------------------------------------
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
[e-mail]
https://www.ietf.org/mailman/listinfo/geopriv