Re: [saag] Additions to RFC 3631?

Joe Touch <touch@isi.edu> Tue, 22 May 2012 17:00 UTC

Return-Path: <touch@isi.edu>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D71021F8630 for <saag@ietfa.amsl.com>; Tue, 22 May 2012 10:00:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 2K7kUpwlBmpt for <saag@ietfa.amsl.com>; Tue, 22 May 2012 10:00:34 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 6C9FC21F8606 for <saag@ietf.org>; Tue, 22 May 2012 10:00:34 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q4MGxZ1g013014 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 22 May 2012 09:59:35 -0700 (PDT)
Message-ID: <4FBBC5F7.3030008@isi.edu>
Date: Tue, 22 May 2012 09:59:35 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Nico Williams <nico@cryptonector.com>
References: <300A2E9F-E99B-46FA-A101-E3611BD0D197@cs.columbia.edu> <877gw69h81.fsf@latte.josefsson.org> <4FB9ECA4.3010904@gmail.com> <D54BB652-9B1D-4A19-8F8F-AF288E4ADE24@cs.columbia.edu> <78F24BEE-DD3B-474D-9E0B-1AC73CBE373A@vpnc.org> <CAK3OfOj=jR4R+hBDTcv-DNqqU0AdHHonSTOmsMpR3ZqmhDmbdQ@mail.gmail.com> <4FBA7807.5080207@isi.edu> <4FBA8820.2030702@gmail.com> <CAK3OfOgELvoK5xSeVaCpOjd6yaA=ROJv88pM9SOdZkeEcbb3ew@mail.gmail.com>
In-Reply-To: <CAK3OfOgELvoK5xSeVaCpOjd6yaA=ROJv88pM9SOdZkeEcbb3ew@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, IETF Security Area Advisory Group <saag@ietf.org>
Subject: Re: [saag] Additions to RFC 3631?
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/saag>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 May 2012 17:00:35 -0000

On 5/21/2012 11:27 AM, Nico Williams wrote:
> On Mon, May 21, 2012 at 1:23 PM, Yaron Sheffer<yaronf.ietf@gmail.com>  wrote:
>> Trying my best to be unpopular:
>>
>> Much as I like the concept of BTNS, it hasn't caught on. I see this RFC as
>> providing useful guidance to practitioners, and non-existent technology
>> doesn't cut it.
>
> Hey, I said it too.
>
>> On the other hand, SSH "leap of faith" is very close to BTNS, and should in
>> fact be mentioned in the paragraph that discusses SSH. In the context of
>> SSH, "leap of faith" is much more innovative than what the current text
>> focuses on.
>
> Right.  But note that for me BTNS was not about leap-of-faith, though
> that was a key selling point for some.  For me BTNS was about
> anon-anon channels that could be bound into app-layer authentication.

Or useful even without further authentication - by raising the effort of 
an attacker -- i.e., attacks need to do the work of a flash-crowd; 
merely tossing RSTs at TCP connections wouldn't work under BTNS, even 
without tying security at that connection to another layer. And that 
sort of protection is possible without *any* KMI.

Joe