On 7/8/2017 11:24 AM, Murray S. Kucherawy wrote:
There's interest verging on anxiety to get this deployed, and thus there are both private and public implementations of it that are relatively stable (modulo some open questions about the draft content). It won't be long before we're able to gather efficacy details based on live operation, even if the draft hasn't been given an RFC number yet.
I think the document can introduce itself better and give a more helpful conceptual framework at the start. But that's not a comment on the technical details. While it's possible that there is some interesting technical deficiency lurking there, I'm not especially worried about that.
Rather...
But you're right, there's some new stuff here, and strange side effects could take a while to manifest, or it could take us a while to figure
It's these sorts of issues. I'm reacting from intuition here, not a specific bit of insight or concern. Just a general feeling that the operational dynamics of this require some breadth of experience.
out how to deal with them when they appear. So if it's more important to get an RFC published than it is to wait for some modicum of deployed maturity -- which will take months, at least, I would guess -- then Experimental is indeed something we should consider, and I also agree with Andrew that the experiment should be reasonably well described and bounded.
If I thought that bench-testing would suffice, then I'd suggest doing it and holding the RFC until we get the results. But I think the question of dynamics and operations is more complex and requires some breadth of deployment experience to resolve. (Even if 'resolve' means a solid 'no problems' comeback rather than any interesting statements about nuance or implication.)
On the matter of a goal for the experiment I'll repeat that I think we merely need to target development of a Deployment and Use BCP. When we have good community support for the contents of such a document, based on significant experience, then the spec will be ready for standards track.
(The formal rules for Proposed do not require field experience or even implementation. Except sometimes. And there's no clear rule about when it's required. My own sense of the rule is "when we don't adequately understand how it will work in the real world and especially when problems could have an infrastructure effect." I see this as one of those cases.)
d/ d/ -- Dave Crocker Brandenburg InternetWorking bbiw.net _______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
