This was corrected a while ago (March 13th in the git repository). The –04 version that's now current has it right.
-MSK From: Tim Draegen <[email protected]<mailto:[email protected]>> Date: Thursday, April 3, 2014 9:09 AM To: Alexey Nezhdanov <[email protected]<mailto:[email protected]>> Cc: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [dmarc-discuss] An error in formal protocol definition (ABNF) Hi Alexey, You've found a recently-introduced bug. Unfortunately, the recent change to make the ABNF a bit more strict clashes with some left-over text "Tag and value matching is case-insensitive." at the end of section 5.3. This should be correctly ASAP, as it's not good. -= Tim On Apr 3, 2014, at 11:30 AM, Alexey Nezhdanov <[email protected]<mailto:[email protected]>> wrote: Hello. I am working on a web app that validates DMARC TXT records and noticed a possible error in formal spec: dmarc-version = %x76 *WSP "=" %x44.4d.41.52.43 I believe, it should be dmarc-version = %x76 *WSP "=" %x44.4d.41.52.43.31 i.e. it is 'v=DMARC' vs 'v=DMARC1' Also, it seems that the string is case-sensitive, but just to double check - is that really so? Best regards, Alexey Nezhdanov
_______________________________________________ dmarc-discuss mailing list [email protected] http://www.dmarc.org/mailman/listinfo/dmarc-discuss NOTE: Participating in this list means you agree to the DMARC Note Well terms (http://www.dmarc.org/note_well.html)
