![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
In message <380B7608.77EF2F61 at ecal.com>, John Stracke writes: > Thomas Narten wrote: > > > > 2. IETF working group mailing lists NEED to be run on an IETF system. > > > > Since no VPN WG was ever formed, this mailing list would not have been > > eligible to be an official IETF list. > > That would be one possible policy. Another would be, "OK, if we're going > to hold a BoF, then maybe it'll turn into a WG, and we don't want to > migrate the list, so let's host the BoF list at ietf.org". > > (Mind you, I'm not certain about the premise that having IETF host the > lists would help--the current system is a little messy, but it has the > advantage of spreading the cost out to the people that are most interested > in seeing the work done.) There was no WG because there was insufficient consensus on just what the working group was supposed to do. --Steve Bellovin
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.