IETF Logo Mail Archive

Re: [saag] Additions to RFC 3631?

Steven Bellovin <smb@cs.columbia.edu> Mon, 21 May 2012 17:59 UTC

Return-Path: <smb@cs.columbia.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 E87D721F85FF for <saag@ietfa.amsl.com>; Mon, 21 May 2012 10:59:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 R0PCATeLyNjY for <saag@ietfa.amsl.com>; Mon, 21 May 2012 10:59:42 -0700 (PDT)
Received: from paneer.cc.columbia.edu (paneer.cc.columbia.edu [128.59.29.4]) by ietfa.amsl.com (Postfix) with ESMTP id 3052321F85E7 for <saag@ietf.org>; Mon, 21 May 2012 10:59:42 -0700 (PDT)
Received: from [192.168.2.166] (74-92-112-54-Philadelphia.hfc.comcastbusiness.net [74.92.112.54]) (user=smb2132 mech=PLAIN bits=0) by paneer.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id q4LHxdRC013087 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 21 May 2012 13:59:39 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset="us-ascii"
From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <CAK3OfOj=jR4R+hBDTcv-DNqqU0AdHHonSTOmsMpR3ZqmhDmbdQ@mail.gmail.com>
Date: Mon, 21 May 2012 13:59:38 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <416327B2-6E60-4D09-B3E7-D314F4FDD4E1@cs.columbia.edu>
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>
To: Nico Williams <nico@cryptonector.com>
X-Mailer: Apple Mail (2.1278)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.4
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: Mon, 21 May 2012 17:59:43 -0000

On May 21, 2012, at 1:06 49PM, Nico Williams wrote:

> On Mon, May 21, 2012 at 11:42 AM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
>> +1 to adding EAP as a mechanism.
>> 
>> +/-0 to adding channel bindings, given how few people understand them.
> 
> EIther it's important/useful or not.  If it is then having some text
> in this RFC would help those people who don't understand CB.
> 
I agree.


		--Steve Bellovin, https://www.cs.columbia.edu/~smb

v2.23.0 | Report a Bug | By Email