I proposed adding this right above "Work Items" (it accomplishes the same thing):
4. Incidental related work Any issues related to the email authentication space that are large enough to mandate working group review but do not already fit under the charter of an existing working group can be considered for adoption by DMARC. A prime example is draft-levine-appsarea-eaiauth, which provides EAI-related updates to DMARC and the protocols upon which it depends. On Mon, Nov 5, 2018 at 1:03 PM Barry Leiba <[email protected]> wrote: > I was about to propose something very similar, so I'm happy to go with > Kurt's text. Alexey, do you think this will work? > > DMARC working group, are you OK with that addition to the charter? > Any objections? > > Barry > On Mon, Nov 5, 2018 at 10:01 AM Kurt Andersen (b) <[email protected]> > wrote: > > > > I think that we could possibly already read this into the existing > charter, but the following one sentence patch makes it explicit: > > > > diff --git a/dmarc-wg-charter b/dmarc-wg-charter > > index a1d0fac..c8ac6bc 100644 > > --- a/dmarc-wg-charter > > +++ b/dmarc-wg-charter > > @@ -81,6 +81,9 @@ 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. > > > > +Clarifying the handling of internationalized email addresses (EAI) > > +throughout the authentication stack of SPF, DKIM, and DMARC. > > + > > Improvements in DMARC features (identifier alignment, reporting, > > policy preferences) will be considered, such as: > > > > --Kurt > > > > -- > Barry > -- > Barry Leiba ([email protected]) > http://internetmessagingtechnology.org/ >
_______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
