BIND 10 #1438: NSEC3: consistent selection of NSEC3PARAM

[BIND 10 Development]

#1438: NSEC3: consistent selection of NSEC3PARAM
-------------------------------------+-------------------------------------
            Reporter:  stephen       |                        Owner:
                Type:  enhancement   |                       Status:  new
            Priority:  major         |                    Milestone:  New
           Component:  Unclassified  |  Tasks
           Sensitive:  0             |                     Keywords:
         Sub-Project:  DNS           |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 Consistent selection of NSEC3PARAM record for use in all subsequent NSEC3
 code. [http://tools.ietf.org/html/rfc5155 RFC 5155] does not prohibit
 multiple NSEC3PARAM RRs at the apex of the zone and leaves flexibility in
 which one is used.  The purpose of this ticket is to review the NSEC3 code
 and to ensure if multiple NSEC3PARAM records are present, the parameters
 of the same record are used throughout one query. (See
 [http://tools.ietf.org/html/rfc5155#section-7.3 RFC 5155 section 7.3].)

 This relies on the completion of tickets #1431 through #1437.

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