RFC 1035 says “prior occurance”, which would mean no. 4.1.4. Message compression
In order to reduce the size of messages, the domain system utilizes a compression scheme which eliminates the repetition of domain names in a message. In this scheme, an entire domain name or a list of labels at the end of a domain name is replaced with a pointer to a prior occurance of the same name. Brian > On Apr 15, 2021, at 8:39 AM, John R Levine <jo...@taugh.com> wrote: > > On Thu, 15 Apr 2021, Christian Huitema wrote: >>> Adding test vectors would help, especially broken vectors. >> >> +1. That would be a pretty good way for the IETF to help clean the mess. >> That, and maybe a DNS site that would serve the test vectors. > > In this case I think it's a reasonable idea but I echo jck's concern that > test vectors can turn into de-facto standards, particularly when the tests > and the text turn out not to exactly match. > > On the other hand, is it valid for a DNS compression pointer to point forward > in the message? Why or why not? > > Regards, > John Levine, jo...@taugh.com, Taughannock Networks, Trumansburg NY > Please consider the environment before reading this e-mail. > https://urldefense.com/v3/__https://jl.ly__;!!GjvTz_vk!Fjf42blj0yV8IPVN81l1DX083zhJ6EyGrExCUwvu4ak3_8pUW9kQBitxYWlLWe8$ > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/dnsop__;!!GjvTz_vk!Fjf42blj0yV8IPVN81l1DX083zhJ6EyGrExCUwvu4ak3_8pUW9kQBitxSq3w_EQ$ > _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
