BIND 10 #2124: RFC 6594 for SSHFP

[BIND 10 Development]

#2124: RFC 6594 for SSHFP
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  UnAssigned
  vorner                             |                Status:  new
                       Type:         |             Milestone:  Next-Sprint-
  defect                             |  Proposed
                   Priority:         |            Resolution:
  medium                             |             Sensitive:  0
                  Component:         |           Sub-Project:  DNS
  libdns++                           |  Estimated Difficulty:  0
                   Keywords:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by shane):

 Replying to [comment:2 vorner]:
 > What do you mean, by ignore? Reject, or accept?
 >
 > The (frustrating) problem I see is, because the code doesn't know the
 type exists, it rejects it. But if the check is just removed, everything
 works fine. I'm OK with allowing just the known ones, but once there's a
 new type, we'll need to extend the check again so the type accepts a valid
 key it is able to handle, just unwilling. I kind of don't see the
 advantage of having the check.

 I meant accept.

 Basically, if we know about a given type, then we can check it, if we
 don't we just assume that it is correct.

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