Re: [saag] Additions to RFC 3631?

Simon Josefsson <simon@josefsson.org> Mon, 21 May 2012 06:33 UTC

Return-Path: <simon@josefsson.org>
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 C93FF21F8473 for <saag@ietfa.amsl.com>; Sun, 20 May 2012 23:33:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.309
X-Spam-Level:
X-Spam-Status: No, score=-97.309 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_COM=0.553, HOST_EQ_STATICB=1.372, 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 tWT6YmIqQFYh for <saag@ietfa.amsl.com>; Sun, 20 May 2012 23:33:02 -0700 (PDT)
Received: from yxa-v.extundo.com (static-213-115-179-173.sme.bredbandsbolaget.se [213.115.179.173]) by ietfa.amsl.com (Postfix) with ESMTP id B0B4921F850F for <saag@ietf.org>; Sun, 20 May 2012 23:33:00 -0700 (PDT)
Received: from latte (static-213-115-179-130.sme.bredbandsbolaget.se [213.115.179.130]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id q4L6WkCV009076 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 21 May 2012 08:32:48 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Steven Bellovin <smb@cs.columbia.edu>
References: <300A2E9F-E99B-46FA-A101-E3611BD0D197@cs.columbia.edu>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:120521:saag@ietf.org::W2dwtGhzLGCMsf2n:4qR/
X-Hashcash: 1:22:120521:smb@cs.columbia.edu::J79Y5Ko6pLsygylg:8TeW
Date: Mon, 21 May 2012 08:32:46 +0200
In-Reply-To: <300A2E9F-E99B-46FA-A101-E3611BD0D197@cs.columbia.edu> (Steven Bellovin's message of "Fri, 18 May 2012 22:31:39 -0400")
Message-ID: <877gw69h81.fsf@latte.josefsson.org>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/23.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Virus-Scanned: clamav-milter 0.97.3 at yxa-v
X-Virus-Status: Clean
Cc: 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: Mon, 21 May 2012 06:33:02 -0000

Steven Bellovin <smb@cs.columbia.edu> writes:

> Does anyone have any suggestions for additions or corrections to RFC 3631?
> It looks to me like it's held up pretty well, save for newer versions of
> some of the protocols.

I think channel bindings ought to be discussed, as a simple way to bind
different layers together to avoid certain attacks.  It could be
discussed in the SASL or GSS-API section.  Further, I think EAP as a
protocol should be included in the list of standard security mechanisms.

/Simon