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

[BIND 10 Development]

#600: NSEC3 hashed name shouldn't have base32 padding
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  UnAssigned
  jinmei                             |                Status:  new
                       Type:         |             Milestone:  New Tasks
  enhancement                        |            Resolution:
                   Priority:  minor  |             Sensitive:  0
                  Component:         |           Sub-Project:  DNS
  libdns++                           |  Estimated Difficulty:  0.0
                   Keywords:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by jinmei):

 * milestone:   => New Tasks


Comment:

 Actually we've solved this in the recent NSEC3 work (at least for the
 parser part;
 I suspect if we received wire-format hash data that would require padding,
 NSEC3::toText()
 will add padding - but in that case there would be no correct
 representation anyway).

 We are now (probably) the only implementation that does this correctly!

 Closing.

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