Wednesday, June 6, 2012

[Geopriv] draft-ietf-geopriv-policy-26.txt - Beyond here and now

Is there an IETF plan to future-proof geopriv policy's scope?

 

Please consider the following examples - these reside outside a needed geopriv scope:

 

Circa 2001, NNTP content is stripped of 'closed-context' newsgroup specific discussion premise.  Content is converted to HTML and becomes overly and overtly indexed.  Legacy NNTP access and search constructs become irrelevant.  Now a ~1994 NNTP discussion within talk.abortion has search engine indexing not only specific NNTP newsgroup context, but my identity / location (by virtue of NNTP auth (name.surname@domain.com) & date/time stamped IP address.  How does the policy address this type of actuality for legacy, current, and future application protocols / content / content transformations?

 

In 2003, I modestly contributed to an IETF anti-spam WG.  While I embrace IETF views on IPR within BPC 78 & 79, there is literally NO option or means by which to make previous IETF contributions closer to "web anonymous".  Someone looks up my name, and search engine effectively headlines my Firstname.Lastname@domain.com profile as highly spam related, including 7 indexed results, all in some way related to a single 2003 IETF anti-spam WG contribution.

 

Many regret how their name/image escapes specific application config/preferences contextual protocol, to become widely visible on the Internet.  Gaining ready access to publishers & re-publishers, willing to retract / delete / modify sensitive personal information or views is less than a standardized protocol – most often by design.  While I can place my name behind most everything I state, I elect to opt out until consideration for privacy re-gains critically lost constitution.


Currer.Anon.Bell@gm

Tuesday, June 5, 2012

Re: [Geopriv] I-D Action: draft-ietf-geopriv-policy-26.txt

Dealing with IESG reviews. See related email.

I have the pen. If you would like the pen, or are concerned for the
safety of your precious text*, then you may request the pen.

--Martin

[*] Trust me, some of this text is in serious jeopardy.

On 5 June 2012 14:46, <internet-drafts@ietf.org> wrote:
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Geographic Location/Privacy Working Group of the IETF.
>
>        Title           : Geolocation Policy: A Document Format for Expressing Privacy Preferences for Location Information
>        Author(s)       : Henning Schulzrinne
>                          Hannes Tschofenig
>                          Jorge R. Cuellar
>                          James Polk
>                          John B. Morris
>                          Martin Thomson
>        Filename        : draft-ietf-geopriv-policy-26.txt
>        Pages           : 49
>        Date            : 2012-06-05
>
>   This document defines an authorization policy language for
>   controlling access to location information.  It extends the Common
>   Policy authorization framework to provide location-specific access
>   control.  More specifically, this document defines condition elements
>   specific to location information in order to restrict access based on
>   the current location of the Target.
>
>   Furthermore, this document defines two algorithms for reducing the
>   granularity of returned location information.  The first algorithm is
>   defined for usage with civic location information while the other one
>   applies to geodetic location information.  Both algorithms come with
>   limitations.  There are circumstances where the amount of location
>   obfuscation provided is less than what is desired.  These algorithms
>   might not be appropriate for all application domains.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-geopriv-policy-26.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-geopriv-policy-26.txt
>
> The IETF datatracker page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-geopriv-policy/
>
> _______________________________________________
> 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] I-D Action: draft-ietf-geopriv-policy-26.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Geographic Location/Privacy Working Group of the IETF.

Title : Geolocation Policy: A Document Format for Expressing Privacy Preferences for Location Information
Author(s) : Henning Schulzrinne
Hannes Tschofenig
Jorge R. Cuellar
James Polk
John B. Morris
Martin Thomson
Filename : draft-ietf-geopriv-policy-26.txt
Pages : 49
Date : 2012-06-05

This document defines an authorization policy language for
controlling access to location information. It extends the Common
Policy authorization framework to provide location-specific access
control. More specifically, this document defines condition elements
specific to location information in order to restrict access based on
the current location of the Target.

Furthermore, this document defines two algorithms for reducing the
granularity of returned location information. The first algorithm is
defined for usage with civic location information while the other one
applies to geodetic location information. Both algorithms come with
limitations. There are circumstances where the amount of location
obfuscation provided is less than what is desired. These algorithms
might not be appropriate for all application domains.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-geopriv-policy-26.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-geopriv-policy-26.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-geopriv-policy/

_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

[Geopriv] Discuss on geopriv-policy - assistance required

For some reason, I've been stiffed with dealing with AD discusses on
geopriv-policy. I consented before I read through Barry Leiba's
DISCUSS.

geopriv policy requires "standards action" for registrations of new
location profiles. Barry has requested justification.

Why?

It seems a bit much to me. common-policy already has mechanisms for
dealing with rules that contain not-supported elements. And code
points are in short supply. I'm inclined to suggest "specification
required" instead. At least I'd have no trouble justifying the
requirement for a reasonable specification.
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

Thursday, May 31, 2012

[Geopriv] Last Call: (Dynamic Host Configuration Protocol (DHCP) IPv4 and IPv6 Option for a Location Uniform Resource Identifier (URI)) to Proposed Standard

The IESG has received a request from the Geographic Location/Privacy WG
(geopriv) to consider the following document:
- 'Dynamic Host Configuration Protocol (DHCP) IPv4 and IPv6 Option for a
Location Uniform Resource Identifier (URI)'
<draft-ietf-geopriv-dhcp-lbyr-uri-option-15.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2012-06-14. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


This document creates a Dynamic Host Configuration Protocol (DHCP)
Option for transmitting a client's geolocation Uniform Resource
Identifier (URI). This Location URI can then be dereferenced in a
separate transaction by the client or sent to another entity and
dereferenced to learn physically where the client is located.





The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-geopriv-dhcp-lbyr-uri-option/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-geopriv-dhcp-lbyr-uri-option/ballot/


No IPR declarations have been submitted directly on this I-D.


_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

[Geopriv] I-D Action: draft-ietf-geopriv-dhcp-lbyr-uri-option-15.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Geographic Location/Privacy Working Group of the IETF.

Title : Dynamic Host Configuration Protocol (DHCP) IPv4 and IPv6 Option for a Location Uniform Resource Identifier (URI)
Author(s) : James Polk
Filename : draft-ietf-geopriv-dhcp-lbyr-uri-option-15.txt
Pages : 13
Date : 2012-05-31

This document creates a Dynamic Host Configuration Protocol (DHCP)
Option for transmitting a client's geolocation Uniform Resource
Identifier (URI). This Location URI can then be dereferenced in a
separate transaction by the client or sent to another entity and
dereferenced to learn physically where the client is located.



A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-geopriv-dhcp-lbyr-uri-option-15.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-geopriv-dhcp-lbyr-uri-option-15.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-geopriv-dhcp-lbyr-uri-option/

