BIND 10 #2522: support generic version of rdata::createRdata(text) in RP, MINFO, TSIG RDATA

BIND 10 Development do-not-reply at isc.org
Fri May 17 23:46:53 UTC 2013


#2522: support generic version of rdata::createRdata(text) in RP, MINFO, TSIG
RDATA
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  task          |  jinmei
            Priority:  medium        |                       Status:
           Component:  libdns++      |  reviewing
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-20130528
         Sub-Project:  DNS           |                   Resolution:
Estimated Difficulty:  5             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  N/A
                                     |  Feature Depending on Ticket:
                                     |  loadzone-ng
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by pselkirk):

 * owner:  pselkirk => jinmei
 * estimatedhours:  4 => 5


Comment:

 Replying to [comment:11 jinmei]:

 Ready for re-review.

 As noted in comment 13, I added SSHFP to the ticket, so I added 1 point to
 the Estimated Difficulty.

 Here is the proposed changelog entry:

 {{{
 613.?   [func]          pselkirk
         libdns++: All Rdata classes now use the generic lexer in
         constructors from text.  This means that the name fields in such
         RRs in a zone file can now be non-absolute (the origin name in
 that
         context will be used), e.g., when loaded by b10-loadzone.  Note
         that the existing string constructors for these Rdata classes also
         use the generic lexer, and they now expect an absolute name (with
         the trailing '.') in the name fields.
 }}}

 Should this include all related tickets and commits, or just the ones not
 covered by prior changelog entries?

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


More information about the bind10-tickets mailing list