On 1 Jan 2019, at 1:28, John R Levine wrote: > foo VARIANT n1 n2 n3 n4 ... > > The fields are 32 bit ints, each of which is interpreted as a UTF-32 code > point. The meaning is that in the subtree at and below this name, n1 is a > canonical code point and the rest are variants. If you get a request with an > a-label that doesn't exist, turn it in to a u-label, replace any of the > variants n2..nx with canonical n1, turn it back into an a-label and try > again. It might synthesize new RRs for the requested name, or CNAMEs give or > take the CNAME at the apex issue.
Hmm...you mean:
If you get a request that include any of the code points {n1, n2,...}, return a
CNAME where nM is replaced with foo?
Patrik
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
