![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
It's worth noting that several hundred people attended the newcomers' briefing on the Sunday before the IETF. What I realised, sitting in that meeting, is that the allocated hour or so is simply not long enough to cover everything that newcomers need to know. And it is a bit late on Sunday to tell them to read 600 drafts by Monday morning. Brian John Border wrote: > > Closing meetings might have other implications re Thursday's poisson > discussion... > > Rather than do anything drastic, a preliminary step would be to try to > better educate meeting attendees on what is expected of them before attending a > meeting. At the Orlando meeting, several additional people attended from my > company and, when asked what to expect, I explained to them that to get > anything out of the meetings they planned to attend, they need to read the > drafts pertaining to the meeting or at least spend some time to figure out > (ahead of time) what the working group is all about. Perhaps an attachment can > be automatically tagged onto the reservation confirmation message sent to all > attendees... > > John Border > Hughes Network Systems
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.