_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

Monday, May 14, 2012

Re: [Geopriv] Fwd: New Version Notification for draft-bellis-geopriv-flow-identity-01.txt

The idea of a source and destination is quite subjective when it comes
to NAT traversal. From the perspective of the NAT it is usually the
endpoint behind that initiates the flow (because that's how holes
appear), but where there are two NATs on a flow, the same view is held
by both NATs.

e.g.
A -- NATa -- (Internets!) -- NATb -- B

NATa views A as being the source. NATb views B as being the source.

This fits well with what you have since you assume src to be the
default and you are normally talking to something that will share the
perspective bias of the NAT. An explanation of this trap might be
useful.

Extension is easy:
<xs:sequence>
<xs:element name="src" type="flow:flowEndpoint"/>
<xs:element name="dst" type="flow:flowEndpoint"/>
>> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>

Nit:
Section 3: s/show/shown/

On 14 May 2012 08:03, Ray Bellis <Ray.Bellis@nominet.org.uk> wrote:
> Following the discussion in Paris and subsequent chats with Martin I've now updated this draft.
>
> The changes are:
>
> - simplified (shorter) XSD
>
> - allowing an IP protocol number to be specified instead
>  of "tcp", "udp" etc.
>
>  [I considered doing the same for IP version, but I really
>   don't see us trying to do IPv10 just yet...]
>
> - adding of an (optional) "target" attribute to the <flow>
>  tag to identify which end of the flow is the target of the
>  <locationRequest>.
>
> Please review - the draft is short, and I'd love to see it zip straight through the WG and up to the IESG asap.
>
> Ray
>
>> A new version of I-D, draft-bellis-geopriv-flow-identity-01.txt has been successfully submitted by Ray Bellis and posted to the IETF repository.
>>
>> Filename:      draft-bellis-geopriv-flow-identity
>> Revision:      01
>> Title:                 Flow Identity Extension for HELD
>> Creation date:         2012-05-14
>> WG ID:                 Individual Submission
>> Number of pages: 12
>
> _______________________________________________
> 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] Fwd: New Version Notification for draft-bellis-geopriv-flow-identity-01.txt

Following the discussion in Paris and subsequent chats with Martin I've now updated this draft.

The changes are:

- simplified (shorter) XSD

- allowing an IP protocol number to be specified instead
of "tcp", "udp" etc.

[I considered doing the same for IP version, but I really
don't see us trying to do IPv10 just yet...]

- adding of an (optional) "target" attribute to the <flow>
tag to identify which end of the flow is the target of the
<locationRequest>.

Please review - the draft is short, and I'd love to see it zip straight through the WG and up to the IESG asap.

Ray

> A new version of I-D, draft-bellis-geopriv-flow-identity-01.txt has been successfully submitted by Ray Bellis and posted to the IETF repository.
>
> Filename: draft-bellis-geopriv-flow-identity
> Revision: 01
> Title: Flow Identity Extension for HELD
> Creation date: 2012-05-14
> WG ID: Individual Submission
> Number of pages: 12

_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

Monday, May 7, 2012

Re: [Geopriv] I-D Action: draft-ietf-geopriv-deref-protocol-05.txt

This update covers feedback from IESG review.

On 7 May 2012 15:43, <internet-drafts@ietf.org> wrote:
>        Title           : A Location Dereferencing Protocol Using HELD
>        Filename        : draft-ietf-geopriv-deref-protocol-05.txt
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

[Geopriv] I-D Action: draft-ietf-geopriv-deref-protocol-05.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Geographic Location/Privacy Working Group of the IETF.

Title : A Location Dereferencing Protocol Using HELD
Author(s) : James Winterbottom
Hannes Tschofenig
Henning Schulzrinne
Martin Thomson
Filename : draft-ietf-geopriv-deref-protocol-05.txt
Pages : 23
Date : 2012-05-07

This document describes how to use the Hypertext Transfer Protocol
(HTTP) over Transport Layer Security (TLS) as a dereferencing
protocol to resolve a reference to a Presence Information Data Format
Location Object (PIDF-LO). The document assumes that a Location
Recipient possesses a URI that can be used in conjunction with the
HTTP-Enabled Location Delivery (HELD) protocol to request the
location of the Target.


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

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-geopriv-deref-protocol-05.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-geopriv-deref-protocol/

_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

Friday, April 27, 2012

Re: [Geopriv] [Technical Errata Reported] RFC6225 (3202)

This seems appropriate.

James

At 10:59 AM 4/26/2012, Martin Thomson wrote:
>Valid. Recommend hold for document update.
>
>On 26 April 2012 01:18, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
> >
> > The following errata report has been submitted for RFC6225,
> > "Dynamic Host Configuration Protocol Options
> for Coordinate-Based Location Configuration Information".
> >
> > --------------------------------------
> > You may review the report below and at:
> > http://www.rfc-editor.org/errata_search.php?rfc=6225&eid=3202
> >
> > --------------------------------------
> > Type: Technical
> > Reported by: Alfred Hoenes <ah@TR-Sys.de>
> >
> > Section: 4.3, pg. 19
> >
> > Original Text
> > -------------
> > Â Description: The description of the altitude described by this code.
> >
> > Corrected Text
> > --------------
> > Â Description: The description of the datum (coordinate system)
> > Â Â Â described by this code.
> >
> > Notes
> > -----
> > Rationale: copyedit artifact; text obviously copied from
> > Â Section 4.2. (Altitude Type Registry) without performing
> > Â the needed adaptation for Section 4.3. (Datum Registry).
> >
> > Instructions:
> > -------------
> > This errata is currently posted as "Reported". If necessary, please
> > use "Reply All" to discuss whether it should be verified or
> > rejected. When a decision is reached, the verifying party (IESG)
> > can log in to change the status and edit the report, if necessary.
> >
> > --------------------------------------
> > RFC6225 (draft-ietf-geopriv-rfc3825bis-17)
> > --------------------------------------
> > Title        : Dynamic Host
> Configuration Protocol Options for
> Coordinate-Based Location Configuration Information
> > Publication Date   : July 2011
> > Author(s) Â Â Â Â Â : J. Polk, M. Linsner, M. Thomson, B. Aboba, Ed.
> > Category       : PROPOSED STANDARD
> > Source        : Geographic Location/Privacy
> > Area         : Real-time Applications and Infrastructure
> > Stream        : IETF
> > Verifying Party   : IESG
> > _______________________________________________
> > 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

Re: [Geopriv] WGLC on draft-ietf-geopriv-relative-location-02

We got 1 response to this, and it was from an author. We need to hear from more of the WG before proceeding.

On Mar 29, 2012, at 12:12 PM, Richard L. Barnes wrote:

> Dear GEOPRIV,
>
> This is a Working Group Last Call for comments on draft-ietf-geopriv-relative-location-02:
> <http://tools.ietf.org/html/draft-ietf-geopriv-relative-location-02>
>
> Please send comments to the list no later than Friday, 20 April 2012.
>
> Remember that all comments are helpful, even if it's just "Looks good to me". You can also say "Doesn't look good to me", but it's more helpful to say why!
>
> Thanks,
> Alissa and Richard
> The GEOPRIV Chairs
> _______________________________________________
> 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

Thursday, April 26, 2012

Re: [Geopriv] [Technical Errata Reported] RFC6225 (3202)

Valid. Recommend hold for document update.

On 26 April 2012 01:18, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
>
> The following errata report has been submitted for RFC6225,
> "Dynamic Host Configuration Protocol Options for Coordinate-Based Location Configuration Information".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=6225&eid=3202
>
> --------------------------------------
> Type: Technical
> Reported by: Alfred Hoenes <ah@TR-Sys.de>
>
> Section: 4.3, pg. 19
>
> Original Text
> -------------
>   Description: The description of the altitude described by this code.
>
> Corrected Text
> --------------
>   Description: The description of the datum (coordinate system)
>      described by this code.
>
> Notes
> -----
> Rationale: copyedit artifact; text obviously copied from
>  Section 4.2. (Altitude Type Registry) without performing
>  the needed adaptation for Section 4.3. (Datum Registry).
>
> Instructions:
> -------------
> This errata is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> RFC6225 (draft-ietf-geopriv-rfc3825bis-17)
> --------------------------------------
> Title               : Dynamic Host Configuration Protocol Options for Coordinate-Based Location Configuration Information
> Publication Date    : July 2011
> Author(s)           : J. Polk, M. Linsner, M. Thomson, B. Aboba, Ed.
> Category            : PROPOSED STANDARD
> Source              : Geographic Location/Privacy
> Area                : Real-time Applications and Infrastructure
> Stream              : IETF
> Verifying Party     : IESG
> _______________________________________________
> 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] [Technical Errata Reported] RFC6225 (3202)

