Application-Layer Traffic Optimization
charter-ietf-alto-04

Note: This ballot was opened for revision 03-00 and is now closed.

Ballot question: "Is this charter ready for external review?"

(Spencer Dawkins) Yes

(Martin Stiemerling) Yes

(Jari Arkko) No Objection

(Alia Atlas) No Objection

Comment (2014-05-14 for -03-00)
No email
send info
I find myself in complete agreement with Adrian and Alissa.

(Richard Barnes) No Objection

Comment (2014-05-15 for -03-01)
No email
send info
I support Alissa's concerns about the Everything Protocol, and especially about the utility of existing discovery mechanisms.

(Benoît Claise) No Objection

Alissa Cooper (was Block) No Objection

(Adrian Farrel) (was Block) No Objection

Comment (2014-05-14 for -03-01)
No email
send info
Thanks for addressing my concerns

(Stephen Farrell) (was Block) No Objection

Comment (2014-05-15 for -03-01)
No email
send info
If you did s/privacy/privacy and information leakage/
in the relavant paragraph, that'd be lovely. (What whatever
wordsmithing would be needed.)

(Brian Haberman) No Objection

(Joel Jaeggli) No Objection

Comment (2014-05-11 for -03-00)
No email
send info
Given the position I found myself with respect to alto documents I would strongly encourage the working group to consider the implications of information leakage when pursuing additional work e.g. the product of client queries to the map.

DNS it turns out has to consider some similar problems under the rubric of dnspriv.

Barry Leiba No Objection

(Ted Lemon) No Objection

Comment (2014-05-13 for -03-00)
No email
send info
My fellow ADs have already identified the issues that jumped out at me when I read this, and I support their blocks and comments.

(Kathleen Moriarty) No Objection

Comment (2014-05-15 for -03-03)
No email
send info
I agree with Stephen's comments, adding something about privacy would be lovely.

(Pete Resnick) No Objection