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