Skip to main content

Geopriv Requirements
draft-ietf-geopriv-reqs-04

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    geopriv mailing list <geopriv@ietf.org>, 
    geopriv chair <geopriv-chairs@tools.ietf.org>
Subject: Document Action: 'Geopriv requirements' to 
         Informational RFC 

The IESG has approved the following document:

- 'Geopriv requirements '
   <draft-ietf-geopriv-reqs-05.txt> as an Informational RFC

This document is the product of the Geographic Location/Privacy Working 
Group. 

The IESG contact persons are Ted Hardie and Jon Peterson.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-geopriv-reqs-05.txt

Ballot Text

Technical Summary

This document focuses on the authorization, security and privacy
requirements for location-dependent services.  Specifically, it
describes the requirements for the Geopriv Location Object (LO) and
for the protocols that use this Location Object.  This LO is envisioned 
to be the primary data structure used in all Geopriv protocol exchanges 
to securely transfer location data.

Working Group Summary

There was consensus in the working group for publishing this document
as an Information RFC.
 
Protocol Quality
 
This document was reviewed for the IESG by Ted Hardie


RFC-Editor,

Please make the following changes to this draft.

Thanks,

Ted Hardie


Abstract:
OLD
   This LO is envisioned to be the main object defined by the Geopriv WG, 
   used in all Geopriv exchanges and in particular used to securely transfer
   location data.

NEW
   This LO is envisioned to be the primary data structure
   used in all Geopriv protocol exchanges to securely
   transfer location data.

NEW

7.2, Req. 5

OLD

   Req. 5.  The using protocol will typically facilitate that the keys
   associated with the credentials are transported to the respective
   parties, that is, key agreement is responsibility of the using
   protocol.


NEW

   Req. 5.  The using protocol will typically facilitate that the keys
   associated with the credentials are transported to the respective
   parties, that is, key establishment is the responsibility of the using
   protocol.

RFC Editor Note