On Mon, Apr 16, 2018 at 2:08 PM, Viktor Dukhovni <ietf-d...@dukhovni.org> wrote: > > >> On Apr 16, 2018, at 1:58 PM, Warren Kumari <war...@kumari.net> wrote: >> >> I throw away the one that contains 'bar', fair enough, got it. What I don't >> understand is what a record would look like which is a single record (#2), >> but >> that contains multiple strings (#3). Can you provide an example of a TXT >> record >> with multiple strings? I don't *think* that this is just me being dense, and >> so >> I think that the document needs to better explain this / include the example. > > Strings in TXT records have a single-octet length field. When returning a > longer > string, or when one wants to explicitly segment a TXT RDATA into multiple > strings > one returns: > > txt.example. IN TXT "first string" "second string" ... "last string" > > with the wire RDATA being: > > <len1>first string<len2>second string...<lenN>last string >
Ah, you mean basically do what RFC4408, S 3.1.3 says? I *completely* didn't understand that from the above... I still think that it would be useful to have an example of multiple strings which meet the above (preferably in "zone file" format) but I'll accept that I was just being dumb and clear my DISCUSS. W > -- > Viktor. -- I don't think the execution is relevant when it was obviously a bad idea in the first place. This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants. ---maf _______________________________________________ Uta mailing list Uta@ietf.org https://www.ietf.org/mailman/listinfo/uta