The following errata report has been submitted for RFC6225,
"Dynamic Host Configuration Protocol Options for Coordinate-Based Location Configuration Information".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6225&eid=3202

--------------------------------------
Type: Technical
Reported by: Alfred Hoenes <ah@TR-Sys.de>

Section: 4.3, pg. 19

Original Text
-------------
Description: The description of the altitude described by this code.

Corrected Text
--------------
Description: The description of the datum (coordinate system)
described by this code.

Notes
-----
Rationale: copyedit artifact; text obviously copied from
Section 4.2. (Altitude Type Registry) without performing
the needed adaptation for Section 4.3. (Datum Registry).

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary.

--------------------------------------
RFC6225 (draft-ietf-geopriv-rfc3825bis-17)
--------------------------------------
Title : Dynamic Host Configuration Protocol Options for Coordinate-Based Location Configuration Information
Publication Date : July 2011
Author(s) : J. Polk, M. Linsner, M. Thomson, B. Aboba, Ed.
Category : PROPOSED STANDARD
Source : Geographic Location/Privacy
Area : Real-time Applications and Infrastructure
Stream : IETF
Verifying Party : IESG
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

Friday, April 20, 2012

Re: [Geopriv] WGLC on draft-ietf-geopriv-held-measurements-04

One nit: section 4 and section 5 have the same title, which could be a bit confusing. Since section 4 is more about the data model elements than actual data types, I would suggest changing the section 4 title.

Alissa

On Mar 29, 2012, at 12:12 PM, Richard L. Barnes wrote:

> Dear GEOPRIV,
>
> This is a Working Group Last Call for comments on draft-ietf-geopriv-held-measurements-04:
> <http://tools.ietf.org/html/draft-ietf-geopriv-held-measurements-04>
>
> Please send comments to the list no later than Friday, 20 April 2012.
>
> Remember that all comments are helpful, even if it's just "Looks good to me". You can also say "Doesn't look good to me", but it's more helpful to say why!
>
> Thanks,
> Alissa and Richard
> The GEOPRIV Chairs
> _______________________________________________
> 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

Monday, April 2, 2012

Re: [Geopriv] IETF 83 minutes

I'm sorry, my mistake in notetaking. Not that I've made any other
mistakes, ever.

--Martin

On 2 April 2012 23:48, Richard L. Barnes <rbarnes@bbn.com> wrote:
>>>
>>> >> GEOPRIV is OAR SOME!
>>> >>
>>> >> __boring status stuff
>>> >>
>>> >> AD asked about DHC LbyR - there is an apps review that is very new
>>> >>
>>> >> Ray Bellis asked about draft expiry and WGLC, was asked to revise the draft
>>> >
>>> > Alissa
>>> >
>>> > Ray was asked to revise the DHC LbyR draft?
>>> >
>>> > James
>>>
>>> He was asked to issue a new revision, with no content changes, so that the draft would be live again.
>>
>> Did you chairs fire me as editor and not tell me?
>>
>> James
>
> Ah, sorry, now I understand the confusion.  In that sentence, "draft expiry" refers to draft-ietf-geopriv-res-gw-lis-discovery, not draft-ietf-geopriv-dhcp-lbyr-uri-option.  So, no change in authorship.
>
> --Richard
> _______________________________________________
> 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

Re: [Geopriv] IETF 83 minutes

>>
>> >> GEOPRIV is OAR SOME!
>> >>
>> >> __boring status stuff
>> >>
>> >> AD asked about DHC LbyR - there is an apps review that is very new
>> >>
>> >> Ray Bellis asked about draft expiry and WGLC, was asked to revise the draft
>> >
>> > Alissa
>> >
>> > Ray was asked to revise the DHC LbyR draft?
>> >
>> > James
>>
>> He was asked to issue a new revision, with no content changes, so that the draft would be live again.
>
> Did you chairs fire me as editor and not tell me?
>
> James

Ah, sorry, now I understand the confusion. In that sentence, "draft expiry" refers to draft-ietf-geopriv-res-gw-lis-discovery, not draft-ietf-geopriv-dhcp-lbyr-uri-option. So, no change in authorship.

--Richard
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

Re: [Geopriv] IETF 83 minutes

