thanks for review! proposed diff attached.
> If the comments change, the signature changes?
yep. otherwise vast complexity lurks. but is there a text change you
want? i may be naïve expecting that "a digest of the main body of the
file" is sufficient.
> [a] the source of the geofeed cl
On Fri, Sep 11, 2020 at 1:48 PM Randy Bush wrote:
> would appreciate review prior to calling for wg adoption
>
> thanks
>
> randy
>
> A new version of I-D, draft-ymbk-opsawg-finding-geofeeds-02.txt
> has been successfully submitted by Randy Bush and posted to the
> IETF repository.
>
> Name:
would appreciate review prior to calling for wg adoption
thanks
randy
A new version of I-D, draft-ymbk-opsawg-finding-geofeeds-02.txt
has been successfully submitted by Randy Bush and posted to the
IETF repository.
Name: draft-ymbk-opsawg-finding-geofeeds
Revision: 02
Title:
Brilliant!
Welcome Henk! This is a great way to end the week.
Eliot
> On 11 Sep 2020, at 18:35, Rob Wilton (rwilton)
> wrote:
>
> Dear all,
>
> I am happy to announce that Henk Birkholz has agreed to serve as a third
> OPSAWG WG chair to help with the current workload and gain some chair
Hi Rob et al,
thanks for having me! I intend to move from being a burden to being a
help in the near future, of course. Thanks also to Joe and Tianran for
helping me to move from one side to the other :-)
Viele Grüße,
Henk
On 11.09.20 18:37, Joe Clarke (jclarke) wrote:
Welcome, Henk! It’s
Welcome, Henk! It’s great to have you onboard. I hope you’ll be able to join
us at the virtual 109 meeting for a proper introduction.
Joe
> On Sep 11, 2020, at 12:35, Rob Wilton (rwilton)
> wrote:
>
> Dear all,
>
> I am happy to announce that Henk Birkholz has agreed to serve as a third
>
Dear all,
I am happy to announce that Henk Birkholz has agreed to serve as a third OPSAWG
WG chair to help with the current workload and gain some chair experience.
Please welcome Henk to OPSAWG.
Kind regards,
Rob
___
OPSAWG mailing list
OPSAWG@iet
On Fri, 11 Sep 2020 at 16:11, Nick Lamb wrote:
> On Fri, 11 Sep 2020 12:32:03 +0530
> tirumal reddy wrote:
>
> > The MUD URL is encrypted and shared only with the authorized
> > components in the network. An attacker cannot read the MUD URL and
> > identify the IoT device. Otherwise, it provide
Hi Wei,
Thanks for the feedback. Please see inline
On Fri, 11 Sep 2020 at 09:43, Panwei (William)
wrote:
> Hi authors, all,
>
> I've read the draft and I support adoption. This draft is useful for the
> network element, e.g., firewalls, to identity and prevent the unintended
> usage of (D)TLS e
Hi Ben,
Please see inline
On Fri, 11 Sep 2020 at 07:05, Ben Schwartz wrote:
> Thanks for highlighting this, Michael. I don't support adoption of this
> draft, because I don't think it is fit-for-purpose. Specifically, I think
> it is likely to provide a significant advantage to malware author
10 matches
Mail list logo
