-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In message <CAH48ZfzzqFRP0UC0Ynh12aYat_StEn=Nhf7bDJyxD5TToDc- g...@mail.gmail.com>, Douglas Foster <dougfoster.emailstanda...@gmail.com> writes
>By contrast, the new tag cannot be effective until DMARCbis is published >and filtering software updated. This involves years. Hard to say ... there is some self-interest here in having shiny new features (such as they are) and it is argued that pretty much everyone uses one of a small number of libraries so only a small number of programmers need to stay up late to make updating possible Although people did not update software very often 20 years back, fear of compromises (and the widespread existence of such compromises) means that updating cycles are far faster than they used to be. >Even then, domain >owners will never have confidence that the new token support has been >implemented by all recipient evaluators. That of course was one of the reasons for having a version bump ... but there was no consensus for that. However, careful reading of reports will tell you whether those evaluators who send reports have updated, and you can take a view from those - -- richard Richard Clayton Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. Benjamin Franklin 11 Nov 1755 -----BEGIN PGP SIGNATURE----- Version: PGPsdk version 1.7.1 iQA/AwUBZT8VyN2nQQHFxEViEQI4KwCgoq/AfjOOaln5Gz+lGTdC1w2jHG8AoNvY ojMIxIPArJ94MmA8MhS1tJ0Z =bOmC -----END PGP SIGNATURE----- _______________________________________________ dmarc mailing list dmarc@ietf.org https://www.ietf.org/mailman/listinfo/dmarc
