+1
On Thu, Apr 6, 2023 at 9:19 AM Mickey Chandler wrote:
> +1 from me as well.
>
> On Tue, Apr 4, 2023 at 10:50 AM Laura Atkins
> wrote:
> >
> > I want to thank everyone for their patience as I learn IETF processes
> and tools. Tim and I are working on a statement for the group from us as
> cha
+1 on adoption of Wei's latest draft.
On Thu, Apr 6, 2023 at 9:19 AM Mickey Chandler wrote:
> +1 from me as well.
>
> On Tue, Apr 4, 2023 at 10:50 AM Laura Atkins
> wrote:
> >
> > I want to thank everyone for their patience as I learn IETF processes
> and tools. Tim and I are working on a state
+1 from me as well.
On Tue, Apr 4, 2023 at 10:50 AM Laura Atkins wrote:
>
> I want to thank everyone for their patience as I learn IETF processes and
> tools. Tim and I are working on a statement for the group from us as chairs.
> While we’re doing that, though, I would like to get the group m
+1 for adoption of the current draft problem statement
--
Tom Perrine
tom.perr...@servicenow.com
___
Ietf-dkim mailing list
Ietf-dkim@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-dkim
On Tuesday, April 4, 2023 12:52:51 PM EDT Michael Thomas wrote:
> While a good start, this document is far too vague about what the
> current state of the problem actually is for those who of us who are not
> part of industry groups privy to more information.
To this specific point, I think any la
Add me as another +1 (though I'm a co-author on the doc so that can be assumed
I guess, maybe)
Bron.
On Wed, Apr 5, 2023, at 01:49, Laura Atkins wrote:
> I want to thank everyone for their patience as I learn IETF processes and
> tools. Tim and I are working on a statement for the group from us
