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:                      
     Type:  defect  |       Status:  new                 
 Priority:  major   |    Milestone:  feature backlog item
Component:  xfrout  |   Resolution:                      
 Keywords:          |    Sensitive:  0                   
--------------------+-------------------------------------------------------

Comment(by jinmei):

 Replying to [comment:1 zhanglikun]:
 > Is there one RFC talking about case-sensitive compress mode. I have read
 RFC4343, and didn't find the word "MUST" to the use of case-sensitive
 compress mode for AXFR, or it's suggested in "DNS Zone Transfer Protocol
 (AXFR) draft-ietf-dnsext-axfr-clarify-14"?

 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).

 p.s. when you work on it, please don't forget writing tests first:-)

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