On Jun 29, 2012, at 5:09 PM 6/29/12, Joe Touch wrote: > > > On 6/29/2012 1:09 PM, Ralph Droms wrote: >> >> On Jun 29, 2012, at 3:58 PM 6/29/12, james woodyatt wrote: >> >>> On Jun 29, 2012, at 11:27 , Michael Thomas <[email protected]> wrote: >>>> >>>> Maybe I can add some fuel to Olafur's fire. I'd like to say that the >>>> homenet name service MUST be DNS. >>> >>> Let's go further. Let's say that it must be DNS-Based Service Discovery >>> [I-D.cheshire-dnsext-dns-sd], which has been in the RFC Editor Queue for >>> 199 days at this point, so one imagines that it stands a decent chance of >>> being a published RFC by the time HOMENET finishes its first round of major >>> work. >> >> Well, DNS-Based Service Discovery addresses just one kind of requirement: >> listing entities that provide a certain kind of service; perhaps >> generalizable to resolution based on a characteristic or set of >> characteristics that might return more than one response to the resolution >> request. At some point, there needs to be a mechanism for resolving an >> identity to a single IP address. > > Why? if the DNS gives multiple answers, they're intended to be equivalent for > that service.
Sure...I should have said "resolve an identity to an IP address or address(es)". - Ralph > > Joe _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
