![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Laird Popkin wrote: > As we discussed last week at the IETF P2Pi Workshop, here are a list of > some of the ways that IETF standards can potentially help P2P > applications make better network decisions, and thus help ISPs. This > isn't a complete list, but I hope that it's at least a useful starting > point for a discussion. It seems to me that this turned out to be a two-sided problem. On the one hand, it is clear that applications on the endpoints are in the worst position to make optimal network decisions; a first part of the solution should thus consist of a mechanism to defer such decisions to external entities (not necessarily controlled by ISPs, as e.g. in the case of Ono, where the redirection service is provided by Akamai servers). The need for such a mechanism was claimed by several papers [4,26,28,29] and, AFAIR, received little objection (the one that I recall was the "hot potato" thing, where the external entity providing the peer selection service would be able to place sort of DDOS attacks against specific targets/networks). On the other hand, how to compute best paths is a separate part of the problem; topology/cost/congestion notification, cache identification, usage metrics, and the like all fall in this category and, at this time, are probably more research topics than engineering issues. Right now, I think the IETF should focus on the first part of the problem, the front-end of a generic third-party peer selection service p2p applications can query in order to make better choices; innovation and competition will then happen on the back-end of such a service without requiring standardization in the first place. [*] References at http://www.ietf.org/mail-archive/web/p2pi/current/msg00005.html -- Ciao, Enrico
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ p2pi mailing list p2pi at ietf.org https://www.ietf.org/mailman/listinfo/p2pi