Re: SSH File Transfer Protocol - draft-moonesamy-secsh-filexfer-00
"denis bider \(Bitvise\)" <ietf-ssh3@denisbider.com> Fri, 12 July 2013 15:44 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 1EA5C21F9307 for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Fri, 12 Jul 2013 08:44:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 Dm4pmZV7T3MK for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Fri, 12 Jul 2013 08:44:10 -0700 (PDT)
Received: from mail.netbsd.org (mail.NetBSD.org [IPv6:2001:4f8:3:7::25]) by ietfa.amsl.com (Postfix) with ESMTP id 1CF5D21F91BF for <secsh-tyoxbijeg7-archive@lists.ietf.org>; Fri, 12 Jul 2013 08:44:10 -0700 (PDT)
Received: by mail.netbsd.org (Postfix, from userid 605) id D41D714A28A; Fri, 12 Jul 2013 15:44:06 +0000 (UTC)
Delivered-To: ietf-ssh@NetBSD.org
Received: from localhost (localhost [127.0.0.1]) by mail.netbsd.org (Postfix) with ESMTP id 1837C14A23E for <ietf-ssh@NetBSD.org>; Fri, 12 Jul 2013 15:44:03 +0000 (UTC)
X-Virus-Scanned: amavisd-new at NetBSD.org
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 pD3_GpGq5Az0 for <ietf-ssh@NetBSD.org>; Fri, 12 Jul 2013 15:44:02 +0000 (UTC)
Received: from skroderider.denisbider.com (skroderider.denisbider.com [50.18.172.175]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.netbsd.org (Postfix) with ESMTPS id 6DD5C14A22F for <ietf-ssh@NetBSD.org>; Fri, 12 Jul 2013 15:44:02 +0000 (UTC)
X-Footer: ZGVuaXNiaWRlci5jb20=
Received: from localhost ([127.0.0.1]) by skroderider.denisbider.com (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Fri, 12 Jul 2013 15:43:22 +0100
Message-ID: <A433CD8982A340C09BFBF0E5D4911A71@Dragonborn>
From: "denis bider (Bitvise)" <ietf-ssh3@denisbider.com>
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>, S Moonesamy <sm+ietf@elandsys.com>
Cc: ietf-ssh@NetBSD.org
References: <9A043F3CF02CD34C8E74AC1594475C734470C9DE@uxcn10-6.UoA.auckland.ac.nz> <6.2.5.6.2.20130712050150.0cd0f7e8@elandnews.com>
In-Reply-To: <6.2.5.6.2.20130712050150.0cd0f7e8@elandnews.com>
Subject: Re: SSH File Transfer Protocol - draft-moonesamy-secsh-filexfer-00
Date: Fri, 12 Jul 2013 08:42:40 -0600
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="response"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 15.4.3555.308
X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3555.308
Sender: ietf-ssh-owner@NetBSD.org
List-Id: ietf-ssh.NetBSD.org
Precedence: list
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. -----Original Message----- From: S Moonesamy Sent: Friday, July 12, 2013 06:18 To: Peter Gutmann Cc: ietf-ssh@NetBSD.org Subject: Re: SSH File Transfer Protocol - draft-moonesamy-secsh-filexfer-00 Hi Peter, At 04:37 12-07-2013, Peter Gutmann wrote: >Some background information on this decision would be useful, for example >why >restart work on it now, and why use version 3 of the protocol as the >baseline? There was a short discussion a few months ago about Section 6.1 of an expired SFTP drafts. I used Version 3 as the baseline as that is the version which OpenSSH implemented. In my opinion it would be easier to document Version 3 as an IETF specification instead of trying to pursue the previous efforts. 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