IETF Logo Mail Archive

Re: [saag] Additions to RFC 3631?

Nico Williams <nico@cryptonector.com> Mon, 21 May 2012 17:20 UTC

Return-Path: <nico@cryptonector.com>
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 7B2DB21F858A for <saag@ietfa.amsl.com>; Mon, 21 May 2012 10:20:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 GvYoMDzv0dR5 for <saag@ietfa.amsl.com>; Mon, 21 May 2012 10:20:23 -0700 (PDT)
Received: from homiemail-a73.g.dreamhost.com (caiajhbdcahe.dreamhost.com [208.97.132.74]) by ietfa.amsl.com (Postfix) with ESMTP id E891D21F854E for <saag@ietf.org>; Mon, 21 May 2012 10:20:22 -0700 (PDT)
Received: from homiemail-a73.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a73.g.dreamhost.com (Postfix) with ESMTP id B3E761F0085 for <saag@ietf.org>; Mon, 21 May 2012 10:20:22 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=cryptonector.com; h=mime-version :in-reply-to:references:date:message-id:subject:from:to:cc: content-type; q=dns; s=cryptonector.com; b=OMMvomkt5gZMNKkAtu9pr CBODv4o8TwFAQapwYGTaZ5qHjRcoiWS6HTLM0n5bIuTH6OBvzKdV66RJCo51f2jp I3dICl02oKxfkrtpLohH/rrDFAqhoUuwcX+FvZnO4ECnRJT9uYCIVV7Na9kzCvNb Lr3sYBbGgLOYVJhFFM9x60=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=tyrjqCPhjI1EfbDbIxAt K9WFuH8=; b=YP4lF31JxQ6VOMAQyuvWRdXk2eWBmGB+ZXZ707S7lr5hPKi1Oaex A/ea40lX4GHSgAmrvlownYbg9eoSWbwuys/1DmHJRNm+DmdzUrFCxgFNrYzXKYyO Z3Qe+JPbs/YEHnx8JOLhoGnMMf+tkyF7XkHR+irYwPE39hQqscnK2n4=
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a73.g.dreamhost.com (Postfix) with ESMTPSA id 8B1601F0083 for <saag@ietf.org>; Mon, 21 May 2012 10:20:22 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so7362023pbc.31 for <saag@ietf.org>; Mon, 21 May 2012 10:20:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.216.33 with SMTP id on1mr70305750pbc.105.1337620822208; Mon, 21 May 2012 10:20:22 -0700 (PDT)
Received: by 10.68.5.99 with HTTP; Mon, 21 May 2012 10:20:22 -0700 (PDT)
In-Reply-To: <4FBA7807.5080207@isi.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> <4FBA7807.5080207@isi.edu>
Date: Mon, 21 May 2012 12:20:22 -0500
Message-ID: <CAK3OfOhp+ic6wtpts2ychqzHMypkwvtWfUQBx6HgCxzHA86ixw@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Joe Touch <touch@isi.edu>
Content-Type: text/plain; charset="UTF-8"
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:20:23 -0000

On Mon, May 21, 2012 at 12:14 PM, Joe Touch <touch@isi.edu> wrote:
> I'd add it - in fact, I would add both BTNS and TCP-AO, since neither are
> covered and both serve different purposes than the mechanisms listed.

And RFC5660.  The problem with that is that BTNS and RFC5660 have not
been implemented, to my knowledge.  Whereas at least CB have been
implemented in SASL and GSS.  Microsoft has implemented and deployed
CB.

Nico
--

v2.23.0 | Report a Bug | By Email