At 12:09 PM 4/2/2012, Richard L. Barnes wrote:
> >> Minutes - GEOPRIV - IETF 83
> >>
> >> Summary:
> >>
> >> 1. Chairs' Introduction
> >> The chairs noted the publication of RFC 6447 since the last
> IETF. The AD noted that a new apps area review has come in for
> draft-ietf-geopriv-dhcp-lbyr-uri-option. The WG's three remaining
> active drafts entered WGLC during the meeting session. The authors
> of draft-ietf-res-gw-lis-discovery agreed to rev their draft since
> it had expired and needs more comments before it can be pub requested.
> >>
> >> 2. draft-bellis-geopriv-flow-identity-00
> >> This draft received a few suggested improvements, but was
> uncontroversial overall. Ray will rev based on feedback, followed
> by a likely combined call for adoption/WGLC.
> >>
> >> 3. Where do we go from here?
> >> The WG will remain open at least until all current drafts are
> through the IESG, although may not meet face-to-face.
> >>
> >> 4. draft-thomson-geopriv-uncertainty-07
> >> Martin agreed to rev this expired draft and Roger agreed to do a review.
> >>
> >>
> >> Raw notes from the tools.ietf.org etherpad follow
> >> ----------
> >>
> >> GEOPRIV is OAR SOME!
> >>
> >> __boring status stuff
> >>
> >> AD asked about DHC LbyR - there is an apps review that is very new
> >>
> >> Ray Bellis asked about draft expiry and WGLC, was asked to
> revise the draft
> >
> > Alissa
> >
> > Ray was asked to revise the DHC LbyR draft?
> >
> > James
>
>He was asked to issue a new revision, with no content changes, so
>that the draft would be live again.

Did you chairs fire me as editor and not tell me?

James


>--Richard

_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

Re: [Geopriv] IETF 83 minutes

>> Minutes - GEOPRIV - IETF 83
>>
>> Summary:
>>
>> 1. Chairs' Introduction
>> The chairs noted the publication of RFC 6447 since the last IETF. The AD noted that a new apps area review has come in for draft-ietf-geopriv-dhcp-lbyr-uri-option. The WG's three remaining active drafts entered WGLC during the meeting session. The authors of draft-ietf-res-gw-lis-discovery agreed to rev their draft since it had expired and needs more comments before it can be pub requested.
>>
>> 2. draft-bellis-geopriv-flow-identity-00
>> This draft received a few suggested improvements, but was uncontroversial overall. Ray will rev based on feedback, followed by a likely combined call for adoption/WGLC.
>>
>> 3. Where do we go from here?
>> The WG will remain open at least until all current drafts are through the IESG, although may not meet face-to-face.
>>
>> 4. draft-thomson-geopriv-uncertainty-07
>> Martin agreed to rev this expired draft and Roger agreed to do a review.
>>
>>
>> Raw notes from the tools.ietf.org etherpad follow
>> ----------
>>
>> GEOPRIV is OAR SOME!
>>
>> __boring status stuff
>>
>> AD asked about DHC LbyR - there is an apps review that is very new
>>
>> Ray Bellis asked about draft expiry and WGLC, was asked to revise the draft
>
> Alissa
>
> Ray was asked to revise the DHC LbyR draft?
>
> James

He was asked to issue a new revision, with no content changes, so that the draft would be live again.

--Richard
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

Re: [Geopriv] IETF 83 minutes

At 08:58 AM 4/2/2012, Alissa Cooper wrote:
>Minutes - GEOPRIV - IETF 83
>
>Summary:
>
>1. Chairs' Introduction
>The chairs noted the publication of RFC 6447 since the last IETF.
>The AD noted that a new apps area review has come in for
>draft-ietf-geopriv-dhcp-lbyr-uri-option. The WG's three remaining
>active drafts entered WGLC during the meeting session. The authors
>of draft-ietf-res-gw-lis-discovery agreed to rev their draft since
>it had expired and needs more comments before it can be pub requested.
>
>2. draft-bellis-geopriv-flow-identity-00
>This draft received a few suggested improvements, but was
>uncontroversial overall. Ray will rev based on feedback, followed by
>a likely combined call for adoption/WGLC.
>
>3. Where do we go from here?
>The WG will remain open at least until all current drafts are
>through the IESG, although may not meet face-to-face.
>
>4. draft-thomson-geopriv-uncertainty-07
>Martin agreed to rev this expired draft and Roger agreed to do a review.
>
>
>Raw notes from the tools.ietf.org etherpad follow
>----------
>
>GEOPRIV is OAR SOME!
>
>__boring status stuff
>
>AD asked about DHC LbyR - there is an apps review that is very new
>
>Ray Bellis asked about draft expiry and WGLC, was asked to revise the draft

Alissa

Ray was asked to revise the DHC LbyR draft?

James

>_______________________________________________
>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] IETF 83 minutes

Minutes - GEOPRIV - IETF 83

Summary:

1. Chairs' Introduction
The chairs noted the publication of RFC 6447 since the last IETF. The AD noted that a new apps area review has come in for draft-ietf-geopriv-dhcp-lbyr-uri-option. The WG's three remaining active drafts entered WGLC during the meeting session. The authors of draft-ietf-res-gw-lis-discovery agreed to rev their draft since it had expired and needs more comments before it can be pub requested.

2. draft-bellis-geopriv-flow-identity-00
This draft received a few suggested improvements, but was uncontroversial overall. Ray will rev based on feedback, followed by a likely combined call for adoption/WGLC.

3. Where do we go from here?
The WG will remain open at least until all current drafts are through the IESG, although may not meet face-to-face.

4. draft-thomson-geopriv-uncertainty-07
Martin agreed to rev this expired draft and Roger agreed to do a review.


Raw notes from the tools.ietf.org etherpad follow
----------

GEOPRIV is OAR SOME!

__boring status stuff

AD asked about DHC LbyR - there is an apps review that is very new

Ray Bellis asked about draft expiry and WGLC, was asked to revise the draft

__flow identity

martin thomson noted that the src/dst fields could be ambiguously interpreted, it's not clear which end applies to the target

marc linsner asks who actually creates the request, is it under the same rules as for RFC 6155
ray bellis yes, it's 6155

question of adoption deferred

__where do we go from here?

the bar?

question asked: who needs the working group?

marc: this is parallel to ecrit. there is potentially work for emergency services and location for dealing with emergency services in XMPP might need a working group host for that

roger marshall: wants to keep the WG alive, likes my super-fantastic uncertainty draft

robert sparks: the wg is going to be alive for at least as long as it takes to get rid of the current work, most likely, we will have our answer by then


martin thomson talks impromptu about his awesome-terrific uncertainty draft
roger talks about confidence, promises to review said great draft

martin thomson will rev his super-dooper draft soon

_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

Friday, March 30, 2012

Re: [Geopriv] WGLC: draft-ietf-geopriv-policy-25

Sorry to get this in so late.

In the discussion of dynamic/moving references, I think it may be good to emphasize that heading is true heading, rather than magnetic heading.

In 4.9.2.1, GML Sphere Template, there is a typo in the namespace declarations (gml is defined twice, gs is not).

In 4.9.5.1, GML Arc-Band Template, there is a copy/paste error: the closing tag is Ellipsoid rather than ArcBand.

