Well, I haven't doubt that it is on our charter, but I have questioned the timing.
Martin [email protected] NEC Laboratories Europe - Network Research Division NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London W3 6BL | Registered in England 2832014 > -----Original Message----- > From: Roni Even [mailto:[email protected]] > Sent: Friday, March 06, 2009 12:35 PM > To: Martin Stiemerling; 'songhaibin 64081'; 'Gustavo Garcia Bernardo' > Cc: [email protected] > Subject: RE: [alto] ALTO server discovery > > Martin, > This is from the WG charter > > - In order to query the ALTO server, clients must first know one or > more ALTO servers that might provide useful information. The WG > will look at service discovery mechanisms that are in use, or > defined elsewhere (e.g. based on DNS SRV records or DHCP options). > If such discovery mechanisms can be reused, the WG will produce a > document to specify how they may be adopted for locating such > servers. However, a new, general-purpose service discovery > mechanism is not in scope. > > So this is chartered work. > > Regards > Roni Even > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of > Martin Stiemerling > Sent: Friday, March 06, 2009 12:21 PM > To: songhaibin 64081; Gustavo Garcia Bernardo > Cc: [email protected] > Subject: Re: [alto] ALTO server discovery > > Hi all, > > Just a (probably) very silly question: > > Isn't it way too early to get a discussion about ALTO server discovery > started? And also (as Lisa pointed out) there are already many > mechanisms to > discover hosts, server, and services. > > I see more the need to spend cycles on ALTO problem space, reqs, > basically > where do we go with that?! > > Just my two cents > > Martin > > [email protected] > > NEC Laboratories Europe - Network Research Division > NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, > London > W3 6BL | Registered in England 2832014 > > > -----Original Message----- > > From: [email protected] [mailto:[email protected]] On Behalf > Of > > songhaibin 64081 > > Sent: Friday, March 06, 2009 3:50 AM > > To: Gustavo Garcia Bernardo > > Cc: [email protected] > > Subject: Re: [alto] ALTO server discovery > > > > Dear Gustavo, > > > > > Our idea is to avoid > > > defining new discovery protocols and reuse the existing ones > > > describing how they can be applied to the ALTO use case. > > > > > > > We have the same thought, and that's also what we did in draft-song- > > alto-server-discovery. > > > > Regards, > > Haibin > > > > > > > BR, > > > G. > > > > > > ________________________________________ > > > From: [email protected] [[email protected]] On Behalf Of > > > songhaibin 64081 [[email protected]] > > > Sent: Thursday, March 05, 2009 10:25 AM > > > To: [email protected] > > > Subject: [alto] ALTO server discovery > > > > > > Hi all, > > > > > > We also submit an ALTO server discovery draft. Here is the link: > > > > > > http://tools.ietf.org/id/draft-song-alto-server-discovery-00.txt > > > > > > Now there are two drafts on ALTO server discovery. I think they > > > have commonness and differences. Our draft mainly focuses on the > > > scenario where network operators provide the alto servers. The > > > solution has the consideration for residential gateways when using > > > DHCP option to retrieve the alto service name. We also take into > > > account the discovery process by end terminals and application > > > trackers(or proxies). These two drafts can be of compleme > > > ntary to each other. > > > > > > Any comments are appreciated! > > > > > > Best Regards! > > > Song Haibin > > > _______________________________________________ > > > alto mailing list > > > [email protected] > > > https://www.ietf.org/mailman/listinfo/alto > > > > > _______________________________________________ > > alto mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/alto > _______________________________________________ > alto mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/alto _______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
