keyword_arc-protocol_wordsmithingowner:draft-ietf-dmarc-arc-protocol@ietf.orgresolution_fixedtype_enhancement | by kboth+ietf@drkurt.com
Copied from -11:
Seth: replace with “ARC MUST be the last signer of the message; otherwise it cannot be validated on receipt.” in the signer actions section.
Kurt: Concern that this still does not address the risk of DKIM-Signatures covering ARC chains. This does not seem like it fits in this section but it needs to go somewhere. ]]
Statement in contention:
DKIM-Signatures SHOULD never sign any ARC header fields.
Kurt: Response to Dave’s concern (in mailing list): If DKIM covers ARC and ARC covers DKIM, which comes first? The chicken or the egg? I’m open to alternate ways to phrase this without opening the “modifying the DKIM spec” can of worms.
Issue migrated from trac:14 at 2022-01-24 16:14:25 +0000
keyword_arc-protocol_wordsmithing
owner:draft-ietf-dmarc-arc-protocol@ietf.org
resolution_fixed
type_enhancement
| by kboth+ietf@drkurt.comCopied from -11:
Seth: replace with “ARC MUST be the last signer of the message; otherwise it cannot be validated on receipt.” in the signer actions section.
Kurt: Concern that this still does not address the risk of DKIM-Signatures covering ARC chains. This does not seem like it fits in this section but it needs to go somewhere. ]]
Statement in contention: DKIM-Signatures SHOULD never sign any ARC header fields.
Kurt: Response to Dave’s concern (in mailing list): If DKIM covers ARC and ARC covers DKIM, which comes first? The chicken or the egg? I’m open to alternate ways to phrase this without opening the “modifying the DKIM spec” can of worms.
Issue migrated from trac:14 at 2022-01-24 16:14:25 +0000