The IETF have no control over how third parties choose to implement RFCs. If a vendor chooses not to implement a particular RFC because of its status, and that choice results in an interoperability issue, then that discussion is between the vendor and their customers - the IETF have no part to play in that conversation.
My personal opinion would be that Barracuda will choose to implement ARC long before it gets on the standards track simple because of the market force of their customers demanding it. I suspect that they are not the only filter vendor who needs to revaluate implementing ARC in light of Microsoft's decision. The ARC WG may be a better place to ask about the development status of the protocol - https://www.ietf.org/mailman/listinfo/arc Ken. From: dmarc <dmarc-boun...@ietf.org> On Behalf Of Andreas Niedermann Sent: Friday 29 July 2022 10:40 To: dmarc@ietf.org Subject: [dmarc-ietf] rfc8617 Hi there My question is at which time rfc8617 will move from the experimental cathegory... Microsoft uses ARC and many customers moved to Office365. They interact with outbound.protection.outlook.com. Many messages from this source are modified and break even relaxed/relaxed DKIM cannonication. Thus email from this domain is blocked and cannot reach our customers. We use barracuda filters and wanted to request DMARC and ARC features. Barracuda tells us that they're not implementing because of the experimental status. Weird... it's in state experimental and all giants like Microsoft and Google are using it... Do you have some explaination? Freundliche Grüsse Andreas Niedermann Armacom AG Muttenzerstrasse 107 4133 Pratteln Mail: andreas.niederm...@armacom.ch<mailto:andreas.niederm...@armacom.ch>
_______________________________________________ dmarc mailing list dmarc@ietf.org https://www.ietf.org/mailman/listinfo/dmarc
