Technical Summary
Current location configuration protocols are capable of provisioning
an Internet host with a location URI that refers to the host's
location. These protocols lack a mechanism for the target host to
inspect or set the privacy rules that are applied to the URIs they
distribute. This document extends the current location configuration
protocols to provide hosts with a reference to the rules that are
applied to a URI, so that the host can view or set these rules.
Working Group Summary
This document was uncontroversial. It fills a gap in the location
configuration architecture.
Document Quality
At this time there are no known implementations, nor are there any
reviewers or experts that merit a special mention.
Personnel
Robert Sparks is the responsible Area Director.
Alissa Cooper is the document shepherd.
RFC Editor Note
In Section 1:
OLD: "We then define extensions to the HELD protocol and the DHCP option for location by reference to allow these protocols to carry policy URIs."
NEW: "We then define an extension to the HELD protocol to allow it to carry policy URIs."
In Section 3.1:
OLD: "This expiry time is specified by the 'expires' attribute in the HELD locationResponse or the 'Valid-For' LuriType in DHCP."
NEW: "This expiry time is specified by the 'expires' attribute in the HELD locationResponse."
In Section 3.2:
OLD: "For DHCP and HELD, the client assumes that..."
NEW: "For HELD, the client assumes that..."
Delete Section 4.2
In Section 4.3:
OLD: "policy URI received from either HELD or DHCP"
NEW: "policy URI received from HELD"
Delete Section 5.2 and merge Section 5 and Section 5.1
Delete Section 6.3
In Section 7.1:
OLD: "(see [RFC5985] and [I-D.ietf-geopriv-dhcp-lbyr-uri-option])"
NEW: "(see [RFC5985])"
In Section 7.2:
OLD: "The lifetime T of a location URI set is specified by the "expires" attribute in HELD or the "Valid-For" LuriType in DHCP."
NEW: "The lifetime T of a location URI set is specified by the "expires" attribute in HELD."
Remove the reference [I-D.ietf-geopriv-dhcp-lbyr-uri-option]
Update Author information to the following:
Richard Barnes
Mozilla
650 Castro St., Suite 300
Mountain View, CA, US 94041
rlb@ipv.sx
Martin Thomson
Mozilla
650 Castro St., Suite 300
Mountain View, CA, US 94041
martin.thomson@gmail.com
James Winterbottom
Unaffiliated
a.james.winterbottom@gmail.com
Hannes Tschofenig
Unaffiliated
hannes.tschofenig@gmx.net