Case-Insensitive Response Compression May Cause Problems With Mixed-Case Data and Non-Conforming Clients
dot at dotat.at
Mon Feb 10 16:25:01 UTC 2014
Paul Vixie <paul at redbarn.org> wrote:
> Tony Finch wrote:
> > ...
> > If you later create positive cache entries under these labels (by asking
> > for SRV) you get the first answer back with canonical case (because it is
> > copied from the authoritative answer) but subsequent answers from the
> > cache use the same case as the negative cache entry.
> i recommend that this be solved with a 2181-bis that adds label
> credibility to its section 5.4.1.
Another thing I wonder about is what happens on authority servers with
zones like below. But I gather Mark already has some possible solutions in
silly.example A 127.0.0.1
SILLY.EXAMPLE AAAAA ::1
But making this much effort to preserve case seems contrary to RFC 4343.
f.anthony.n.finch <dot at dotat.at> http://dotat.at/
Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
Rough, becoming slight or moderate. Showers, rain at first. Moderate or good,
occasionally poor at first.
More information about the bind-workers