I support the adoption of both documents.

For the lmap use cases, 3rd party discovery may be necessary, e.g. if a web 
service provider want to find out which ALTO server can provide LMAP result for 
a given end user IP address.

 - Jan

> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of
> Sebastian Kiesel
> Sent: Thursday, October 17, 2013 2:05 PM
> To: Enrico Marocco
> Cc: [email protected]
> Subject: Re: [alto] WG adoption of *-3pdisc and *-ip-based-srv-disc drafts
> 
> Dear all,
> 
> On Tue, Oct 15, 2013 at 09:44:54AM +0200, Enrico Marocco wrote:
> > Dear WG participants:
> >
> > we would like to check consensus on the adoption of the following drafts
> > that will complement the server discovery deliverable in the current
> > ALTO WG charter:
> >
> >   + draft-kiesel-alto-ip-based-srv-disc
> >   + draft-kist-alto-3pdisc
> 
> [writing as a co-author of these two drafts]
> 
> Of course I think both drafts are useful and should be adopted, but
> I leave the decision up to our valued chairmen whether to consider/count
> this statement. :)
> 
> 
> 
> [writing as a co-author of RFC 6708 (ALTO requirements)]
> 
> I'd like to bring to your attention that AR-33 (third-party discovery)
> is the only requirement we have documented, for which no WG item
> specification exists so far.
> draft-kist-alto-3pdisc provides a solution for this requirement.
> However, if someone knows another (better?) solution, please share it
> with us now.
> 
> AR-32 (resource consumer initiated ALTO server discovery) is supported
> by draft-ietf-alto-server-discovery-10, which is now in the RFC editor
> queue.  While this draft is definitely uselful in several important
> deployment scenarios, it is not 100% optimal in the light of AR-37.
> This is where draft-kiesel-alto-ip-based-srv-disc fits in.
> 
> Thanks
> Sebastian
> _______________________________________________
> alto mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/alto
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto

Reply via email to