BIND 10 #253: xfrout should use the case-sensitive compress mode.

[BIND 10 Development]

#253: xfrout should use the case-sensitive compress mode.
-------------------------------------+-------------------------------------
                 Reporter:  jinmei   |                Owner:  zzchen_pku
                     Type:  defect   |               Status:  assigned
                 Priority:  minor    |            Milestone:  A-Team-
                Component:  xfrout   |  Sprint-20110223
                 Keywords:           |           Resolution:
Estimated Number of Hours:  0.0      |            Sensitive:  0
                Billable?:  0        |  Add Hours to Ticket:
                Internal?:  0        |          Total Hours:
-------------------------------------+-------------------------------------

Comment (by zzchen_pku):

 Replying to [comment:2 jinmei]:
 > It's in axfr-clarify:
 >
 > {{{
 >    Hence, name compression in an AXFR message SHOULD be performed in a
 >    case-preserving manner, unlike how it is done for 'normal' DNS
 >    responses.  That is, although when comparing a domain name for
 > }}}
 > (in 3.4.  Name Compression)
 >
 > but my understanding is that this is a "clarification" document, and
 just reflects the common understanding of the original spec
 (RFC1034/1035).
 Now we have rfc5936 for reference:-)

-- 
Ticket URL: <https://bind10.isc.org/ticket/253#comment:5>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development