Extensions to the Proxy Mobile IPv6 (PMIPv6) Access Network Identifier Option
draft-ietf-netext-ani-location-09
Yes
(Brian Haberman)
No Objection
(Adrian Farrel)
(Alia Atlas)
(Barry Leiba)
(Benoît Claise)
(Jari Arkko)
(Kathleen Moriarty)
(Martin Stiemerling)
(Pete Resnick)
(Spencer Dawkins)
(Ted Lemon)
Note: This ballot was opened for revision 08 and is now closed.
Brian Haberman Former IESG member
Yes
Yes
(for -08)
Unknown
Adrian Farrel Former IESG member
No Objection
No Objection
(for -08)
Unknown
Alia Atlas Former IESG member
No Objection
No Objection
(for -08)
Unknown
Barry Leiba Former IESG member
No Objection
No Objection
(for -08)
Unknown
Benoît Claise Former IESG member
No Objection
No Objection
(for -08)
Unknown
Jari Arkko Former IESG member
No Objection
No Objection
(for -08)
Unknown
Kathleen Moriarty Former IESG member
No Objection
No Objection
(for -08)
Unknown
Martin Stiemerling Former IESG member
No Objection
No Objection
(for -08)
Unknown
Pete Resnick Former IESG member
No Objection
No Objection
(for -08)
Unknown
Richard Barnes Former IESG member
(was Discuss)
No Objection
No Objection
(2015-03-19 for -08)
Unknown
Thanks for a good discussion of confidentiality protections in the Security Considerations. It would be helpful if you could also note that another way to address the concerns here is to provision location information at the least granular level possible. Suggested: "The other way to protect the sensitive location information of network users is of course to not send it in the first places. Users of the civic location sub option should provision location values with the highest possible level of granularity, e.g., to the province or city level, rather than provisioning specific addresses. In addition to helping protect private information, reducing granularity will also reduce the size of the civic location sub option." I cleared because it looks like we are agreed on point (4) of my DISCUSS, i.e., that the XML/URI-based option will be removed in favor of just using the DHCP option. I trust Brian and the authors will make sure the change is made.
Spencer Dawkins Former IESG member
No Objection
No Objection
(for -08)
Unknown
Stephen Farrell Former IESG member
No Objection
No Objection
(2015-03-05 for -08)
Unknown
- What if the network being identified here was a tethering n/w or any other kind of n/w that's carried about by a person? In that case ANI, and these new options, would be privacy invasive. Does that statement exist in one of the RFCs referred to in section 6? If not, would it be worth adding here, even though it might better belong elsewhere? - intro: What if a WLAN operator has no realm? - intro: DPI? What's that got to do with it? I'd suggest removing that.
Ted Lemon Former IESG member
No Objection
No Objection
(for -08)
Unknown