> On 7. Feb 2022, at 20:12, Maxime Devos <maximede...@telenet.be> wrote: > > Schanzenbach, Martin schreef op ma 07-02-2022 om 19:02 [+0000]: >>>> LEGACY HOSTNAME >>>> A UTF-8 string (which is not 0-terminated) representing the >>>> legacy hostname. >>> >>> What happens if it contaings \0, or ends with two dots, does that >> mean >>> the LEHO record is invalid and must be rejected? If it is in >> punycode, >>> why say ‘A UTF-8 string’ instead of ’an ASCII string’? >> >> It is not in punycode. It is just a UTF-8 string. >> Why is it not 0-terminated? TBH I am not sure, probably to save a >> byte :) > > A follow-up question: LEGACY HOSTNAME can be an UTF-8 string, not in > punycode. But can it be in punycode, even though that is not > necessary? Should punycode be forbidden here, in favour of UTF-8?
Well punycode is ASCII. And any ASCII string is (AFAIK) is also a valid uncode string. So yes, you can put punycode in there. BR > > Greetings, > Maxime.
signature.asc
Description: Message signed with OpenPGP