dank@nntp-server.caltech.edu (Daniel R. Kegel) (04/17/91)
PPP is the successor to SLIP, and will soon become a household word for anyone connecting to a TCP/IP LAN over a modem. Let's create comp.protocols.ppp. - Dan Kegel (dank@blacks.jpl.nasa.gov)
swansonc@acc.stolaf.edu (Chris Swanson) (04/18/91)
>>>>> On 16 Apr 91 23:02:04 GMT, >>>>> in message <1991Apr16.230204.7500@nntp-server.caltech.edu>, >>>>> dank@nntp-server.caltech.edu (Daniel R. Kegel) wrote: dank> Article-I.D.: nntp-ser.1991Apr16.230204.7500 dank> PPP is the successor to SLIP, and will soon become a household word dank> for anyone connecting to a TCP/IP LAN over a modem. dank> Let's create comp.protocols.ppp. dank> - Dan Kegel (dank@blacks.jpl.nasa.gov) I second this motion. -Chris -- Chris Swanson, Chem/CS/Pre-med Undergrad, St. Olaf College, Northfield,MN 55057 DDN: (CDS6) INTERNET: swansonc@acc.stolaf.edu UUCP: uunet!stolaf!swansonc AT&T: Work: (507)-645-4528 Home: (507)-663-6424 I would deny this reality, but that wouldn't pay the bills...
brian@telebit.com (Brian Lloyd) (04/19/91)
I would name it comp.protocols.serial-internetworking. It is rather long but it is more descriptive and it can encompass SLIP, PPP, routing issues, dial-up IP, etc. I wouldn't want to give the appearance of being only for PPP. -- Brian Lloyd, WB6RQN Telebit Corporation Network Systems Architect 1315 Chesapeake Terrace brian@napa.telebit.com Sunnyvale, CA 94089-1100 voice (408) 745-3103 FAX (408) 734-3333
jeff@onion.rain.com (Jeff Beadles) (04/21/91)
brian@telebit.com (Brian Lloyd) writes: > >I would name it comp.protocols.serial-internetworking. It is rather >long but it is more descriptive and it can encompass SLIP, PPP, >routing issues, dial-up IP, etc. I wouldn't want to give the >appearance of being only for PPP. Bleep. Wrong answer. :-) Newsgroup name components may not exceed 14 characters. There are still a lot of older versions of Unix out there that don't support any more than 14 character file/directory names. (sigh) The 'serial-internetworking' portion far exceeds this limit. -Jeff -- Jeff Beadles jeff@onion.rain.com
carroll@ssc-vax (Jeff Carroll) (04/23/91)
In article <1991Apr21.052511.22841@onion.rain.com> jeff@onion.rain.com (Jeff Beadles) writes: >brian@telebit.com (Brian Lloyd) writes: >> >>I would name it comp.protocols.serial-internetworking. It is rather >>long but it is more descriptive and it can encompass SLIP, PPP, >>routing issues, dial-up IP, etc. I wouldn't want to give the >>appearance of being only for PPP. > >Bleep. Wrong answer. :-) > >Newsgroup name components may not exceed 14 characters. There are still a lot >of older versions of Unix out there that don't support any more than 14 >character file/directory names. (sigh) Another problem with this name is the insinuation that lines that don't use multipin D connectors are somehow not serial. How is Ethernet inherently less serial than EIA-232D? I'd suggest comp.protocols.internet.eia, to be used for discussion of protocols for internetworking machines using EIA-XXX interfaces and voiceband/leased-line analog modems. This would clear the way for the future creation of comp.protocols. internet.isdn, comp.protocols.internet.sonet, and the ilk. -- Jeff Carroll carroll@ssc-vax.boeing.com "Do you think I care? ... I have an infinite amount of money." -Bill Gates
brian@telebit.com (Brian Lloyd) (04/23/91)
I don't care what it is called. And yes, I did forget that some systems can't handle more than 14 character filenames. I just didn't want it to be named comp.protocols.ppp unless it is strictly for PPP. If it is going to cover the issues of serial internetworking (encompassing SLIP, PPP, dial-up internetworking, etc.) then perhaps the name should be more descriptive. Since I have seen several, "the name is too long," messages but no, "how about naming it comp.protocols.foobar instead," messages, perhaps I should take another shot at it. How about comp.protocols.serial-inet? -- Brian Lloyd, WB6RQN Telebit Corporation Network Systems Architect 1315 Chesapeake Terrace brian@napa.telebit.com Sunnyvale, CA 94089-1100 voice (408) 745-3103 FAX (408) 734-3333
emv@ox.com (Ed Vielmetti) (04/23/91)
> comp.protocols.internet.eia, EIA-XXX interfaces and voiceband / > leased-line analog modems PPP runs on both async and sync lines. EIA is more meaningless even than PPP as an acronym. --Ed
swansonc@acc.stolaf.edu (Chris Swanson) (04/24/91)
>>>>> On 21 Apr 91 05:25:11 GMT, >>>>> in message <1991Apr21.052511.22841@onion.rain.com>, >>>>> jeff@onion.rain.com (Jeff Beadles) wrote: [Text deleted - CDS] jeff> Bleep. Wrong answer. :-) jeff> Newsgroup name components may not exceed 14 characters. There jeff> are still a lot of older versions of Unix out there that don't jeff> support any more than 14 character file/directory names. (sigh) jeff> The 'serial-internetworking' portion far exceeds this limit. How about ser-inet? jeff> -Jeff jeff> -- jeff> Jeff Beadles jeff@onion.rain.com -Chris -- Chris Swanson, Chem/CS/Pre-med Undergrad, St. Olaf College, Northfield,MN 55057 DDN: (CDS6) INTERNET: swansonc@acc.stolaf.edu UUCP: uunet!stolaf!swansonc AT&T: Work: (507)-645-4528 Home: (507)-663-6424 I would deny this reality, but that wouldn't pay the bills...
brnstnd@kramden.acf.nyu.edu (Dan Bernstein) (04/24/91)
In article <EMV.91Apr23040707@poe.aa.ox.com> emv@ox.com (Ed Vielmetti) writes: > > comp.protocols.internet.eia, EIA-XXX interfaces and voiceband / > > leased-line analog modems > PPP runs on both async and sync lines. EIA is more meaningless even > than PPP as an acronym. Yeah. What's wrong with comp.protocols.serial? The *protocols* here are serial, even if they run over parallel or asynchronous lines. ---Dan
jessea@homecare.uucp (Jesse W. Asher) (04/25/91)
In article <1991Apr22.220622.7421@telebit.com>, brian@telebit.com (Brian Lloyd) wrote the following: >Since I have seen several, "the name is too long," messages but no, >"how about naming it comp.protocols.foobar instead," messages, perhaps >I should take another shot at it. How about >comp.protocols.serial-inet? I like this - it is a compromise between serial, ppp, and the others that have been posted. This one has my vote! -- Jesse W. Asher NIC Handle: JA268 Phone: (901)386-5061 Health Sphere of America Inc. 5125 Elmore Rd., Suite 1, Memphis, TN 38134 UUCP: ...!banana!homecare!jessea
warb@faatcrl.UUCP (Dan Warburton) (04/25/91)
Well when the voting comes aroud I'd like to see comp.protocols.ppp as my first choice and comp.protocols.serial-net as a second choice. More and more people will be turning to ppp and there will be comp.protocols.ppp to help spread the word. I'd vote yes. -- + Dan Warburton Nas Simulation Support Facility (NSSF) + Federal Aviation Administration Technical Center + Atlantic City International Airport, NJ 08405 // + 609-484-4480 Mail Stop: ACN-313 Amiga \X/ Sun + warb@faatcrl.uucp ...rutgers!faatcrl!warb -- An Open Systems Group --
dave@fps.com (Dave Smith) (04/25/91)
PPP really reflects what we want the group to be about, LAN interconnection. Unfortunately it is also the name of an already established protocol. How about comp.protocols.inter-tie? -- David L. Smith FPS Computing, San Diego ucsd!celit!dave or dave@fps.com "It was time to stop playing games. It was time to put on funny hats and eat ice cream. Froggie played his oboe" - Richard Scarry
brian@telebit.com (Brian Lloyd) (04/25/91)
I guess that bottom line is that there is interest in forming this new newsgroup regardless of its name. No name yet proposed is optimal but not having the newsgroup is definitely suboptimal. I have never created a newsgroup before so I will leave it up to someone else to do. If someone else with more experience does not do it within a day or two, I will. BTW, there is probably going to be a goodly bit of SLIP discussion in this new newsgroup. PPP may be the wave of the future but SLIP is what most people are using now. -- Brian Lloyd, WB6RQN Telebit Corporation Network Systems Architect 1315 Chesapeake Terrace brian@napa.telebit.com Sunnyvale, CA 94089-1100 voice (408) 745-3103 FAX (408) 734-3333
emv@ox.com (Ed Vielmetti) (04/25/91)
In article <1991Apr24.235827.26048@telebit.com> brian@telebit.com (Brian Lloyd) writes:
I guess that bottom line is that there is interest in forming this new
newsgroup regardless of its name. No name yet proposed is optimal but
not having the newsgroup is definitely suboptimal. I have never
created a newsgroup before so I will leave it up to someone else to
do. If someone else with more experience does not do it within a day
or two, I will.
Brian, please don't just create the group.
There is an established protocol for creating a new newsgroup; it's
rather speedier than (e.g.) the ISO standardization process, but it
does take a while to spin itself out. Right now we're in the
"discussion" phase, which involves a ritual wailing and gnashing of
teeth over picking the right name. The prescribed time for that is
two weeks (see news.announce.newgroups). I'm collecting all of the
traffic about PPP, in all of the groups that I get and will include
that information in the "call for votes" which looks like I'm going
to start some time in May. The vote itself will take all of May
(about a month).
Although it's kind of a pain that traffic is spread around, it's
useful to wait for all of the necessary usenet rules have been waited
for. It's just not practical for news administrators to have to guess
whether new groups are valid, and going through the ritual ensures
plenty of advance billing and time to prepare for the easy to answer
questions. For now, there's always the IETF PPP mailing list,
subscriptions to ietf-ppp-request@ucdavis.edu.
Between now and say June 1, use comp.dcom.modems and comp.dcom.lans
for this kind of stuff; after that, the group (whatever its name is)
show have plenty of reasonable traffic. My preference is
comp.protocols.ppp, in no small part because "ppp" is a unique enough
and catchy enough acronym to be easily found in vast volumes of news
by automatic methods. "serial internetworking" or some contraction of
it is more descriptive but much hard to grep for....
--
Msen Edward Vielmetti
/|--- moderator, comp.archives
emv@msen.com
"(6) The Plan shall identify how agencies and departments can
collaborate to ... expand efforts to improve, document, and evaluate
unclassified public-domain software developed by federally-funded
researchers and other software, including federally-funded educational
and training software; "
High-Performance Computing Act of 1991, S. 218david@indetech.com (David Kuder x2003) (04/30/91)
In article <3884@ssc-bee.ssc-vax.UUCP> carroll@ssc-vax.UUCP (Jeff Carroll) writes: > Another problem with this name is the insinuation that lines that >don't use multipin D connectors are somehow not serial. How is Ethernet >inherently less serial than EIA-232D? I've left my references at home, but please try to find a Tanenbaum. He goes into great detail why ethernet isn't just serial. It is a packet medium on a broadcast wire with collision detection. You can drag in the heirarchical model of your choice and work out which bits fit where, but the serial bit ordering of ethernet is a small part compared to EIA-@#@D. The serialness you seem to see in these protocols can be found in every protocol. The arrow of time is a work in them all. A "parallel" printer port is actually byte serial. Disk buses are byte or word serial during transfers. As long as we're moving something from one place to another one will follow the other at some level. > I'd suggest comp.protocols.internet.eia, to be used for discussion >of protocols for internetworking machines using EIA-XXX interfaces and >voiceband/leased-line analog modems. But EIA means nothing at all to me. Couldn't whoever EIA are do something other than RS-232 type standards (like BNC)? I don't think EIA is any improvement over PPP. > This would clear the way for the future creation of comp.protocols. >internet.isdn, comp.protocols.internet.sonet, and the ilk. To the best of my knowledge PPP could run over ISDN, SONET and frame relay. Maybe not well. But PPP is designed to provide Point to Point connections over low speed asynchronous serial links as well as medium (56Kb) to high speed synchronous serial links (T1). Feel free to prove me wrong in comp.protocols.ppp. -- David A. Kuder Looking for enough time to get past patchlevel 1 415 438-2003 david@indetech.com {uunet,sun,sharkey,pacbell}!indetech!david