Xref: utzoo comp.protocols.tcp-ip:11675 comp.protocols.iso:1033 Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!mstar!mstar.morningstar.com!bob From: bob@MorningStar.Com (Bob Sutterfield) Newsgroups: comp.protocols.tcp-ip,comp.protocols.iso Subject: Re: A proposal on a new newsgroup "comp.protocols.migrate.to.iso" Message-ID: Date: 11 Jun 90 14:33:14 GMT References: <4414@infmx.UUCP> <4460@infmx.UUCP> Sender: news@MorningStar.COM (USENET Administrator) Organization: Morning Star Technologies Lines: 40 In-Reply-To: kwang@infmx.UUCP's message of 9 Jun 90 10:06:40 GMT In article <4460@infmx.UUCP> kwang@infmx.UUCP (Kwang Sung) writes: Recently, I've proposed a new newsgroup "comp.protocols.migrate.to.iso". From: Amit Parghi Don't use the name "comp.protocols.migrate.to.iso"; since there are already groups under "comp.protocols.iso", call it "comp.protocols.iso.migration". If comp.protocols.iso and its associated mailing list, iso@nic.ddn.mil, were swamped with transition traffic (it isn't) and if its regular readers were calling for help in the form of another, more focused group and list (they aren't), then the group should be called comp.protocols.iso.migration, in order to fit in with the established naming structure. First of all, I would like to show some responses in order to prove why we need to create those new newsgroup. I'd suggest you follow the common newsgroup creation procedure: set up a mailing list, broadcast its existence to all appropriate, interested forums (e.g. the existing ISO forums), and invite all interested parties to join. When the traffic becomes too heavy for members' mailboxes, you'll have a particularly strong case to call for a new newsgroup. At that time, ask someone to help you set up a gateway between your iso-migration list and the new c.p.i.m newsgroup. And you have my permission, in advance, to say "I told you so" :-) I suspect that the existing list and group facilities are able to manage the traffic. In fact, "the impending IP-ISO transition" is one of the topics of comp.protocols.iso and its associated mailing list. You have asked the folks there whether they're interested in segmenting their discussions. From their responses, I see neither the need or the mandate. In summary, we should continue discussing migration issues in the existing forum. When the popular mandate arises for a new forum, create it as a mailing list. When the mailing list becomes too busy, establish a gateway to a newsgroup named comp.protocols.iso.migration.