On Wednesday 05 November 2008 14:00:35 Peter Saint-Andre wrote: > Discussion: Dave raised some questions about the TXT record data format. > Peter to ping the DNS-SD authors, Dave and Ralph to do some testing of > real-world deployments.
Kev fails for not contacting me about this. The dig output is pretty and doesn't include the length byte which is indeed in the record data. The question is really about XEP-174's usage of that "text-based DNS record description notation" (for lack of a better name) in the context of representing multiple strings, and not about the actual TXT raw byte format of which there is no dispute. I'm not sure if there's an authoritative source for that text-based DNS record description notation (other than RFC 1035, which is quite sketchy), but information about SPF reveals the use of multiple strings in one line. E.g.: example.com. 4500 IN TXT "string1" "string2" "string3" Indeed, sending dig at a TXT record containing multiple strings prints the result exactly this way. You can dig iChat like this: dig @ip_address_of_ichat -p 5353 -t txt [EMAIL PROTECTED] So, I think the right answer is to put all strings on one line. From what I can tell, the DNS-SD spec dodges this topic by not using the notation at all, which is not a bad approach either. :) It's not like anyone implementing XEP-174 will be parsing this format. -Justin
