Re: [Uri-review] Request for sftp URI scheme

Ira McDonald <blueroofmusic@gmail.com> Wed, 26 September 2018 11:12 UTC

Return-Path: <blueroofmusic@gmail.com>
X-Original-To: uri-review@ietfa.amsl.com
Delivered-To: uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE5CD130E53 for <uri-review@ietfa.amsl.com>; Wed, 26 Sep 2018 04:12:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wp-FAmnwu-8E for <uri-review@ietfa.amsl.com>; Wed, 26 Sep 2018 04:12:45 -0700 (PDT)
Received: from mail-yb1-xb35.google.com (mail-yb1-xb35.google.com [IPv6:2607:f8b0:4864:20::b35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DAE2130E7F for <uri-review@ietf.org>; Wed, 26 Sep 2018 04:12:45 -0700 (PDT)
Received: by mail-yb1-xb35.google.com with SMTP id c4-v6so11130349ybl.6 for <uri-review@ietf.org>; Wed, 26 Sep 2018 04:12:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=sEsoW6DRhqAOP1/P1/JItXM1aLc9DzwFmx66RI6SKQY=; b=OucQx8E136SKneb9U5gV7Gf0D3eu2XLGgoESX7jiWl5OoZnTMpNpj1hKDqhtjaXO+A 5AiXCu+JdRfzXBXx7Td0uglzel1avLjWy/B3QYL0yeHRBVvdIIkZfzgiQjr7GlHMRkQM tACvttfOUZ5gwirrzqI3orKqj8SX/Ylz0zBZk95KCZWisLfIimFGodiOX3eG9h8/JnaC 5BZ1m3OXxOjmPjt1QR1nr9PHOH4WQ0rzradpcEXv8vEZPSaWdLLiAkmDbdK3hElX4yxy VHzvNVmUk6A3Vvib8xE3xE2btc7MCYm25eJ5s/CIOz3x0XIDjLb34QCOoJmCpaYx/3Xv 87WA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=sEsoW6DRhqAOP1/P1/JItXM1aLc9DzwFmx66RI6SKQY=; b=E4m3RSFJPWf8H2C4fcN0SoAv9zWojKy53ecRIVHS4z5LZHcSfBifsyHdnPybB6Jz6g ESTTnMr3z0xoCCzEvfoAbJ6v5MlzxFaD5nX0z3YNt5+kbAcnSuTBZUhdvwcn7wJ/4wpl JXeyIFXohQ52tTyocJfa3eeBE9FxXENz+tByes1MmQqc0kKvx0VqrItBDIGSwXDuS9If VKfkjo7rh8wB8r1sNSS8Rcc7gF+8LufanF0YbDzZV+E/EzUvIxBRq6mLorsnrrKHNBXc F//6nK88LAGZOkAhhuHvjSMWgHegdZkQtSLC43J9NXpILT5EhsskBTAEWaAlxaCkeSkI WzGQ==
X-Gm-Message-State: ABuFfogXMoHrQDphycpzHCzmfrgKbquE4jrJpv26/Y68gwrMxh0uWIMf FAKzerUt0tKiGcsxn/dlK5sFl6uHM9O9X2W0+LY0/1MR
X-Google-Smtp-Source: ACcGV61MJ2uNCxErSwMsj04Uz5L5UseNWwDFXqi4s7QBvF1uE7gSzUcqP1NWczvJeTrkcGE5qmMJoxgRjtuLk0vasyM=
X-Received: by 2002:a25:868e:: with SMTP id z14-v6mr423616ybk.472.1537960364336; Wed, 26 Sep 2018 04:12:44 -0700 (PDT)
MIME-Version: 1.0
References: <5BAB3AE1.2090603@openfortress.nl>
In-Reply-To: <5BAB3AE1.2090603@openfortress.nl>
From: Ira McDonald <blueroofmusic@gmail.com>
Date: Wed, 26 Sep 2018 07:13:50 -0400
Message-ID: <CAN40gSs6MFVTEpK+J2b9_Vhf9x2yQwrL-e==2tMPhqQtrAM+iw@mail.gmail.com>
To: rick@openfortress.nl, Ira McDonald <blueroofmusic@gmail.com>
Cc: "uri-review@ietf.org >> uri-review@ietf.org" <uri-review@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000031ec9b0576c44db8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/uri-review/I3IR3MGmL3uiqENNoM5vv-kvSi0>
Subject: Re: [Uri-review] Request for sftp URI scheme
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uri-review/>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Sep 2018 11:12:49 -0000

Hi Rick,

Your referenced URI I-D in section 4.6 Protocols using this URI Scheme
references https://datatracker.ietf.org/doc/draft-ietf-secsh-filexfer/
which
is expired and was abandoned in 2006.

Two separate efforts to standardize SFTP (the protocol) in IETF failed a
long time ago.  Interoperability between different versions is not
available.

Do you intend to start an IETF standards-track effort to standardize
SFTP?  Or at least to point to a stable, current spec of SFTP protocol?
Otherwise, I believe that even a provisional registration is of dubious
value.

Cheers,
- Ira



Ira McDonald (Musician / Software Architect)
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music / High North Inc
http://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthinc
mailto: blueroofmusic@gmail.com
Jan-April: 579 Park Place  Saline, MI  48176  734-944-0094
May-Dec: PO Box 221  Grand Marais, MI 49839  906-494-2434



On Wed, Sep 26, 2018 at 3:53 AM Rick van Rein <rick@openfortress.nl>; wrote:

> Hello,
>
> This is a registration that seems to be long overdue (and we need it).
>
> Confusion in implementations already seems to exist, at least I've once
> seen the use of "ssh:" in a place where "sftp:" should have been used.
> Looking at the spec of "ssh:" this is "like telnet" and so not menat for
> file transfer, so I would like to propose "sftp:" based on the same
> documentation as originally used for "ssh:" registration.
>
>
> Scheme name:
>      sftp
>
> Status:
>      Provisional
>
> Applications/protocols that use this scheme name:
>      WinSCP,          https://winscp.net/eng/docs/session_url
>      Konqueror / KIO, https://www.youtube.com/watch?v=EVE84xgRrNE
>
>      Plus, we intend to include it into ARPA2 Reservoir, to connect to
>      remote object stores across realm boundaries, using standardised
>      and secure URIs.  Proper authentication will be the starting point
>      for refined access control, which can also allow remote users in.
>      http://reservoir.arpa2.net
>      http://idp.arpa2.net/radius.html
>
> Contact:
>      Rick van Rein <rick@openfortress.nl>;
>
> Change controller:
>      Rick van Rein <rick@openfortress.nl>;
>      Architect for the InternetWide.org project.
>
> References:
>      http://en.wikipedia.org/wiki/Secure_Shell
>      http://tools.ietf.org/html/draft-ietf-secsh-scp-sftp-ssh-uri
>
>
> Thanks,
>
> Rick van Rein
> OpenFortress / InternetWide / ARPA2
>
> _______________________________________________
> Uri-review mailing list
> Uri-review@ietf.org
> https://www.ietf.org/mailman/listinfo/uri-review
>