Hi, As I understand it, the proposal does not intend to keep a registry of the URIs used for discovery (it is a parameter for a query using HTTP GET) and, therefore, ALTO could mandate its own URI, in the same way the U-NAPTR lookup defines the string to be queried.
The requirements on external registrations are essentially the same in both cases (none, I think). My point is that an ALTO client would have to rely only in queries aligned with the rest of the transport protocol, i.e. plain HTTP(S), and not be required to include support for specific DNS queries. Be goode, On 7 Nov 2012, at 15:50 , Scharf, Michael (Michael) wrote: > After briefly scanning through draft-jones-simple-web-discovery, which seems > to be an individual draft, I wonder how the ALTO service would be registered > in this solution. The text states: "The definition of URIs used to identify > principals and services are outside the scope of this specification." If such > issues are not clear as of now, it is unclear to me whether this is indeed a > mature technology. > > At first sight, compared to that, the U-NAPTR lookup is a well-understood > mechanism used by other IETF protocols with similar requirements like ALTO. > > Michael > -- "Esta vez no fallaremos, Doctor Infierno" Dr Diego R. Lopez Telefonica I+D http://people.tid.es/diego.lopez/ e-mail: [email protected] Tel: +34 913 129 041 Mobile: +34 682 051 091 ----------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