In the example 5.1, there are comments lettering the points of a polygon, but the polygon is not illustrated in this document.

Marc B.

-----Original Message-----
From: geopriv-bounces@ietf.org [mailto:geopriv-bounces@ietf.org] On Behalf Of Hannes Tschofenig
Sent: Friday, February 24, 2012 9:14 AM
To: Alissa Cooper
Cc: GEOPRIV WG
Subject: Re: [Geopriv] WGLC: draft-ietf-geopriv-policy-25

I think it is ready to go. We have worked on this document far too long.

On Feb 24, 2012, at 4:48 PM, Alissa Cooper wrote:

> Just a reminder to send your WGLC comments on this, even if your only comment is that the document is ready to go.
>
> On Feb 13, 2012, at 6:18 PM, Alissa Cooper wrote:
>
>> This is a GEOPRIV Working Group Last Call for comments on
>> draft-ietf-geopriv-policy-25
>>
>> Please send your comments to the list by 27 February 2012. As always, please remember to send a note in if you've read the document and have no other comments other than "its ready to go" - we need those as much as we need "I found a problem."
>> _______________________________________________
>> 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
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

Re: [Geopriv] WGLC on draft-ietf-geopriv-relative-location-02

This is freaking mind-blowing.

On 29 March 2012 18:12, Richard L. Barnes <rbarnes@bbn.com> wrote:
> Dear GEOPRIV,
>
> This is a Working Group Last Call for comments on
> draft-ietf-geopriv-relative-location-02:
> <http://tools.ietf.org/html/draft-ietf-geopriv-relative-location-02>
>
> Please send comments to the list no later than Friday, 20 April 2012.
>
> Remember that all comments are helpful, even if it's just "Looks good to
> me".  You can also say "Doesn't look good to me", but it's more helpful to
> say why!
>
> Thanks,
> Alissa and Richard
> The GEOPRIV Chairs
> _______________________________________________
> 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

Thursday, March 29, 2012

Re: [Geopriv] WGLC on draft-ietf-geopriv-held-measurements-04

Looks good to me!

Carl


-----Original Message-----
From: Richard L. Barnes
Sent: Thursday, March 29, 2012 10:12 AM
To: geopriv@ietf.org
Subject: [Geopriv] WGLC on draft-ietf-geopriv-held-measurements-04

Dear GEOPRIV,

This is a Working Group Last Call for comments on
draft-ietf-geopriv-held-measurements-04:
<http://tools.ietf.org/html/draft-ietf-geopriv-held-measurements-04>

Please send comments to the list no later than Friday, 20 April 2012.

Remember that all comments are helpful, even if it's just "Looks good to
me". You can also say "Doesn't look good to me", but it's more helpful
to say why!

Thanks,
Alissa and Richard
The GEOPRIV Chairs
_______________________________________________
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

Re: [Geopriv] I-D Action: draft-ietf-geopriv-res-gw-lis-discovery-03.txt

On 29 Mar 2012, at 23:07, <internet-drafts@ietf.org>
wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Geographic Location/Privacy Working Group of the IETF.
>
> Title : Location Information Server (LIS) Discovery using IP address and Reverse DNS
> Author(s) : Martin Thomson
> Ray Bellis
> Filename : draft-ietf-geopriv-res-gw-lis-discovery-03.txt
> Pages : 19
> Date : 2012-03-29
>
>

This rev:

1. unexpires the document
2. has Martin's new address
3. fixes a couple of xref issues

Ray


_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

[Geopriv] I-D Action: draft-ietf-geopriv-res-gw-lis-discovery-03.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Geographic Location/Privacy Working Group of the IETF.

Title : Location Information Server (LIS) Discovery using IP address and Reverse DNS
Author(s) : Martin Thomson
Ray Bellis
Filename : draft-ietf-geopriv-res-gw-lis-discovery-03.txt
Pages : 19
Date : 2012-03-29

The residential gateway is a device that has become an integral part
of home networking equipment. Discovering a Location Information
Server (LIS) is a necessary part of acquiring location information
for location-based services. However, discovering a LIS when a
residential gateway is present poses a configuration challenge,
requiring a method that is able to work around the obstacle presented
by the gateway.

This document describes a solution to this problem. The solution
provides alternative domain names as input to the LIS discovery
process based on the network addresses assigned to a Device.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-geopriv-res-gw-lis-discovery-03.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-geopriv-res-gw-lis-discovery-03.txt

_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

Re: [Geopriv] WGLC on draft-ietf-geopriv-local-civic-03

This document is ready to go!


> -----Original Message-----
> From: geopriv-bounces@ietf.org [mailto:geopriv-bounces@ietf.org] On Behalf
> Of Richard L. Barnes
> Sent: Friday, 30 March 2012 3:13 AM
> To: geopriv@ietf.org
> Subject: [Geopriv] WGLC on draft-ietf-geopriv-local-civic-03
>
> Dear GEOPRIV,
>
> This is a Working Group Last Call for comments on
> draft-ietf-geopriv-local-civic-03:
> <http://tools.ietf.org/html/draft-ietf-geopriv-local-civic-03>
>
> Please send comments to the list no later than Friday, 20 April 2012.
>
> Remember that all comments are helpful, even if it's just "Looks good to
> me". You can also say "Doesn't look good to me", but it's more helpful
> to say why!
>
> Thanks,
> Alissa and Richard
> The GEOPRIV Chairs
> _______________________________________________
> 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

Re: [Geopriv] WGLC on draft-ietf-geopriv-held-measurements-04

This document is ready to go!


> -----Original Message-----
> From: geopriv-bounces@ietf.org [mailto:geopriv-bounces@ietf.org] On Behalf
> Of Richard L. Barnes
> Sent: Friday, 30 March 2012 3:13 AM
> To: geopriv@ietf.org
> Subject: [Geopriv] WGLC on draft-ietf-geopriv-held-measurements-04
>
> Dear GEOPRIV,
>
> This is a Working Group Last Call for comments on
> draft-ietf-geopriv-held-measurements-04:
> <http://tools.ietf.org/html/draft-ietf-geopriv-held-measurements-04>
>
> Please send comments to the list no later than Friday, 20 April 2012.
>
> Remember that all comments are helpful, even if it's just "Looks good to
> me". You can also say "Doesn't look good to me", but it's more helpful
> to say why!
>
> Thanks,
> Alissa and Richard
> The GEOPRIV Chairs
> _______________________________________________
> 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

Re: [Geopriv] WGLC on draft-ietf-geopriv-local-civic-03

An underappreciated gem.

