IETF Logo Mail Archive

Re: [Curdle] Comments on draft-ietf-curdle-ssh-ext-info

Benjamin Kaduk <kaduk@mit.edu> Sat, 18 March 2017 23:48 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 7B72512773A for <curdle@ietfa.amsl.com>; Sat, 18 Mar 2017 16:48:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.222
X-Spam-Level:
X-Spam-Status: No, score=-4.222 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] 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 sKVMhQ1bnDLJ for <curdle@ietfa.amsl.com>; Sat, 18 Mar 2017 16:48:49 -0700 (PDT)
Received: from dmz-mailsec-scanner-3.mit.edu (dmz-mailsec-scanner-3.mit.edu [18.9.25.14]) (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 1ED4312944F for <curdle@ietf.org>; Sat, 18 Mar 2017 16:48:48 -0700 (PDT)
X-AuditID: 1209190e-1bfff700000015e1-29-58cdc75e9447
Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by (Symantec Messaging Gateway) with SMTP id 47.EB.05601.E57CDC85; Sat, 18 Mar 2017 19:48:46 -0400 (EDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id v2INmjPd004672; Sat, 18 Mar 2017 19:48:45 -0400
Received: from kduck.kaduk.org (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 v2INmf8H001469 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 18 Mar 2017 19:48:44 -0400
Date: Sat, 18 Mar 2017 18:48:41 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: "denis bider (Bitvise)" <ietf-ssh3@denisbider.com>
Cc: curdle <curdle@ietf.org>
Message-ID: <20170318234841.GB30306@kduck.kaduk.org>
References: <2DD56D786E600F45AC6BDE7DA4E8A8C118BA5A70@eusaamb107.ericsson.se> <1489827654266.43895@cs.auckland.ac.nz> <50977E6A3D174856B8DAF264C3CB81E8@Khan>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <50977E6A3D174856B8DAF264C3CB81E8@Khan>
User-Agent: Mutt/1.6.1 (2016-04-27)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupjleLIzCtJLcpLzFFi42IR4hTV1o07fjbCYMVxQYutC2cxW9x7OYXR gcnj/vR57B5LlvxkCmCK4rJJSc3JLEst0rdL4Mp48vcse0E/a0Vb0yb2BsZZLF2MnBwSAiYS rxdMYQOxhQTamCR+tyl0MXIB2RsZJabM28oO4Vxlkuif9ZIdpIpFQFVi/8lVYDabgIpEQ/dl ZhBbRMBMYtuO26wgNrOAjMTf17sZQWxhAQeJT9u7wGp4gbZ93fKVDWLoQqANX5ayQCQEJU7O fMIC0awu8WfeJaAGDiBbWmL5Pw6IsLxE89bZYGFOoDnvJleChEUFlCUaZjxgnsAoOAvJoFlI Bs1CGDQLyaAFjCyrGGVTcqt0cxMzc4pTk3WLkxPz8lKLdI31cjNL9FJTSjcxgoNakm8H46QG 70OMAhyMSjy8P8rPRgixJpYVV+YeYpTkYFIS5bWWORMhxJeUn1KZkVicEV9UmpNafIhRgoNZ SYQ3czJQOW9KYmVValE+TEqag0VJnFdcozFCSCA9sSQ1OzW1ILUIJivDwaEkwXvzKFCjYFFq empFWmZOCUKaiYMTZDgP0PD/IDW8xQWJucWZ6RD5U4y6HDeOH3jDJMSSl5+XKiXOewekSACk KKM0D24OKBlJZO+vecUoDvSWMO/RY0BVPMBEBjfpFdASJqAly26cAVlSkoiQkmpg5LDzXsYx m6V5a9zkA5oNDIr+m5bNseJu071wtGRh7FGdsiP+N5N2GOn27LuqvHjrJ7eQQ58UGLKV1rtz 9K/vOs3eJzN1lZRu39YL1b0X7rTfdL1f91nmV+3Wj1cPGNn/kc7N3ulq1urlFOtzf+3slXpz 7ngwN9xunJJ9etr6Eif1Jwl/7+yaq8RSnJFoqMVcVJwIAASHoJohAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/ior4LpPpBNlpbeCe4WUo1zYekxU>
Subject: Re: [Curdle] Comments on draft-ietf-curdle-ssh-ext-info
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: Sat, 18 Mar 2017 23:48:50 -0000

Replying to just a process point:

On Sat, Mar 18, 2017 at 07:30:48AM -0600, denis bider (Bitvise) wrote:
> My understanding, also, is that IETF expects implementations to exist in order to bless an RFC – at least two independent implementations ideally, or at least one minimum. Perhaps I’m mistaken on this?

You are probably thinking about getting a document published as a
full IETF Internet Standard, which does require at least two
interoperable implementations.  Less stringent RFC types, such as
Proposed Standard, Informational, and Experimental, do not have such
a requirement (though it's always good to have, of course).

-Ben

v2.23.0 | Report a Bug | By Email