On Tue 28/Jun/2016 17:13:58 +0200 Kurt Andersen wrote:
[email protected] <mailto:[email protected]> since the protocol has been adopted
there...
-ARC Discussion <[email protected]> to reduce cross-posting...
On Sat, Jun 25, 2016 at 11:27 PM, Murray S. Kucherawy <[email protected]
<mailto:[email protected]>> wrote:
The section defining AAR doesn't actually say that it's "i=N;" (with the
semi-colon). It should. Note though that the rest of that header field
is not pure tag=value syntax.
So here's a bit of hand grenade: You could separate the AAR parts from
the AR parts by doing something like:
ARC-Authentication-Results: i=1;
ar=<base64-or-qp-encoded-copy-of-AR-you-want-to-preserve>
That makes AAR into a purely tag=value syntax. If there's no need for
any part of ARC to care what the preserved thing is, this seems mighty
clean.
I'm OK with this sort of strategy. Presumably the ar tag value would be
canonicalized before encoding?
What's wrong with something readable? E.g.:
arc-authres-header = "ARC-Authentication-Results:" [CFWS] arc-instance
[ CFWS] authserv-id
[ CFWS authres-version ]
( no-result / 1*resinfo ) [CFWS] CRLF
arc-instance = %x69 [FWS] "=" [FWS] 1*3DIGIT ";"
; i=N;
Ale
--
_______________________________________________
dmarc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmarc
