On Sat, Dec 31, 2022 at 4:18 PM Michael Thomas wrote:
>
> On 12/31/22 2:37 PM, Murray S. Kucherawy wrote:
>
> On Sat, Dec 31, 2022 at 1:09 PM Michael Thomas wrote:
>
>>
>> On 12/29/22 7:20 PM, Murray S. Kucherawy wrote:
>>
>> On Sun, Dec 25, 2022 at 4:14 PM Michael Thomas wrote:
>>
>>>
>>>
>>>
On 12/31/22 2:37 PM, Murray S. Kucherawy wrote:
On Sat, Dec 31, 2022 at 1:09 PM Michael Thomas wrote:
On 12/29/22 7:20 PM, Murray S. Kucherawy wrote:
On Sun, Dec 25, 2022 at 4:14 PM Michael Thomas wrote:
Done, and thanks for that text.
One nit, Barry's text sho
On 12/31/2022 3:02 PM, Murray S. Kucherawy wrote:
If we think this constraint is appropriate, I'm fine to include it.
Does someone want to propose a sentence or two? I need to avoid
getting my wrist slapped for both championing the charter and writing it.
Murray,
Sorry but I don't know what
On Sat, Dec 31, 2022 at 2:43 PM Dave Crocker wrote:
> The initial effort to form a working group in the IETF was pretty casual
> and surfaced a lack of sufficient consensus among advocates. The IETF
> said go away until there's more agreement.
>
> We went away for a year, during which we develop
On 12/31/2022 2:37 PM, Murray S. Kucherawy wrote:
I take as evidence of this the fact that the first incarnation of the
DKIM working group knew itself well enough to completely avoid the
topic of user interfaces, for example.
The initial effort to form a working group in the IETF was pretty ca
On Sat, Dec 31, 2022 at 1:09 PM Michael Thomas wrote:
>
> On 12/29/22 7:20 PM, Murray S. Kucherawy wrote:
>
> On Sun, Dec 25, 2022 at 4:14 PM Michael Thomas wrote:
>
>>
>>
>> Done, and thanks for that text.
>>
>> One nit, Barry's text should be above the proposals not below. It makes
>> it look
On 12/29/22 7:20 PM, Murray S. Kucherawy wrote:
On Sun, Dec 25, 2022 at 4:14 PM Michael Thomas wrote:
Done, and thanks for that text.
One nit, Barry's text should be above the proposals not below. It
makes it look like those are the only proposals on the table which
I'm ne
