Confirmed, and updated the doc with the RFC reference.
On Mon, Apr 16, 2018 at 11:39 AM, Viktor Dukhovni <[email protected]> wrote: > > > > On Apr 16, 2018, at 2:24 PM, Warren Kumari <[email protected]> wrote: > > > >> 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. > > Yes, but I'm not an author, that's just how I read that text, > so I'll let the authors confirm. Perhaps a reference to: > > https://tools.ietf.org/html/rfc4408#section-3.1.3 > > i,e. "Section 3.1.3 of rfc4408" would help other readers. > > -- > Viktor. > >
_______________________________________________ Uta mailing list [email protected] https://www.ietf.org/mailman/listinfo/uta
