RE: SSH File Transfer Protocol - draft-moonesamy-secsh-filexfer-00
S Moonesamy <sm+ietf@elandsys.com> Mon, 15 July 2013 08:23 UTC
Return-Path: <bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org>
X-Original-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Delivered-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81D1421F997B for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Mon, 15 Jul 2013 01:23:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.588
X-Spam-Level:
X-Spam-Status: No, score=-102.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hiDlYvuLdmhB for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Mon, 15 Jul 2013 01:23:23 -0700 (PDT)
Received: from mail.netbsd.org (mail.NetBSD.org [IPv6:2001:4f8:3:7::25]) by ietfa.amsl.com (Postfix) with ESMTP id 23D6621F9ECE for <secsh-tyoxbijeg7-archive@lists.ietf.org>; Mon, 15 Jul 2013 01:20:31 -0700 (PDT)
Received: by mail.netbsd.org (Postfix, from userid 605) id 8926E14A1CF; Mon, 15 Jul 2013 08:20:24 +0000 (UTC)
Delivered-To: ietf-ssh@NetBSD.org
Received: from localhost (localhost [127.0.0.1]) by mail.netbsd.org (Postfix) with ESMTP id C653714A1C6 for <ietf-ssh@NetBSD.org>; Mon, 15 Jul 2013 08:20:15 +0000 (UTC)
X-Virus-Scanned: amavisd-new at NetBSD.org
Authentication-Results: mail.NetBSD.org (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=V72knHr0; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=qhNLpcCX
Received: from mail.netbsd.org ([127.0.0.1]) by localhost (mail.NetBSD.org [127.0.0.1]) (amavisd-new, port 10025) with ESMTP id Nj88y3BRt1Iw for <ietf-ssh@NetBSD.org>; Mon, 15 Jul 2013 08:20:15 +0000 (UTC)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by mail.netbsd.org (Postfix) with ESMTP id A775E14A1C2 for <ietf-ssh@NetBSD.org>; Mon, 15 Jul 2013 08:20:14 +0000 (UTC)
Received: from SUBMAN.elandsys.com ([197.224.153.203]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r6F8JxsJ015210 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Jul 2013 01:20:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1373876412; bh=XNG1PwBE5/xoHKfhx+L1a2JKcZDcy7E3JJG8Tv0NYu8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=V72knHr0EDokNmkfslZG1XsExgq+R1jc76IcaE/sh6jzX1LSRJf99+9QyDcJ/DXQp mc8O4d9/DJFkbwQ2emJ8LAHVO1b0ulhi31birQZnVsfaoujSFFLn3/Dr2caccEKQpM eH+ek33jn3feXUi3GryQ0DqZW3IeZYPFmBQKRznQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1373876412; i=@elandsys.com; bh=XNG1PwBE5/xoHKfhx+L1a2JKcZDcy7E3JJG8Tv0NYu8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=qhNLpcCX/CWHk36rSt4Tfug8GnUoYs0Hle38sqh8YacsQSBAO96n3D8ipSXd/mvgM fog8GlZzsa6Gqig/rSeZf1rpWk7GkSus5GCC7HPwPOA331kszyR9f3RBJPEmxsqH3B awvXLDqYRi34GTXGCETk3fA2TQyYLqClyXVSWWgw=
Message-Id: <6.2.5.6.2.20130715003705.0d08f828@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 15 Jul 2013 00:51:17 -0700
To: Rich Whalen <whalenr@process.com>, "denis bider (Bitvise)" <ietf-ssh3@denisbider.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: RE: SSH File Transfer Protocol - draft-moonesamy-secsh-filexfer-00
Cc: ietf-ssh@NetBSD.org
In-Reply-To: <33d1f2bbe99843448ee8e993d701b14f@BL2PR08MB004.namprd08.pro d.outlook.com>
References: <9A043F3CF02CD34C8E74AC1594475C734470C9DE@uxcn10-6.UoA.auckland.ac.nz> <6.2.5.6.2.20130712050150.0cd0f7e8@elandnews.com> <33d1f2bbe99843448ee8e993d701b14f@BL2PR08MB004.namprd08.prod.outlook.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: ietf-ssh-owner@NetBSD.org
List-Id: ietf-ssh.NetBSD.org
Precedence: list
At 05:50 12-07-2013, Rich Whalen wrote: >The protocol is more of a file access protocol than a file transfer protocol. >This re-introduction of Version 3 of the protocol has the problem of >not addressing the problem of exchanging text files on dissimilar >systems. Though OpenSSH is a very common implementation there are >other implementations on systems that use a line break mechanism >that is different from Unix/Linux. Many commercial users of SFTP >implementations use it to transfer files between dissimilar systems >and often encounter problems with text files that use different line >break sequences. While the EXTENDED operation allows for vendor >specific extensions, the problem is that they are VENDOR specific, >and a company implementing a SFTP utility does not want to try to >determine which implementation of the protocol they are dealing with >and implement one of a variety of text file access methods. Thanks for the feedback. I'll comment below. At 07:42 12-07-2013, denis bider (Bitvise) wrote: >A fair number of implementations, including ours, implement SFTP >versions 4 and 6, as specified in: > >draft-ietf-secsh-filexfer-13.txt > >as well as extensions specified in: > >draft-galb-filexfer-extensions-00.txt > >Just because one open source implementation chooses to be stuck in >the past - apparently because SFTP version 3 is simplistic, and >offered most of what is needed on their target platform - doesn't >mean it should get to dictate the standard. > >The latest SFTP version is 6. Restarting standardization at 3 >doesn't mean implementations of 4 and 6 are going to go away. It in >fact means that two concurrent SFTP version trees are going to exist >in the future. I think this is a poor decision, and I do not support it. > >Any standardization efforts should continue where these documents left off: > >draft-ietf-secsh-filexfer-13.txt >draft-galb-filexfer-extensions-00.txt > >If OpenSSH chooses to be stuck in the past and implement an older >version of the protocol known as SFTP version 3, then the OpenSSH >project can document the version they implement, but based on one >implementation, that doesn't need to be an internet standard. The draft is not about dictating any Internet standard. I understand that there are a number of implementations that implement different versions of the expired drafts. I am also aware of the file access protocol discussion and the discussion about vendor specific extensions. As I mentioned previously my effort is about documentation what exists. It is not about making implementations of 4 and 6 go away. Regards, S. Moonesamy
- SSH File Transfer Protocol - draft-moonesamy-secs… S Moonesamy
- Re: SSH File Transfer Protocol - draft-moonesamy-… Peter Gutmann
- Re: SSH File Transfer Protocol - draft-moonesamy-… S Moonesamy
- Re: SSH File Transfer Protocol - draft-moonesamy-… denis bider (Bitvise)
- Re: SSH File Transfer Protocol - draft-moonesamy-… Mouse
- Re: SSH File Transfer Protocol - draft-moonesamy-… Mouse
- Re: SSH File Transfer Protocol - draft-moonesamy-… Mark D. Baushke
- Re: SSH File Transfer Protocol - draft-moonesamy-… Peter Gutmann
- RE: SSH File Transfer Protocol - draft-moonesamy-… S Moonesamy
- Re: SSH File Transfer Protocol - draft-moonesamy-… S Moonesamy
- Re: SSH File Transfer Protocol - draft-moonesamy-… S Moonesamy
- RE: SSH File Transfer Protocol - draft-moonesamy-… Rich Whalen
- Re: SSH File Transfer Protocol - draft-moonesamy-… Albert Lunde
- Re: SSH File Transfer Protocol - draft-moonesamy-… Mark D. Baushke
- Re: SSH File Transfer Protocol - draft-moonesamy-… Jeffrey Hutzelman
- Re: SSH File Transfer Protocol - draft-moonesamy-… Damien Miller
- Re: SSH File Transfer Protocol - draft-moonesamy-… Joseph Galbriath
- Re: SSH File Transfer Protocol - draft-moonesamy-… Joseph Galbriath
- Re: SSH File Transfer Protocol - draft-moonesamy-… Joseph Galbriath
- Re: SSH File Transfer Protocol - draft-moonesamy-… Joseph Galbriath
- Re: SSH File Transfer Protocol - draft-moonesamy-… S Moonesamy
- Re: SSH File Transfer Protocol - draft-moonesamy-… Peter Gutmann
- Re: SSH File Transfer Protocol - draft-moonesamy-… Damien Miller
- Re: SSH File Transfer Protocol - draft-moonesamy-… Richard Kettlewell