This is a discussion on Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding - DNS ; -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Paul Vixie wrote: |> some mention of name case preservation, and how label compression can make a |> mess of this. | since we seem to agree that copying the question is what everybody ...
-----BEGIN PGP SIGNED MESSAGE-----
Paul Vixie wrote:
|> some mention of name case preservation, and how label compression can
|> mess of this.
| since we seem to agree that copying the question is what everybody
| what everybody should keep doing and what should be clarified in the spec,
| then you appear to be arguing that responses ought not use this copied
| question as a compression pointer target. sounds fine to me, if i'm
| you correctly. perhaps an "unless it would lead to truncation that
| occur if the question section copied from the query were available as a
| compression pointer target" exemption, though in an increasingly EDNS0
| i'm not sure we need to worry much about this as much.
| if we uptake ed's suggestion (progress the responder-must-copy
| separately) then perhaps that draft would be a good place to recommend the
| no-question-pointers logic as well. (trying to conserver RFC numbers
I would be against no-question-pointers text. It is perfectly ok for a
(authority, cache) server to compress to the question section. The
server can determine if it wants to do so (and if that smashes case).
If you feel the need for text:
Please note that the copied query name can differ in upper and lower
case, and therefore its use as a compression target depends on the
servers choices regarding compression.
Advancing 'copy the question section into the reply bit-for-bit' is fine
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
to unsubscribe send a message to firstname.lastname@example.org with
the word 'unsubscribe' in a single line as the message text body.