BIND 10 #600: NSEC3 hashed name shouldn't have base32 padding

[BIND 10 Development]

#600: NSEC3 hashed name shouldn't have base32 padding
-------------------------------------+-------------------------------------
           Reporter:  jinmei         |                      Owner:
               Type:  enhancement    |  UnAssigned
           Priority:  minor          |                     Status:  new
          Component:  DNSPacket API  |                  Milestone:  A-Team-
          Sensitive:  0              |  Task-Backlog
Add Hours to Ticket:  0              |                   Keywords:
        Total Hours:  0              |  Estimated Number of Hours:  0
                                     |                  Billable?:  1
                                     |                  Internal?:  0
-------------------------------------+-------------------------------------
 According to RFC5155, the hashed owner name of NSEC3 RRs shouldn't have
 trailing padding.

 We currently don't strictly follow that spec (but no other implementations
 seem to be correct in that sense, either).

 This problem isn't realized with SHA-1 hashes, so it's quite minor.
 Still, as a reference implementation it would be nicer to do it
 explicitly.

-- 
Ticket URL: <http://bind10.isc.org/ticket/600>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development