As others pointed out, an ALTO protocol is not expected to make peer selections for the apps. On a high level, it's expected to provide information about the network and about ISP routing preferences. While peer selection preferences vary from application to application substantially, the network itself is the same, and so the information about it remains valid.
-- Stas On Tue, Feb 10, 2009 at 2:14 AM, Zoran Despotovic < [email protected]> wrote: > Hi all, > > I was wondering if and how IETF would address possible differences among > relevant P2P applications in the sense that different applications may > require totally different solutions. Was there any discussion on this before > on the list? > > Just as an example, different criteria to drive peer selection may work > differently for give-to-get streaming and tit-for-tat BT. So how will IETF > deal with this? Standardize different solutions for different applications? > Standardize one solution for all? Pick the most critical (heaviest traffic) > applications and standardize a solution for it? > > It makes sense to clarify that at this early stage and, perhaps, first see > if the solution should and can be application agnostic or not. > > Best regards, > Zoran > > -- > Zoran Despotovic, Ph.D. > Senior Researcher > > DOCOMO Communications Laboratories Europe GmbH > Landsbergerstrasse 312, 80687 Munich, Germany > Tel: +49-89-56824-205 Fax: +49-89-56824-300 > http://www.docomoeurolabs.de/ > > Managing Directors (Geschaeftsfuehrer): > Dr. Toru Otsu, Dr. Narumi Umeda, Mr. Tsutomu Sakai > Amtsgericht Muenchen, HRB 132976 > -------------------------------------------------- > > _______________________________________________ > alto mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/alto > -- Stanislav Shalunov BitTorrent Inc [email protected] personal: http://shlang.com
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
