Re: [ietf-dkim] DKIM and EAI

2018-02-09 Thread Murray S. Kucherawy 
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
> A-R specs.
>

Since 7601bis is now a live DMARC WG document, you might want to make some
suggestions over there since 7601 will be obsoleted.

-MSK
___
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html

Re: [ietf-dkim] DKIM and EAI

2018-02-09 Thread John Levine 
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: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html

Re: [ietf-dkim] DKIM and EAI

2018-02-09 Thread Scott Kitterman 
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 you try to expand a UTF-8 local part, it doesn't
> match anything.  I figure this is consistent with what would happen if
> your local part was something like foo..bar which won't match anything
> either.
> 
> I would appreciate if people would take a look and see if anything seems
> obviously wrong.  I'm doing some EAI whitepapery things for ICANN and it
> would be nice if, for a change, the advice they offer matches reality.

Thanks.  I think that's a reasonable resolution of the SPF macro issue that I 
raised.  Not ideal, in theory, but plenty good enough for the corner case it 
is.

Does this need to update RFC 7208 since there are SPF related MUST 
requirements?

Scott K
___
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html

Re: [ietf-dkim] DKIM and EAI

2018-02-09 Thread John R. Levine 

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 figure this is consistent with what would happen if 
your local part was something like foo..bar which won't match anything 
either.


I would appreciate if people would take a look and see if anything seems 
obviously wrong.  I'm doing some EAI whitepapery things for ICANN and it 
would be nice if, for a change, the advice they offer matches reality.


Regards,
John Levine, jo...@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly
___
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html

Re: [ietf-dkim] DKIM and EAI

2017-12-06 Thread Hector Santos 

+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 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 decisions about what's in
ASCII (a-labels) or what's in UTF-8 (u-labels.)  I did a draft about
it last year:

 https://datatracker.ietf.org/doc/draft-levine-appsarea-eaiauth/

It would be nice if this could be finished and published, so I have
something better than an expired draft to point at when people ask me
how to do DKIM and SPF with their EAI mail.



--
HLS


___
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html

Re: [ietf-dkim] DKIM and EAI

2016-10-02 Thread John R. Levine 

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 through DISPATCH.


Regards,
John Levine, jo...@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly
___
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html

Re: [ietf-dkim] DKIM and EAI

2016-10-01 Thread Murray S. Kucherawy 
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 document/work forward.
>

Which working group?  DKIM hasn't existed in years.  We'd have to spin up
another one.

-MSK
___
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html

Re: [ietf-dkim] DKIM and EAI

2016-09-27 Thread Jiankang Yao 


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 document/work forward.

Best Regards



Jiankang Yao

From: John R. Levine
Date: 2016-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 it, but I can't say it's gotten a lot of attention 
other than from Alexey:

https://datatracker.ietf.org/doc/draft-levine-appsarea-eaiauth/

Regards,
John Levine, jo...@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly
___
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html___
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html