In article <[email protected]> you write: >-=-=-=-=-=- > >draft-ietf-dmarc-arc-protocol > >The production “arc-info” includes a semicolon after “instance”, which in turn >has a semicolon at the >end. However, a great number of Arc-Authentication-Results header fields I’ve >seen in practice include only >one semicolon between the instance and the “authres-payload”; for example: >“i=1; mx.example.com; …”. > >draft-ietf-dmarc-rfc7601bis
You're right, that's a bug in the ABNF. The definition of instance in section 3.6 shouldn't have a semicolon because both places it's used, arc-info and arc-as-info, put a semicolon after it. I suppose we could take the semicolon out of arc-info and arc-as-info instead. >I also want to report on another form of the Authentication-Results field that >I've seen in practice. It has the form: > > authserv from=domain; method=result (comment); from=domain; method=result > (comment) > >where "authserv" (from what I've seen) is a domain name that always ends in >"yahoo.com". Yeah, Yahoo implemented it wrong. I'll remind them when I see them at M3AAWG. R's, John _______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
