1 / 11

DNSEXT-63 Next steps in Trust Anchor Management for DNSSEC

DNSEXT-63 Next steps in Trust Anchor Management for DNSSEC. Ólafur Guðmundsson ogud @ogud.com. Current Status . 2 drafts: Threshold n out of m Timers IPR claim filed against both drafts Patent is issued in Israel License terms Royalty free

parley
Download Presentation

DNSEXT-63 Next steps in Trust Anchor Management for DNSSEC

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DNSEXT-63 Next steps in Trust Anchor Management for DNSSEC Ólafur Guðmundsson ogud@ogud.com

  2. Current Status • 2 drafts: • Threshold n out of m • Timers • IPR claim filed against both drafts • Patent is issued in Israel • License terms • Royalty free • Clause about references causes problems for some implementers • IPR holder wants to update IPR statement with new terms but not posted yet

  3. Larger picture • Lack of DNSSEC KEY management is may soon become the excuse “de Jour” for not doing DNSSEC • Large TLD’s will not deploy DNSSEC any time soon without a market. • In early deployment “configured” trust anchors will be the rule • The need for configured trust anchors may never go away

  4. Next steps: • WG needs to get more active on this issue or DROP IT completely • WG owes the proposals: • DISCUSSION • FEEDBACK • Selection criteria • Timeline

  5. “.” ORG COM DE IS UK SE IETF OGUD ISOC DENIC www OPS Why we need Trust Anchor Management (TAM) • Secure Entry Points • .SE enables all domains with DS to be trusted • Root will always need TAM. RFC PAF

  6. Trust Anchor: Timers • One optional protocol change • DNSKEY Revoke bit • Invalidates DS/DNSKEY fast, this is a revocation schema for DNSSEC • “immediately” is within the traditional DNS sense of: • zone update propagation delay + TTL

  7. Resolver Trust Anchor State Machine NB: Differs slightly from ID version!

  8. Trust Anchors: n out of m • Larger DNSKEY set required

  9. The state machine

  10. Open Mike • Comments on proposals • Comments

  11. Next Step • Advance • One • Both • Neither • Take discussion to mailing list

More Related