On 29 March 2012 18:12, Richard L. Barnes <rbarnes@bbn.com> wrote:
> Dear GEOPRIV,
>
> This is a Working Group Last Call for comments on
> draft-ietf-geopriv-local-civic-03:
> <http://tools.ietf.org/html/draft-ietf-geopriv-local-civic-03>
>
> Please send comments to the list no later than Friday, 20 April 2012.
>
> Remember that all comments are helpful, even if it's just "Looks good to
> me".  You can also say "Doesn't look good to me", but it's more helpful to
> say why!
>
> Thanks,
> Alissa and Richard
> The GEOPRIV Chairs
> _______________________________________________
> 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

Re: [Geopriv] WGLC on draft-ietf-geopriv-held-measurements-04

It's a masterpiece.

On 29 March 2012 18:12, Richard L. Barnes <rbarnes@bbn.com> wrote:
> Dear GEOPRIV,
>
> This is a Working Group Last Call for comments on
> draft-ietf-geopriv-held-measurements-04:
> <http://tools.ietf.org/html/draft-ietf-geopriv-held-measurements-04>
>
> Please send comments to the list no later than Friday, 20 April 2012.
>
> Remember that all comments are helpful, even if it's just "Looks good to
> me".  You can also say "Doesn't look good to me", but it's more helpful to
> say why!
>
> Thanks,
> Alissa and Richard
> The GEOPRIV Chairs
> _______________________________________________
> 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] Fwd: New Version Notification for draft-thomson-geopriv-uncertainty-07.txt

As promised.
..
A new version of I-D, draft-thomson-geopriv-uncertainty-07.txt has
been successfully submitted by Martin Thomson and posted to the IETF
repository.

Filename:        draft-thomson-geopriv-uncertainty
Revision:        07
Title:           Representation of Uncertainty and Confidence in PIDF-LO
Creation date:   2012-03-29
WG ID:           Individual Submission
Number of pages: 28

Abstract:
  The key concepts of uncertainty and confidence as they pertain to
  location information are defined.  Methods for the manipulation of
  location estimates that include uncertainty information are outlined.
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

Re: [Geopriv] WGLC: draft-ietf-geopriv-res-gw-lis-discovery-02

This is a call for further comments on
draft-ietf-geopriv-res-gw-lis-discovery-02. (Thus on -03, to be issued
real soon now.) The only comments received during last call were from
the document authors. The chairs do not feel that these constitute a
sufficient basis for submitting this document to the IESG.

If you feel this document is important, please send comments to the list
no later than Friday, 20 April 2012.

Remember that all comments are helpful, even if it's just "Looks good to
me". You can also say "Doesn't look good to me", but it's more helpful
to say why!

Thanks,
Alissa and Richard
The GEOPRIV Chairs

On 2/14/12 4:20 PM, Alissa Cooper wrote:
> This is a GEOPRIV Working Group Last Call for comments on
> draft-ietf-geopriv-res-gw-lis-discovery-02
>
> Please send your comments to the GEOPRIV list by 27 February 2012. As always, please remember to send a note in if you've read the document and have no other comments other than "its ready to go" - we need those as much as we need "I found a problem."
> _______________________________________________
> 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] WGLC on draft-ietf-geopriv-relative-location-02

Dear GEOPRIV,

This is a Working Group Last Call for comments on
draft-ietf-geopriv-relative-location-02:
<http://tools.ietf.org/html/draft-ietf-geopriv-relative-location-02>

Please send comments to the list no later than Friday, 20 April 2012.

Remember that all comments are helpful, even if it's just "Looks good to
me". You can also say "Doesn't look good to me", but it's more helpful
to say why!

Thanks,
Alissa and Richard
The GEOPRIV Chairs
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

[Geopriv] WGLC on draft-ietf-geopriv-local-civic-03

Dear GEOPRIV,

This is a Working Group Last Call for comments on
draft-ietf-geopriv-local-civic-03:
<http://tools.ietf.org/html/draft-ietf-geopriv-local-civic-03>

Please send comments to the list no later than Friday, 20 April 2012.

Remember that all comments are helpful, even if it's just "Looks good to
me". You can also say "Doesn't look good to me", but it's more helpful
to say why!

Thanks,
Alissa and Richard
The GEOPRIV Chairs
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

[Geopriv] WGLC on draft-ietf-geopriv-held-measurements-04

Dear GEOPRIV,

This is a Working Group Last Call for comments on
draft-ietf-geopriv-held-measurements-04:
<http://tools.ietf.org/html/draft-ietf-geopriv-held-measurements-04>

Please send comments to the list no later than Friday, 20 April 2012.

Remember that all comments are helpful, even if it's just "Looks good to
me". You can also say "Doesn't look good to me", but it's more helpful
to say why!

Thanks,
Alissa and Richard
The GEOPRIV Chairs
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

Monday, March 26, 2012

Re: [Geopriv] Agenda swap

We are keeping our originally scheduled slot, Thursday at 17:40.

On Mar 16, 2012, at 7:45 PM, Alissa Cooper wrote:

> Due to scheduling conflicts and the short length of our agenda, Richard and I intend to request to move GEOPRIV into the Friday 11:20-12:20 slot (replacing CODEC, which will not be meeting). If anyone has serious issues with this, let us know ASAP.
>
> Thanks,
> Alissa
> _______________________________________________
> 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

Sunday, March 25, 2012

Re: [Geopriv] Agenda swap

Did this happen?

-Marc-

-----Original Message-----
From: Alissa Cooper <acooper@cdt.org>
Date: Fri, 16 Mar 2012 14:45:14 -0400
To: GEOPRIV WG <geopriv@ietf.org>
Subject: [Geopriv] Agenda swap

>Due to scheduling conflicts and the short length of our agenda, Richard
>and I intend to request to move GEOPRIV into the Friday 11:20-12:20 slot
>(replacing CODEC, which will not be meeting). If anyone has serious
>issues with this, let us know ASAP.
>
>Thanks,
>Alissa
>_______________________________________________
>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

Thursday, March 22, 2012

[Geopriv] Fwd: Developer Feedback results

From the W3C Geolocation API mailing list, some interesting data about location privacy preferences.

Begin forwarded message:

From: "Cheng, Diana, Vodafone Group" <Diana.Cheng@vodafone.com>
Subject: Developer Feedback results
Date: March 22, 2012 11:09:37 AM EDT

Hello there,
 
As part of the work for the Geolocation specification, I put out a developer and user survey through the Vodafone Developer platform with the aim of gathering some feedback for the WG.  It took a while unfortunately until we were able to make the results public and individual comments and statements had needed to be removed due to internal policies, but the main results are shared in this blog post: http://developer.vodafone.com/blog/2012/03/22/geolocation-api-survey-results/
 
This was discussed at our last F2F at the beginning of March in London. Hopefully, this kind of feedback has been useful for the working group and will be for other specifications going forward.
 
Thanks and best regards,
 

