> Except, of course, that it's not a "DN" at all: it's not a domain > name.
Also not "qualified", as long as we're quibbling. But I do think the distinction between FQDN and <thing we're talking about> is a useful one to have terminology for, and "LQDN" does get the job done even though it doesn't make proper acronymic sense; I suggest we continue using it here in the short term and plan on switching to a more precisely accurate term by the time we start producing RFC's. I don't have spare cycles to participate in the bikeshedding, but I'll be happy with anything that agrees with the definition previously proposed for "LQDN". -- Evan Hunt -- [email protected] Internet Systems Consortium, Inc. _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
