Eliot,
Your proposal would satisfy me (as an implementor, anyway) in terms of the
opacity of the local-part value in "i=".
What it doesn't do is address the question about whether or not RFC4871
presents a single identity as its output, and if so, which one that is.
Or, alternately, perhaps you're suggesting that's not an issue that really
needs to be solved? (That's not sarcastic; I don't have experience yet to
suggest this is a fire that needs to be put out, so I'm genuinely
wondering.)
-MSK
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html