Diana Cheng
Web & Social Media Expert
Internet Standards, Group R&D
Vodafone Group Services GmbH
Mobile: +491735374317
Email: diana.cheng@vodafone.com
 

Vodafone Group Services GmbH, Mannesmannufer 2, D-40213 Düsseldorf Amtsgericht Düsseldorf, HRB 53554 Geschäftsführung: Dr. Joachim Peters, Rainer Wallek

vodafone.com
 

Tuesday, March 20, 2012

[Geopriv] Last Call: (Geolocation Policy: A Document Format for Expressing Privacy Preferences for Location Information) to Proposed Standard

The IESG has received a request from the Geographic Location/Privacy WG
(geopriv) to consider the following document:
- 'Geolocation Policy: A Document Format for Expressing Privacy
Preferences for Location Information'
<draft-ietf-geopriv-policy-25.txt> as a Proposed Standard

This last call focuses on the changes related to location obfuscation (fuzzing)
resulting from additional working group attention resulting from a prior IESG review.
Please focus the review on the difference between versions -21 and -25 of this draft.

Version -21 of this document was IETF LCed in Jun 2010. Subsequent
IESG review identified an issue with location obfuscation that required
additional working group attention.

Version -11 of this document was IETF LCed in Feb 2007 - subsequent
IESG review identified several issues. The resulting working group
discussion resulted in significant changes to the document.


The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2012-04-03. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


This document defines an authorization policy language for
controlling access to location information. It extends the Common
Policy authorization framework to provide location-specific access
control. More specifically, this document defines condition elements
specific to location information in order to restrict access based on
the current location of the Target.

Furthermore, this document defines two algorithms for reducing the
granularity of returned location information. The first algorithm is
defined for usage with civic location information while the other one
applies to geodetic location information. Both algorithms come with
limitations, i.e. they provide location obfuscation under certain
conditions and may therefore not be appropriate for all application
domains.


The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-geopriv-policy/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-geopriv-policy/ballot/


No IPR declarations have been submitted directly on this I-D.


_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

Friday, March 16, 2012

[Geopriv] Agenda swap

Due to scheduling conflicts and the short length of our agenda, Richard and I intend to request to move GEOPRIV into the Friday 11:20-12:20 slot (replacing CODEC, which will not be meeting). If anyone has serious issues with this, let us know ASAP.

Thanks,
Alissa
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

Wednesday, March 14, 2012

[Geopriv] Draft IETF 83 agenda

Here is a draft agenda for GEOPRIV at IETF 83. You can see there isn't much there. Please send comments to the list this week if you have any.

5m Intro & administrivia (chairs)
20m draft-bellis-geopriv-flow-identity (Ray)
20m Future of GEOPRIV (chairs)
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

Monday, March 12, 2012

[Geopriv] I-D Action: draft-ietf-geopriv-dhcp-lbyr-uri-option-14.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Geographic Location/Privacy Working Group of the IETF.

Title : Dynamic Host Configuration Protocol (DHCP) IPv4 and IPv6 Option for a Location Uniform Resource Identifier (URI)
Author(s) : James Polk
Filename : draft-ietf-geopriv-dhcp-lbyr-uri-option-14.txt
Pages : 13
Date : 2012-03-12

This document creates a Dynamic Host Configuration Protocol (DHCP)
Option for transmitting a client's geolocation Uniform Resource
Identifier (URI). This Location URI can then be dereferenced in a
separate transaction by the client or sent to another entity and
dereferenced to learn physically where the client is located.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-geopriv-dhcp-lbyr-uri-option-14.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-geopriv-dhcp-lbyr-uri-option-14.txt

_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

Saturday, March 10, 2012

[Geopriv] I-D Action: draft-ietf-geopriv-dhcp-lbyr-uri-option-13.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Geographic Location/Privacy Working Group of the IETF.

Title : Dynamic Host Configuration Protocol (DHCP) IPv4 and IPv6 Option for a Location Uniform Resource Identifier (URI)
Author(s) : James Polk
Filename : draft-ietf-geopriv-dhcp-lbyr-uri-option-13.txt
Pages : 13
Date : 2012-03-10

This document creates a Dynamic Host Configuration Protocol (DHCP)
Option for transmitting a client's geolocation Uniform Resource
Identifier (URI). This Location URI can then be dereferenced in a
separate transaction by the client or sent to another entity and
dereferenced to learn physically where the client is located.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-geopriv-dhcp-lbyr-uri-option-13.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-geopriv-dhcp-lbyr-uri-option-13.txt

_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

Thursday, March 1, 2012

Re: [Geopriv] New Version Notification for draft-bellis-geopriv-flow-identity-00.txt

This is pretty good. The only addition that I would make is to ensure
that the next great network or transport protocol gets a chance at
working here. Extension points for layer3 and layer4 are probably a
good idea. Fortunately, UPA isn't a problem, so you can make the
simple type a union of what you have and xs:token (or some restriction
thereof in order to restrict the valid set of characters to something
sensible).

I do think that your justification could be made clearer. You wish to
identify a host on the remote side of a NAT by identifying a flow that
you know that host is participating in. We all got this one wrong.

--Martin

On 29 February 2012 08:45, Ray Bellis <Ray.Bellis@nominet.org.uk> wrote:
> It's only the complete 6-tuple that uniquely identifies the flow, and hence
> the internal target behind that NAT.
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

Wednesday, February 29, 2012

Re: [Geopriv] New Version Notification for draft-bellis-geopriv-flow-identity-00.txt


On 29 Feb 2012, at 16:39, Tschofenig, Hannes (NSN - FI/Espoo) wrote:

Hi Ray,
 
ports are specified in HELD identity.

Indeed, and it was my idea in the first place.

But I didn't get it right.
 
Since the idea of HELD is to find out where the entity (as described by an IP address, etc.) is I wonder why it would be useful to include the destination address and port number (which is what a flow information adds).

Because on a CGN (and some other NATs) it's possible for the same source IP / port pair to be part of lots of flows at once.

It's only the complete 6-tuple that uniquely identifies the flow, and hence the internal target behind that NAT.

Ray


Re: [Geopriv] Fwd: New Version Notification for draft-bellis-geopriv-flow-identity-00.txt

> Since the idea of HELD is to find out where the entity (as described by an IP address, etc.) is I wonder why it would be useful to include the destination address and port number (which is what a flow information adds).

I can name that tune in 3 letters: CGN.

--Ricahrd

