![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Intresting concept, maybe we should all wear purple robes with gold belts and speak in an ancient dialect (spl???). Actually, quite seriously, its not a bad idea, a little crude, but some sort of qualification such as reading elementary docs would be a good prerequisite. Flame me not, we are all after a solution, I don't know that this is it, and it really goes against alot I stand for, but I guess we could look at it like a course at university, where the student (in this case participants) must have a basic level of understanding. After all, if you don't have some level of interest/understanding you wouldn't want to go to a boring workgroup where you couldn't participate anyway. Cheers, Mitch Denny warbyte at ezymail.com > -----Original Message----- > From: Marshall Rose [mailto:mrose at dbc.mtview.ca.us] > Sent: Tuesday, December 15, 1998 07:51 > To: ietf at ietf.org > Subject: a simple solution to the room crowding problem... > > > well, at the risk of being re-branded a ne'er do well, i have a simple > suggestion to the meeting room problem. > > first, let's see if we can agree that, in general, the problem is with > working groups and not bofs. > if so: > > require that every working group publish at least one I-D prior to the > meeting. in that I-D put a password, e.g., "swordfish". the > password should > be buried in the middle of a big paragraph of text somewhere, e.g., > "big-endian, blah, blah, blah ... and the password is swordfish > (don't tell > anyone, eh?) blah, blah, blah little-endian." > > at the meeting, have a monitor stand at the door asking for the > password. no > password? have the monitor give them a hard copy of the I-D with > instructions to read it cover to cover and then come back. > > /mtr > >
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.