IETF Logo Mail Archive

[saag] Additions to RFC 3631?

Steven Bellovin <smb@cs.columbia.edu> Sat, 19 May 2012 02:31 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 E084121F866A for <saag@ietfa.amsl.com>; Fri, 18 May 2012 19:31:45 -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 7U3LMJhIFpRv for <saag@ietfa.amsl.com>; Fri, 18 May 2012 19:31:45 -0700 (PDT)
Received: from rambutan.cc.columbia.edu (rambutan.cc.columbia.edu [128.59.29.5]) by ietfa.amsl.com (Postfix) with ESMTP id 4166921F8661 for <saag@ietf.org>; Fri, 18 May 2012 19:31:42 -0700 (PDT)
Received: from [192.168.2.180] (74-92-112-54-Philadelphia.hfc.comcastbusiness.net [74.92.112.54]) (user=smb2132 mech=PLAIN bits=0) by rambutan.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id q4J2Vdgn028161 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <saag@ietf.org>; Fri, 18 May 2012 22:31:40 -0400 (EDT)
From: Steven Bellovin <smb@cs.columbia.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Date: Fri, 18 May 2012 22:31:39 -0400
Message-Id: <300A2E9F-E99B-46FA-A101-E3611BD0D197@cs.columbia.edu>
To: IETF Security Area Advisory Group <saag@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.5
Subject: [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: Sat, 19 May 2012 02:31:46 -0000

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.

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

v2.23.0 | Report a Bug | By Email