BIND 10 #781: Define cryptographic API

[BIND 10 Development]

#781: Define cryptographic API
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jinmei
  stephen                            |                Status:  reviewing
                       Type:  task   |             Milestone:
                   Priority:         |  Sprint-20110503
  blocker                            |            Resolution:
                  Component:         |             Sensitive:  0
  Unclassified                       |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  6.0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 And finally, about the "-y" portability.

 My suggestion is to pick up either dig or drill format and complete this
 branch, and open a new ticket to add support for the other format.

 Technically, there's an unsolvable ambiguity, but in practice it
 should be able to detect which format is used run time.  It will make
 the code a bit more complicated, but if it helps attract both dig and
 drill users that would be worth introducing.  In any case, I think it
 doesn't have to be implemented right now.

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