[Net-sec-threat-modeling] Reserve slot during the next F2F meeting

[Mariusz Kondratowicz]

I agree. 20-30 minutes is enough.

We can split it:
5  minutes - review of Survey (BTW, any news about questionnaire? Any
chance for more answers?)
10 minutes - methodology
10 minutes - state of work
5 minutes - Questions

What do you think?

Regards,
Mariusz

*Mariusz Kondratowicz | Compliance Manager*
Opera Software AS



On Thu, May 23, 2019 at 4:58 PM Neil Dunbar <ndunbar at trustcorsystems.com>
wrote:

> I would have thought that 30 minutes is plenty time.
>
> And yes, we can break out if there is a need to get any other work in.
>
> Neil
>
> > On 23 May 2019, at 15:55, Fotis Loukos <fotisl at ssl.com> wrote:
> >
> > Hello everybody,
> > after discussing with Ben and Dimitris, we are able to reserve a slot
> > for the threat modeling subgroup during the next F2F meeting.
> > For all of you who have not attended a F2F meeting before, during that
> > time slot we will be able to present some of our work to the whole CA/B
> > Forum, accept questions, and maybe try to get some people to help us. In
> > general, we do not do any hands-on work.
> > How much time do you think we are going to need? I believe that 20-30
> > mins should be ok, and we can have private meetings if we need to do any
> > hands-on work.
> >
> > Regards,
> > Fotis
> >
> > --
> > Fotis Loukos, PhD
> > Director of Security Architecture
> > SSL Corp
> > e: fotisl at ssl.com
> > w: https://www.ssl.com
> > _______________________________________________
> > Net-sec-threat-modeling mailing list
> > Net-sec-threat-modeling at cabforum.org
> > http://cabforum.org/mailman/listinfo/net-sec-threat-modeling
>
> _______________________________________________
> Net-sec-threat-modeling mailing list
> Net-sec-threat-modeling at cabforum.org
> http://cabforum.org/mailman/listinfo/net-sec-threat-modeling
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cabforum.org/pipermail/net-sec-threat-modeling/attachments/20190523/e62e1bc7/attachment.html>