Hi Yan, The draft seems to be very interesting :) I do have some questions regarding the arguments about improved privacy...
> Through this way, P2P application could select peers according their CPIDs. > It can balance the workload on the server and also reduce the risks > regarding to the privacy issue, especially for P2P application. Can you define the privacy risks you are addressing, and explain how CPIDs help reduce these privacy risks? I noticed that in draft-wang-alto-privacy-load-analysis-00, in Section 5.5 (which I'm assuming is talking about the CPID approach -- please correct me if I'm wrong), it makes the following statements: "ISP doesn't need P2P operational details, which can reduce the risk of disclosing P2P privacy." What "P2P operational details" do you envision are being sent to the ISP? In P4P, no such information is delivered to the ISP -- it simply provides the PID and pDistance Maps. "Although the ISP topology information can be inferred by the full collection of PIDs as P4P, a correct computational function or driver still need to be obtained additionally to calculate the corresponding cost value." What prevents a set of peers (or even a single peer) from gathering the full list of CPIDs, and simply computing the pairwise cost between each one? Aren't the same costs that the ISP would have delivered in the pDistance map immediately discovered by the P2P application? If so, what has the ISP gained in terms of privacy? Thanks! -- Richard Alimi Department of Computer Science Yale University _______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
