Re: [Curdle] Advice on SFTP toward RFC?

Benjamin Kaduk <kaduk@mit.edu> Fri, 16 February 2018 01:11 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: curdle@ietfa.amsl.com
Delivered-To: curdle@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BC0E126DED for <curdle@ietfa.amsl.com>; Thu, 15 Feb 2018 17:11:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 N55WBua7yLmK for <curdle@ietfa.amsl.com>; Thu, 15 Feb 2018 17:11:19 -0800 (PST)
Received: from dmz-mailsec-scanner-4.mit.edu (dmz-mailsec-scanner-4.mit.edu [18.9.25.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27E5B124235 for <curdle@ietf.org>; Thu, 15 Feb 2018 17:11:19 -0800 (PST)
X-AuditID: 1209190f-c59ff70000007195-0d-5a862fb50913
Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id 4C.4B.29077.5BF268A5; Thu, 15 Feb 2018 20:11:18 -0500 (EST)
Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id w1G1BDx0020660; Thu, 15 Feb 2018 20:11:15 -0500
Received: from mit.edu (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id w1G1BATM022317 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 15 Feb 2018 20:11:12 -0500
Date: Thu, 15 Feb 2018 19:11:10 -0600
From: Benjamin Kaduk <kaduk@mit.edu>
To: denis bider <denisbider.ietf@gmail.com>
Cc: curdle <curdle@ietf.org>
Message-ID: <20180216011110.GS12363@mit.edu>
References: <CADPMZDCwUEJr3QwPmi5QPU_C4srAkSnWc_nJw0v6e47X57tBRg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CADPMZDCwUEJr3QwPmi5QPU_C4srAkSnWc_nJw0v6e47X57tBRg@mail.gmail.com>
User-Agent: Mutt/1.9.1 (2017-09-22)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrLIsWRmVeSWpSXmKPExsUixG6nortNvy3K4PQnDoutC2cxWxw/N5fZ gclj56y77B5LlvxkCmCK4rJJSc3JLEst0rdL4Mo482s2U0E/S8WMCYfZGxgXMncxcnJICJhI TP33gb2LkYtDSGAxk8TMxj+sEM5GRonlG3axQThnmSR+zNzECNLCIqAq8XHnYlYQm01ARaKh +zLYKBEBbYlV/4+A2cwCMhJ/X+8GqxcWMJDYf+4sE4jNK6AjcW3RYbBeIYEAicVzpjBDxAUl Ts58wgLRqyVx499LoHoOIFtaYvk/DpAwp0CgRP+HZ2CtogLKEnv7DrFPYBSYhaR7FpLuWQjd CxiZVzHKpuRW6eYmZuYUpybrFicn5uWlFuma6OVmluilppRuYgSFKack/w7GOQ3ehxgFOBiV eHg39LZGCbEmlhVX5h5ilORgUhLlzToPFOJLyk+pzEgszogvKs1JLT7EKMHBrCTCe+s1UI43 JbGyKrUoHyYlzcGiJM7rbqIdJSSQnliSmp2aWpBaBJOV4eBQkuA1AMajkGBRanpqRVpmTglC momDE2Q4D9DwDj2gGt7igsTc4sx0iPwpRmOOtpVP2pg5brx43cYsxJKXn5cqJc67HaRUAKQ0 ozQPbhoo1Uhk7695xSgO9Jww72mQKh5gmoKb9wpoFRPQKl4lkD+KSxIRUlINjGvuv+T96675 n3f7Cp/OlZ4nlywXbUt2PPqhZPe/R5MzTrx+57MlcNeKhJpJuzP9dl+NKdtxaU1xcEDN9e3p jGyh+xX9zv77GFX2uqZQ+Ziuqu+GHvfXMZVWkYL6aQv7t/680bbl4+qFBmvDr9z6x1G06OOl xNQDmQmX2t9rP+tzLmu/8ndyjrcSS3FGoqEWc1FxIgDHEW3YEAMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/ij7SHlbVirK3DqGWgTJ3_0TIIj8>
Subject: Re: [Curdle] Advice on SFTP toward RFC?
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "List for discussion of potential new security area wg." <curdle.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/curdle>, <mailto:curdle-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/curdle/>
List-Post: <mailto:curdle@ietf.org>
List-Help: <mailto:curdle-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/curdle>, <mailto:curdle-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Feb 2018 01:11:20 -0000

On Thu, Feb 15, 2018 at 07:09:05PM -0600, denis bider wrote:
> However, if I write a draft - or perhaps two drafts - I'm not sure who to
> turn to. I'm not sure there's a working group that this could be made part
> of. Is it possible to pursue Standards track as an individual submission?
> Should we create a working group with the purpose to document existing
> practice?

This sounds like an excellent question to ask the SECDISPATCH
working group that will (hopefully) meet for the first time at
London.

-Ben