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