Last Call Review of draft-ietf-geopriv-uncertainty-03

Request Review of draft-ietf-geopriv-uncertainty
Requested rev. no specific revision (document currently at 04)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2014-10-07
Requested 2014-09-29
Authors Martin Thomson, James Winterbottom
Draft last updated 2014-10-02
Completed reviews Genart Last Call review of -03 by Alexey Melnikov (diff)
Secdir Last Call review of -03 by Takeshi Takahashi (diff)
Opsdir Last Call review of -03 by Warren Kumari (diff)
Assignment Reviewer Warren Kumari
State Completed
Review review-ietf-geopriv-uncertainty-03-opsdir-lc-kumari-2014-10-02
Reviewed rev. 03 (document currently at 04)
Review result Has Nits
Review completed: 2014-10-02


Be ye not afraid -- I have reviewed this document as part of the
security directorate's ongoing effort to review all IETF documents
being processed by the IESG.  These comments were written primarily
for the benefit of the security area directors.  Document editors and
WG chairs should treat these comments just like any other last call

Disclaimer: Math is hard. Let's go shopping...

Gadzooks! This draft is full of complex sounding things that I know
nothing about. That said, I found it interesting -- I still don't
understand the half of it, but it sure sounded good :-)

I see no operational concerns here (other than physical ones -- if I
publish the location of my datacenter with small uncertainty some folk
may be more likely to drive over and try actually find it...) This is
a serious reach though...

I suspect that someone with more privacy clue should review / comment.


I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.