Hi,kiesel Well done. Would you be kind to explain some issues? 1, Do you have some example in mind when you point out "Peer-ID" in Approach #3? What kind of info can uniquely identify a client or provider behind NATs? And what kind of info, which client can obtain without much effort, can uniquely identify one without NATs other than IP Add. 2, As far as I know, there seems no way to figure out whether 2 clients are behind the same NAT, therefore no good way to do intra-domain optimization, even for Approach #3, #4 and #5. So could you tell how to do intra-domain optimization in these scenarios?
Thank you very much. Regards Yingjie Gu > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Sebastian Kiesel > Sent: Thursday, August 27, 2009 2:07 AM > To: [email protected] > Subject: [alto] FWD: I-D Action:draft-kiesel-alto-3pdisc-00.txt > > Hi, > > Marco and I have created a document that details the issues > about third-party ALTO server discovery, which were raised in > Stockholm. Comments welcome. > > Thanks, > > Marco and Sebastian > > > ----- Forwarded message from [email protected] ----- > > From: [email protected] > To: [email protected] > Subject: I-D Action:draft-kiesel-alto-3pdisc-00.txt > Date: Wed, 26 Aug 2009 11:00:01 -0700 (PDT) > Reply-To: [email protected] > List-Id: Internet Draft Announcements only <i-d-announce.ietf.org> > > A New Internet-Draft is available from the on-line > Internet-Drafts directories. > > Title : Third-party ALTO server discovery > Author(s) : S. Kiesel, M. Tomsu > Filename : draft-kiesel-alto-3pdisc-00.txt > Pages : 15 > Date : 2009-08-26 > > The goal of Application-Layer Traffic Optimization (ALTO) is > to provide guidance to applications, which have to select one > or several hosts from a set of candidates, that are able to > provide a desired resource. > > This document describes why a third-party ALTO server > discovery mechanism is required for an important class of > applications, namely tracker-based P2P applications. Several > solution approaches are classified and evaluated. The > conclusion is that further work is required to standardize a > protocol and procedures that follow one specific approach. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-kiesel-alto-3pdisc-00.txt > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > Below is the data which will enable a MIME compliant mail > reader implementation to automatically retrieve the ASCII > version of the Internet-Draft. > > > _______________________________________________ > I-D-Announce mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/i-d-announce > Internet-Draft directories: http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > ----- End forwarded message ----- > > -- > Sebastian Kiesel mailto:[email protected] > Network Research Division tel:+49-6221-4342-232 > fax:+49-6221-4342-155 > NEC Laboratories Europe Kurfuerstenanlage 36, 69115 > Heidelberg, Germany > -- > NEC Europe Limited Registered in England 2832014 > Registered Office NEC House, 1 Victoria Road, London W3 6BL > > _______________________________________________ > alto mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/alto _______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
