[30790] in North American Network Operators' Group
RE: ARIN Policy on IP-based Web Hosting
daemon@ATHENA.MIT.EDU (Jason Slagle)
Thu Aug 31 00:24:22 2000
Date: Thu, 31 Aug 2000 00:22:34 -0400 (EDT)
From: Jason Slagle <raistlin@tacorp.net>
To: nanog@merit.edu
In-Reply-To: <Pine.GSO.4.21.0008301105060.3549-100000@vellocet.insync.net>
Message-ID: <Pine.BSO.4.21.0008310019380.31314-100000@mail.tacorp.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
The problem is that SCP is several orders of magnitude slower then FTP. I
use scp, rsync (on top of ssh), nfs, and several other methods of moving
files around, and ftp blows them all away.
You also need to build a ftp like structure on top of it. ie: I pick the
files I want instead of having to know the filenames.
Until this happens, I can see no viable alternative to FTP.
I wouldn't be unhappy to see one, but we can't retire it without a good
replacement that performs nearly as well.
Jason
---
Jason Slagle - CCNA - CCDA
Network Administrator - Toledo Internet Access - Toledo Ohio
- raistlin@tacorp.net - jslagle@toledolink.com - WHOIS JS10172
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12 GE d-- s:+ a-- C++ UL+++ P--- L+++ E- W- N+ o-- K- w---
O M- V PS+ PE+++ Y+ PGP t+ 5 X+ R tv+ b+ DI+ D G e+ h! r++ y+
------END GEEK CODE BLOCK------
On Wed, 30 Aug 2000, Joe Shaw wrote:
> It has been argued by people far smarter than I that FTP needs to
> disappear, and I tend to agree with them. Not that I think that file
> transfers should no longer take place, but FTP has certainly outlived it's
> usefulness in today's networks and should be replaced with something a bit
> more robust/secure. I think SCP is certainly a start in the right
> direction. With a few modifications, it could certainly be an adequate
> drop-in replacement.
