Re: [Ietf-dkim] Chartering update

2023-02-04 Thread Michael Thomas
On 2/4/23 11:40 AM, Murray S. Kucherawy wrote: On Sat, Feb 4, 2023 at 11:11 AM Michael Thomas wrote: There are architectural ramifications regardless of whether it's mandatory or not. It would be a lot more reassuring if this were a common and accepted practice. I don't know the

Re: [Ietf-dkim] Chartering update

2023-02-04 Thread Murray S. Kucherawy
On Sat, Feb 4, 2023 at 11:11 AM Michael Thomas wrote: > There are architectural ramifications regardless of whether it's mandatory > or not. It would be a lot more reassuring if this were a common and > accepted practice. I don't know the answer to that. If it's uncommon, there > needs to be

Re: [Ietf-dkim] Chartering update

2023-02-04 Thread Michael Thomas
On 2/4/23 12:38 AM, Murray S. Kucherawy wrote: On Thu, Feb 2, 2023 at 3:26 PM Michael Thomas wrote: I guess my concern is more along the lines of what solutions *aren't*. There are a bunch of drafts trying to tie the envelope to the email and I think there needs to be a meta

Re: [Ietf-dkim] Chartering update

2023-02-04 Thread Michael Thomas
On 2/4/23 11:02 AM, Evan Burke wrote: On Sat, Feb 4, 2023 at 10:15 AM Michael Thomas wrote: Marketing email probably does. Whether it's spam or not is often in the eye of the beholder. Having spent some time in the industry, I can tell you that a significant majority of marketing

Re: [Ietf-dkim] Chartering update

2023-02-04 Thread Evan Burke
On Sat, Feb 4, 2023 at 10:15 AM Michael Thomas wrote: > Marketing email probably does. Whether it's spam or not is often in the > eye of the beholder. > Having spent some time in the industry, I can tell you that a significant majority of marketing email service providers will deliver a unique

Re: [Ietf-dkim] Chartering update

2023-02-04 Thread Michael Thomas
On 2/4/23 9:20 AM, Evan Burke wrote: On Sat, Feb 4, 2023 at 8:47 AM Dave Crocker wrote: On 2/4/2023 8:41 AM, Scott Kitterman wrote: > I've yet to see a description of the problem that's distinguishable from a mailing list that preserves DKIM signatures. That seems like an

Re: [Ietf-dkim] Chartering update

2023-02-04 Thread Scott Kitterman
On February 4, 2023 5:20:27 PM UTC, Evan Burke wrote: >On Sat, Feb 4, 2023 at 8:47 AM Dave Crocker wrote: > >> On 2/4/2023 8:41 AM, Scott Kitterman wrote: >> > I've yet to see a description of the problem that's distinguishable from >> a mailing list that preserves DKIM signatures. >> >> That

Re: [Ietf-dkim] Chartering update

2023-02-04 Thread Evan Burke
On Sat, Feb 4, 2023 at 8:47 AM Dave Crocker wrote: > On 2/4/2023 8:41 AM, Scott Kitterman wrote: > > I've yet to see a description of the problem that's distinguishable from > a mailing list that preserves DKIM signatures. > > That seems like an especially healthy discussion to have. Focusing

Re: [Ietf-dkim] Chartering update

2023-02-04 Thread Dave Crocker
On 2/4/2023 8:41 AM, Scott Kitterman wrote: I've yet to see a description of the problem that's distinguishable from a mailing list that preserves DKIM signatures. That seems like an especially healthy discussion to have. Focusing on, and seeking convergence about, the nature of the

Re: [Ietf-dkim] Chartering update

2023-02-04 Thread Scott Kitterman
On February 4, 2023 8:38:46 AM UTC, "Murray S. Kucherawy" wrote: >On Thu, Feb 2, 2023 at 3:26 PM Michael Thomas wrote: > >> I guess my concern is more along the lines of what solutions *aren't*. >> There are a bunch of drafts trying to tie the envelope to the email and I >> think there needs

Re: [Ietf-dkim] Chartering update

2023-02-04 Thread Murray S. Kucherawy
On Thu, Feb 2, 2023 at 3:26 PM Michael Thomas wrote: > I guess my concern is more along the lines of what solutions *aren't*. > There are a bunch of drafts trying to tie the envelope to the email and I > think there needs to be a meta discussion of whether that is a good idea or > not in