60 likes | 173 Views
draft-barnes-geopriv-policy-uri. -03 (err… -02). We updated the draft (-02) in early September … and forgot to post it We updated it again (-03) right before the IETF … and missed the deadline All changes now rolled in to -02 Clarifications around default policies Considerations about NATs
E N D
-03 (err… -02) • We updated the draft (-02) in early September • … and forgot to post it • We updated it again (-03) right before the IETF • … and missed the deadline • All changes now rolled in to -02 • Clarifications around default policies • Considerations about NATs • Deployment considerations • Several minor editorial clean-ups
Default Policies • Document talks a few times about using a GET to find out the server’s default policy • But HELD says the default policy is open access • Revised to clarify: • Client’s safest assumption is open access • … but server may apply a more restrictive policy • … which the client can find out with a GET • Also made policy examples more explicit with regard to privacy rules
NATs • In certain circumstances, multiple clients look the same to the server • Risk that one could overwrite another’s policy • Guidance to server: Two options • Provide a fresh location URI and policy URI for each request (so multiple clients don’t overlap) • Use a restrict of the policy language defined here • MUST NOT accept PUT or DELETE requests
Deployment Considerations • Previous documents (held-context) overlaid policy operations on location configuration • Revised to explain that using a separate transaction • Costs an HTTP RTT, but • Gains generality, e.g., DHCP coverage • Also suggested how servers can minimize overhead cost (implicit storage of default)
Next Steps • All known issues resolved • Would like a review from a fresh reviewer • Call for WG adoption toward the end of November • Move to WGLC as soon as milestone is in place