Re: [104all] Further Clarification Re: IETF 104 Preliminary Agenda

Agreed…

There are number of options for side meetings which can be used and IETF could assist in organizing it.

For instance - to reserve rooms on Saturday-Sunday-Friday_afternoon_ for possible use for side meetings.

I agree that IETF time should be used for IETF mostly and any modifications in the schedule should lower number of conflicts between IETF WG meetings.

dol@

> 25 февр. 2019 г., в 18:29, Greg Mirsky <gregimirsky@gmail.com> написал(а):
> 
> Dear All,
> I'm disappointed to find that the number of conflicts for me at IETF-104 is as high as in Bangkok which was two times higher than at any meeting before. I'm stressed that I'll have to run from DetNet to BFD to deliver presentations on work being done, forget being able to follow the discussion adequately. If that's the new normal, then why to come to the meeting at all. 
> I strongly encourage IESG to let us use all available time for WG sessions and let attendees use their time for "corridor talks".
> 
> Regards,
> Greg
> 
> 
> 
> 
> On Fri, Feb 22, 2019 at 9:08 PM IETF Agenda <agenda@ietf.org <mailto:agenda@ietf.org>> wrote:
> Hi everyone,
> 
> Our message earlier today announcing the preliminary agenda [1] was missing some further context. As previously mentioned by Alissa after IETF 103 [2], the IESG wanted to continue the unstructured time experiment at IETF 104.
> 
> Wednesday's schedule has regular sessions until 13:20, unstructured time in the afternoon, and the plenary in the evening at 17:10. This leaves almost four hours of unstructured time for attendees to reserve for side meetings. During this period, there will also be one unique Technology Deep Dive session with the acronym WGTLGO [3].
> 
> Monday through Friday, we will have two rooms available for attendees to reserve for side meetings as usual. On Wednesday afternoon, we will have five rooms available for side meetings. Further details about how to sign up for these rooms will be announced shortly. 
> 
> Thanks,
> IETF Secretariat
> 
> 
> [1]  https://mailarchive.ietf.org/arch/msg/ietf-announce/_JeP2fQ7rHPosZWpNtpl8I_uL5U <https://mailarchive.ietf.org/arch/msg/ietf-announce/_JeP2fQ7rHPosZWpNtpl8I_uL5U>
> [2]  https://mailarchive.ietf.org/arch/msg/ietf-announce/H64AuTYhxsGqM1a8BfTkszCZyso <https://mailarchive.ietf.org/arch/msg/ietf-announce/H64AuTYhxsGqM1a8BfTkszCZyso>
> [3]  https://www.ietf.org/blog/ietf104-bofs/ <https://www.ietf.org/blog/ietf104-bofs/>
> 
> -- 
> 104all mailing list
> 104all@ietf.org <mailto:104all@ietf.org>
> https://www.ietf.org/mailman/listinfo/104all <https://www.ietf.org/mailman/listinfo/104all>