>
> Ciao
> Hannes
>
>
> From: geopriv-bounces@ietf.org [mailto:geopriv-bounces@ietf.org] On Behalf Of ext Ray Bellis
> Sent: Wednesday, February 29, 2012 6:29 PM
> To: GEOPRIV WG
> Subject: [Geopriv] Fwd: New Version Notification for draft-bellis-geopriv-flow-identity-00.txt
>
> I've just submitted the draft detailed below, available at:
>
> http://tools.ietf.org/html/draft-bellis-geopriv-flow-identity-00
>
> Textually, it's somewhat rough, but I wanted to get feedback on the general idea (and the validity of the XSD) before spending too much time on the words themselves.
>
> Ray
>
>
> From: <internet-drafts@ietf.org>
> Subject: New Version Notification for draft-bellis-geopriv-flow-identity-00.txt
> Date: 29 February 2012 16:26:12 GMT
> To: <ray.bellis@nominet.org.uk>
>
> A new version of I-D, draft-bellis-geopriv-flow-identity-00.txt has been successfully submitted by Ray Bellis and posted to the IETF repository.
>
> Filename: draft-bellis-geopriv-flow-identity
> Revision: 00
> Title: Flow Identity Extension for HELD
> Creation date: 2012-02-29
> WG ID: Individual Submission
> Number of pages: 12
>
> Abstract:
> Identity Extensions using an IP address and port number to request a
> location based on an individual packet flow have been previously
> specified by the GEOPRIV Working Group.
>
> However certain kinds on NAT require that identifiers for both ends
> of the packet flow must be specified in order to unambiguously
> satisfy the location request.
>
> This document specifieds a Flow Identity Extension for the HTTP-
> Enabled Location Delivery (HELD) Protocol to support this
> requirement.
>
>
> _______________________________________________
> 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

Re: [Geopriv] New Version Notification for draft-bellis-geopriv-flow-identity-00.txt

On 29 Feb 2012, at 16:29, Ray Bellis wrote:

> Textually, it's somewhat rough

By which I meant to say, there's barely any text at all, yet...

Ray

_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

Re: [Geopriv] Fwd: New Version Notification for draft-bellis-geopriv-flow-identity-00.txt

Hi Ray,

 

ports are specified in HELD identity.

 

Since the idea of HELD is to find out where the entity (as described by an IP address, etc.) is I wonder why it would be useful to include the destination address and port number (which is what a flow information adds).

 

Ciao
Hannes

 

 

From: geopriv-bounces@ietf.org [mailto:geopriv-bounces@ietf.org] On Behalf Of ext Ray Bellis
Sent: Wednesday, February 29, 2012 6:29 PM
To: GEOPRIV WG
Subject: [Geopriv] Fwd: New Version Notification for draft-bellis-geopriv-flow-identity-00.txt

 

I've just submitted the draft detailed below, available at:

 

 

Textually, it's somewhat rough, but I wanted to get feedback on the general idea (and the validity of the XSD) before spending too much time on the words themselves.

 

Ray



Subject: New Version Notification for draft-bellis-geopriv-flow-identity-00.txt

Date: 29 February 2012 16:26:12 GMT

 

A new version of I-D, draft-bellis-geopriv-flow-identity-00.txt has been successfully submitted by Ray Bellis and posted to the IETF repository.

Filename:      draft-bellis-geopriv-flow-identity
Revision:       00
Title:                                   Flow Identity Extension for HELD
Creation date:                     2012-02-29
WG ID:                              Individual Submission
Number of pages: 12

Abstract:
  Identity Extensions using an IP address and port number to request a
  location based on an individual packet flow have been previously
  specified by the GEOPRIV Working Group.

  However certain kinds on NAT require that identifiers for both ends
  of the packet flow must be specified in order to unambiguously
  satisfy the location request.

  This document specifieds a Flow Identity Extension for the HTTP-
  Enabled Location Delivery (HELD) Protocol to support this
  requirement.

 

[Geopriv] Fwd: New Version Notification for draft-bellis-geopriv-flow-identity-00.txt

I've just submitted the draft detailed below, available at:


Textually, it's somewhat rough, but I wanted to get feedback on the general idea (and the validity of the XSD) before spending too much time on the words themselves.

Ray

Subject: New Version Notification for draft-bellis-geopriv-flow-identity-00.txt
Date: 29 February 2012 16:26:12 GMT

A new version of I-D, draft-bellis-geopriv-flow-identity-00.txt has been successfully submitted by Ray Bellis and posted to the IETF repository.

Filename: draft-bellis-geopriv-flow-identity
Revision: 00
Title: Flow Identity Extension for HELD
Creation date: 2012-02-29
WG ID: Individual Submission
Number of pages: 12

Abstract:
  Identity Extensions using an IP address and port number to request a
  location based on an individual packet flow have been previously
  specified by the GEOPRIV Working Group.

  However certain kinds on NAT require that identifiers for both ends
  of the packet flow must be specified in order to unambiguously
  satisfy the location request.

  This document specifieds a Flow Identity Extension for the HTTP-
  Enabled Location Delivery (HELD) Protocol to support this
  requirement.


Tuesday, February 28, 2012

[Geopriv] FW: New Version Notification for draft-ietf-geopriv-local-civic-03.txt

Hi All,

We have just submitted the updated Local Civic draft. We believe that this version addresses all outstanding issues including the IANA recommendation of modifying the existing CAType repository. If you have any issues please send them to the list.

Cheers
James

A new version of I-D, draft-ietf-geopriv-local-civic-03.txt has been successfully submitted by James Winterbottom and posted to the IETF repository.

Filename: draft-ietf-geopriv-local-civic
Revision: 03
Title: Specifying Civic Address Extensions in PIDF-LO
Creation date: 2012-02-28
WG ID: geopriv
Number of pages: 19

Abstract:
New fields are occasionally added to civic addresses. A backwardly-
compatible mechanism for adding civic address elements to the Geopriv
civic address format is described. A formal mechanism for handling
unsupported extensions when translating between XML and DHCP civic
address forms is defined for entities that need to perform this
translation. Intial extensions for some new elements are also
defined. The LoST protocol mechanism that returns civic address
element names used for validation of location information is
clarified to require a namespace on each element.


The IETF Secretariat
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

[Geopriv] I-D Action: draft-ietf-geopriv-local-civic-03.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Geographic Location/Privacy Working Group of the IETF.

Title : Specifying Civic Address Extensions in PIDF-LO
Author(s) : James Winterbottom
Martin Thomson
Richard Barnes
Brian Rosen
Robins George
Filename : draft-ietf-geopriv-local-civic-03.txt
Pages : 19
Date : 2012-02-28

New fields are occasionally added to civic addresses. A backwardly-
compatible mechanism for adding civic address elements to the Geopriv
civic address format is described. A formal mechanism for handling
unsupported extensions when translating between XML and DHCP civic
address forms is defined for entities that need to perform this
translation. Intial extensions for some new elements are also
defined. The LoST protocol mechanism that returns civic address
element names used for validation of location information is
clarified to require a namespace on each element.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-geopriv-local-civic-03.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-geopriv-local-civic-03.txt

_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv