Re: POP3 protocol question
Steve Dorner <sdorner@qualcomm.com> Thu, 13 October 1994 01:57 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa10963; 12 Oct 94 21:57 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa10959; 12 Oct 94 21:57 EDT
Received: from PO2.ANDREW.CMU.EDU by CNRI.Reston.VA.US id aa00326; 12 Oct 94 21:57 EDT
Received: (from postman@localhost) by po2.andrew.cmu.edu (8.6.9/8.6.9) id VAA11284; Wed, 12 Oct 1994 21:52:48 -0400
Received: via switchmail for ietf-pop3+@andrew.cmu.edu; Wed, 12 Oct 1994 21:52:45 -0400 (EDT)
Received: from po2.andrew.cmu.edu via qmail ID </afs/andrew.cmu.edu/service/mailqs/q003/QF.Aib99bK00UdaQfiE4Z>; Wed, 12 Oct 1994 21:50:31 -0400 (EDT)
Received: from ux1.cso.uiuc.edu (ux1.cso.uiuc.edu [128.174.5.59]) by po2.andrew.cmu.edu (8.6.9/8.6.9) with SMTP id VAA11188 for <ietf-pop3+@andrew.cmu.edu>; Wed, 12 Oct 1994 21:50:24 -0400
Received: from dorner1.isdn.uiuc.edu by ux1.cso.uiuc.edu with SMTP id AA21825 (5.67b8/IDA-1.5 for <ietf-pop3+@andrew.cmu.edu>); Wed, 12 Oct 1994 20:50:08 -0500
Received: from [192.17.16.12] (dorner3.isdn.uiuc.edu) by dorner1.isdn.uiuc.edu with SMTP id AA00677 (5.67b/IDA-1.5 for <ietf-pop3+@andrew.cmu.edu>); Wed, 12 Oct 1994 20:51:00 -0500
X-Sender: sdorner@192.17.16.10
Message-Id: <aac2400c18030001edad@[192.17.16.12]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 12 Oct 1994 20:50:30 -0500
To: POP3 IETF Mailing List <ietf-pop3+@andrew.cmu.edu>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Steve Dorner <sdorner@qualcomm.com>
Subject: Re: POP3 protocol question
>If you're going over a dialup line, you need error detection with >retransmission. MNP and LAP-M are quite adequate. There are also error-checked streams that do NOT support TCP, and for whom a single TCP port is by far more convenient. While this of course is not *strictly* an Internet issue, it's a reasonable stretch. >Second, if you start down the slippery >slope of agreeing to put SMTP into POP3, next people will ask for FTP, >GOPHER, etc in POP3 so that MIME's message/external-body can be >fetched. I don't really think there is a slope here at all. You have two basic needs with mail; sending and receiving. I think there's a quite clear step from XTND XMIT to gopher. I'm not arguing for standardization of XTND XMIT; I'd just rather not hear bad arguments against it. >What's complex is putting duplicate functionality in every protocol. Agreed. -- Steve Dorner, Qualcomm Incorporated Whosoever has lived long enough to find out what life is, knows how deep a debt of gratitude we owe to Adam. He brought death into this world. Mark Twain
- POP3 protocol question Jerome Chan
- Re: POP3 protocol question Chris Newman
- Re: POP3 protocol question Steve Dorner
- Re: POP3 protocol question brtmac
- Re: POP3 protocol question Michael D'Errico
- Re: POP3 protocol question Jerome Chan
- Re: POP3 protocol question Steve Dorner
- Re: POP3 protocol question Chris Newman
- Re: POP3 protocol question brtmac
- Re: POP3 protocol question Steve Dorner
- Re: POP3 protocol question Mark Crispin
- Re: POP3 protocol question Steve Dorner
- Re: POP3 protocol question John Gardiner Myers
- Re: POP3 protocol question Ned Freed