On Thu, Jun 26, 2014 at 10:26 AM, Jim Fenton <fen...@bluepopcorn.net> wrote:
> > The base specification relies on the ability of an email receiver to > > determine the organizational domain responsible for sending mail. An > > organizational domain is the basic domain name obtained through a public > > registry, such as example.com or example.co.uk. While the common > > practice is to use a "public suffix" list to determine organizational > > domain, it is widely recognized that this solution will not scale, and > > that the current list often is inaccurate. The task of defining a > > standard mechanism for identifying organizational domain is out of scope > > for this working group. However the working group can consider extending > > the base DMARC specification to accommodate such a standard, should it > > be developed during the life of this working group. > > I don't see how this can be considered out of scope without a viable > alternative. The identification of the Administrative Domain is a > normative requirement in DMARC, and if this problem is not solved, the > specification will be stuck. Having tried and failed to solve this > problem several years ago, I am convinced that this is a very difficult > problem. > I think this is the right way to go because (a) the task at hand is big enough as it is without taking on this as well, especially since (b) the question of identifying the Organizational Domain (to use DMARC's term) has appeared in several other contexts as well, and was the subject of a BoF in London (look up "dbound"), so if that work is going to be done elsewhere, we don't need to also do it here. -MSK
_______________________________________________ dmarc mailing list dmarc@ietf.org https://www.ietf.org/mailman/listinfo/dmarc
