Spencer, This practice was started because the main IETF list got flooded with messages like "where is the nearest Apple store?" once we were onsite and this annoyed the folks who weren't actually at the meeting. Having it (opt-in) on a per-meeting basis makes sense to me, if we create the list in advance of the meeting (pre-registration), I guess we'd have to figure out some subscription mechanims (like "you will be auto-subscribed once you post your first message to ietf-xx" or something like that.) I can see a lot of value in having a list created well in advance to answer questions such as visa and transportation. Ole Ole J. Jacobsen Editor and Publisher, The Internet Protocol Journal Cisco Systems Tel: +1 408-527-8972 Mobile: +1 415-370-4628 E-mail: ole@xxxxxxxxx URL: http://www.cisco.com/ipj On Tue, 30 Mar 2010, Spencer Dawkins wrote: > I'm not sure I understand what problem we're solving by setting up IETF > meeting-specific mailing lists each time. It's not like most of the attendees > at IETF 77 weren't at at least one meeting in the previous year, and if there > is a population on earth that we should expect to be able to unsubscribe from > mailing lists when they aren't relevant to us, it's IETF attendees. Maybe an > ietf-meeting-attendees mailing list, and be done with it? > > Spencer > _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf