----- Original Message -----
From: "John Levine" johnl(_at_)iecc(_dot_)com
I have to agree with Mike (alert the media!) that key
management belongs in a BCP, not in the spec.
Could there be a generalize "BCP" that can be part of a DKIM-BASE and covers
a basic methodology? I would like to see atleast a "summary" in the
DKIM-BASE since it is a very important consideration to help the adoption
process.
Maybe a section that consolidates all the thoughts mentioned throughout the
DKIM-BASE document, including hindsights about possible implementation
considerations would help. Here is a basic outline. Maybe it can serve as
input for some administrator to write this BCP.
Extracted from Current Proposal
x.0) Key Retention and Rollover Stategies
x.1) Selectors/Keys
a) One key per selector (section 3.1)
x.2) Key Revocation
a) Concurrent selectors during transition (section 3.1)
b) Minimum seven (7) day (section 5.2)
c) Empty p= data for revocation (section 3.6.1)
x.3) Signature Expiration
a) No x= tag, no expiration (section 3.6.1)
b) Expiration promotes invalid signature (section 3.6.1)
c) No verification required (not implicitly stated)
x.4) Explicit Classification Statements
a) Expiration forces invalid signature. (section 3.6.1)
b) Key Revocation forces failed verification. (section 6.2)
Implicitly and Explicitly Extracted Problems/Objectives
x.5) Security needs to revoke keys
a) for invalidating signature.
b) (NOT?) for message expirations.
c) without losing original validity.
d) without removing domain responsibility.
e) without destroying domain reputation.
x.6) Time-shifted Verifications Issues
a) Abnormal Transport Delivery Times
b) Post Transport, Delay Verification
c) Offline MUAs
--
Hector Santos, Santronics Software, Inc.
http://www.santronics.com
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html