Re: [spring] IETF 102 - SPRING meeting

[<[e-mail]>]

Hi all,

Agenda has been uploaded: https://datatracker.ietf.org/meeting/102/materials/agenda-102-spring-00

We have a full agenda so please respect your timeslot, which account for both presentation and discussion. In general it's not needed to present the draft in detail.

We had requests for 219 minutes (not counting late requests) so some slots had to be reduced and some slots could not fit in.
In this condition, although coordination with other WGs is generally good, for drafts both targeting a different WG, and presented in that different WG, chairs will present a slide advertising the presentation in those WGs (IDR, PIM) rather than allocating a second slot in SPRING.

Thanks,
See you in Montréal,
--Bruno, Rob


From: spring [mailto:[e-mail]] On Behalf Of [e-mail]
Sent: Monday, June 18, 2018 12:30 PM
To: [e-mail]
Subject: [spring] IETF 102 - SPRING meeting


Hi all,



During IETF 102, the SPRING WG is currently scheduled to meet Monday 13:30-15:30. We have a two hours session.
https://datatracker.ietf.org/meeting/102/agenda.html


It is time start building the SPRING WG agenda for Montreal.

Please send your request for a presentation slot, indicating draft name, speaker, and desired duration (covering presentation and discussion), before Monday 2018-07-02  09:00 CET. Before is better.

If it is not the first presentation of a non-WG draft, please give a reason why it is required to have a new presentation slot.

A checklist is available on the wiki: https://trac.ietf.org/trac/spring/wiki/Checklist%20for%20presenting%20at%20a%20SPRING%20meeting



As we are meeting on Monday, please send your slides on time, before Sunday 18:00 local time. Earlier is better.


Thanks,
--Bruno, Rob

_________________________________________________________________________________________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.