> If I understood ILNP correctly, each ILNP host needs a globally unique FQDN. > That’s to say, the FQDN can not be used as a service ID to represent a set > of ILNP servers which are scattered in the Internet. As a result, the above > load-balancing service through DNS is not available anymore in the ILNP > architecture. Maybe another indirection from one FQDN (representing a > Service ID) to another one (representing a Host ID) should be developed in > order to support the above service.
Hi, That's an interesting interpretation. ILNP uses an explicit numeric token as the identifier. The FQDN is not the identifier. The identifier can be found in the I record. On a forward reference, a FQDN is resolved into an I record and one or more L records. In the case of a service name, it is not unreasonable for DNS to return multiple I records, each with an associated set of L records. This is not explicitly called out in the current ILNP documentation, but is a reasonable extrapolation from current usage, plus the existing documents. Regards, Tony _______________________________________________ rrg mailing list rrg@irtf.org http://www.irtf.org/mailman/listinfo/rrg
