On Fri, Feb 9, 2018 at 3:22 PM, John Levine wrote:
> In article <1707398.kN3rUcK64s@kitterma-e6430> you write:
> >Does this need to update RFC 7208 since there are SPF related MUST
> >requirements?
>
> I would think so, also 6376, 7489, 7601 since it updates DKIM, DMARC, and
>
In article <1707398.kN3rUcK64s@kitterma-e6430> you write:
>Does this need to update RFC 7208 since there are SPF related MUST
>requirements?
I would think so, also 6376, 7489, 7601 since it updates DKIM, DMARC, and A-R
specs.
R's,
John
___
NOTE WELL:
On Friday, February 09, 2018 05:02:00 PM John R. Levine wrote:
> > If I may once again change the topic for a moment ...
> >
> > https://datatracker.ietf.org/doc/draft-levine-appsarea-eaiauth/
>
> I pushed out a new version that says something about SPF macros,
> attempting to say that if
If I may once again change the topic for a moment ...
https://datatracker.ietf.org/doc/draft-levine-appsarea-eaiauth/
I pushed out a new version that says something about SPF macros,
attempting to say that if you try to expand a UTF-8 local part, it doesn't
match anything. I
+1.
I think there are parsing issues to be highlighted. Do you decode
first, then extract the Author Domain or extract first before
decoding? etc.
On 12/5/2017 10:27 PM, John R. Levine wrote:
If I may change the topic for a moment ...
I'm working on some stuff for ICANN to help people
If I may change the topic for a moment ...
I'm working on some stuff for ICANN to help people get EAI mail working.
One of the underspecified bits of EAI is how authentication works with
SPF, DKIM, DMARC and now, I suppose ARC. There's a bunch of places where
one needs to make arbitrary
In order to make EAI environment more friendly, I suggest that this WG
considers to move this document/work forward.
Which working group? DKIM hasn't existed in years. We'd have to spin up
another one.
It's one fairly short and I hope uncontroversial draft, so I'd suggest
running it
On Tue, Sep 27, 2016 at 8:15 PM, Jiankang Yao wrote:
> Since EAI deployment is on the way, gmail, outlok2016, postfix, yandex,
> xgenplus and many more have adopted EAI.
> In order to make EAI environment more friendly, I suggest that this WG
> considers to move this
-09-28 01:45
To: Juan Altmayer Pizzorno
CC: ietf-dkim@mipassoc.org
Subject: [ietf-dkim] DKIM and EAI
> On a bit of a side note, I wonder how much appetite there
> is for a document update? Besides this, we have no way to
> include non-ASCII UTF-8 local parts in i=.
I wrote a draft about
On a bit of a side note, I wonder how much appetite there
is for a document update? Besides this, we have no way to
include non-ASCII UTF-8 local parts in i=.
I wrote a draft about it, but I can't say it's gotten a lot of attention
other than from Alexey:
10 matches
Mail list logo