1 / 16

Overview of DKIM: System Design, Implementation, and Migration Considerations

This document provides a comprehensive overview of DomainKeys Identified Mail (DKIM), detailing its system-level service design, objectives, and constraints. It explores DKIM's integration into messaging services and its relationship with other IETF message signature technologies. Additionally, it outlines considerations for implementation and migration. The draft status is currently at "Draft-ietf-dkim-overview-04" and includes feedback from the working group. It discusses the future of the overview document and the potential separation of related content for timeliness and focus.

regina
Download Presentation

Overview of DKIM: System Design, Implementation, and Migration Considerations

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. DKIM Overview DocumentIETF 68 Tony Hansen Dave Crocker Phillip Hallam-Baker

  2. This document provides • An overview of DKIM • System-level service design • Goals, constraints, etc. • It describes • how it can fit into a messaging service • how it relates to other IETF message signature technologies • implementation considerations • migration considerations

  3. Status • Draft-ietf-dkim-overview-04 • A few content-related comments on the list • Mostly on focused specific items • Question from wg mailing list: • Publish now, with modified version later (when SSP completed) vs. • Publish later only

  4. A few issues to consider…

  5. It’s too %^&*& big! • But what about describing …

  6. Hmmm…

  7. We can use some of this stuff now! • It can all wait until later

  8. Hmmm…

  9. Don’t bother us with this right now • we want to focus on SSP • Charter • Nov 2007  WG last call on SSP protocol • Nov 2007  WG last call on overview document

  10. Hmmm…

  11. Note • The current Overview draft does not cover SSP well • It couldn’t

  12. Another view of Overview • Framework (with information on SSP) • Depends on –ssp-requirements (done soon) • Deployment Guide for –base • Depends on -base • Deployment Guide for –ssp • Planned for, but not yet written • Depends on –ssp-design

  13. An Idea • Split the doc up • Along those three lines • Publish the pieces as they become useful • Now that –base is done • publish the base deployment guide asap • When ssp-requirements is done • Publish the framework • When ssp-design is done • Publish the ssp deployment guide

  14. Advantages • Pieces would be more focused • Pieces can be more timely • Spread out the impact of other WG work • Pieces would be more useful

  15. Impact • Tweaks the milestone list in the charter

  16. Q&A • Send your cards and letters!

More Related