On Aug 29, 2014, at 3:07 PM, Douglas Otis <[email protected]> wrote: > The charter statement indicates work on a public suffix concept is > out-of-scope. This is fine provided the definition used in the charter is > retained: [snip] > Such policy assertions should be a matter handled within the WG as related > to organizational domain policy.
Hi Doug. I'm not Pete but you're writing about the charter's scope and so I'll jump in. Simply put, the public suffix concept is useful beyond what DMARC requires of it. The best that DMARC can do (as a piece of technology) is fully articulate 1 specific use case for the public suffix concept, and hope that other use cases get fleshed out enough so that a viable solution can be crafted by something other than this WG. The closest DMARC comes to discussing policy assertions between organizational domain policy and "everything below the organization" shows up in 1) the DMARC record discovery mechanism (that is, look at direct domain first and if nothing is there then look for a record at the "organizational domain") and 2) the DMARC options of "p=" and "sp=". How number 1 and 2 are used in operation -- as it's not exactly clear to the casual reader -- can be captured and explored in the operational-facing Usage Guide document. I hope this describes how the WG will tackle what you've brought up. =- Tim
_______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
