Re: [saag] Additions to RFC 3631?
Nico Williams <nico@cryptonector.com> Wed, 23 May 2012 14:13 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 EE83321F8694 for <saag@ietfa.amsl.com>; Wed, 23 May 2012 07:13:39 -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 T1tRJBKHK4Ed for <saag@ietfa.amsl.com>; Wed, 23 May 2012 07:13:39 -0700 (PDT)
Received: from homiemail-a16.g.dreamhost.com (caiajhbdccac.dreamhost.com [208.97.132.202]) by ietfa.amsl.com (Postfix) with ESMTP id 7947E21F86F7 for <saag@ietf.org>; Wed, 23 May 2012 07:13:39 -0700 (PDT)
Received: from homiemail-a16.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a16.g.dreamhost.com (Postfix) with ESMTP id 8A20E508082 for <saag@ietf.org>; Wed, 23 May 2012 07:13:38 -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=oJXc8MyZGAQoXZLzOgwO1 73pnyDH/aIjLorLEj3afie3XxrbrkP0Aw9S1vY48D4JZeRTUGdU/F9HgxPeyoTar 3rBrlEKyr6egi7Yxmb7ODOcpmfrkSXvxZajuUbxdQ/GjOXlYPm090A0KqnfYGehq uFZO5mvujvP5bpLhMLFEQM=
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=6zMfVa5TDd9MGw3qMI7m MvdZybw=; b=qBt6INilZYCApkJxUgjv9wKaXUyK5BMYVsJWTDayd6mMVad9Jtc4 szYF+PKd4Qrqu5GHzRsn/dT3FWVYJM25itLcQoHna7m/mQQnzgz0Vj3nE4ai8pPU +uYN1xMPCBws46kM3oKTD2Yx3jmDGXMfeaIjkp2UnVftYfYfB/a7arE=
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-a16.g.dreamhost.com (Postfix) with ESMTPSA id 3521950807D for <saag@ietf.org>; Wed, 23 May 2012 07:13:38 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so10185558pbc.31 for <saag@ietf.org>; Wed, 23 May 2012 07:13:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.213.71 with SMTP id nq7mr1201847pbc.7.1337782417095; Wed, 23 May 2012 07:13:37 -0700 (PDT)
Received: by 10.68.15.134 with HTTP; Wed, 23 May 2012 07:13:37 -0700 (PDT)
In-Reply-To: <20120523124200.17700@gmx.net>
References: <300A2E9F-E99B-46FA-A101-E3611BD0D197@cs.columbia.edu> <20120523124200.17700@gmx.net>
Date: Wed, 23 May 2012 09:13:37 -0500
Message-ID: <CAK3OfOhEq72GqWDyXHW0CQBC-RC4XYpsjhRDh0+qbVpLyDoGTQ@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
Content-Type: text/plain; charset="UTF-8"
Cc: 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: Wed, 23 May 2012 14:13:40 -0000
On Wed, May 23, 2012 at 7:42 AM, Hannes Tschofenig <Hannes.Tschofenig@gmx.net> wrote: > to me it is not clear who the target audience of the document is and what purpose it serves. One target audience would clearly be those who don't wallow in the security area. There's probably an unstated purpose of simple advertising, and maybe to have a tool to beat others with (ISTR someone trying to argue from absence of some definition in the security glossary, that is, using the security glossary as an authority). Perhaps this document can serve as a summary applicability statement, say. There is a risk is that we'll all just argue endlessly about various details, possibly leading to a bloated document. But it does seem like a nice idea: to have a guide to an entire area's past output. Nico --
- Re: [saag] Additions to RFC 3631? Yaron Sheffer
- Re: [saag] Additions to RFC 3631? Eliot Lear
- Re: [saag] Additions to RFC 3631? Mouse
- Re: [saag] Additions to RFC 3631? Simon Josefsson
- [saag] Additions to RFC 3631? Steven Bellovin
- Re: [saag] Additions to RFC 3631? Mouse
- Re: [saag] Additions to RFC 3631? Simon Josefsson
- Re: [saag] Additions to RFC 3631? Stephen Farrell
- Re: [saag] Additions to RFC 3631? Yaron Sheffer
- Re: [saag] Additions to RFC 3631? Eliot Lear
- Re: [saag] Additions to RFC 3631? Steven Bellovin
- Re: [saag] Additions to RFC 3631? Paul Hoffman
- Re: [saag] Additions to RFC 3631? Nico Williams
- Re: [saag] Additions to RFC 3631? Joe Touch
- Re: [saag] Additions to RFC 3631? Nico Williams
- Re: [saag] Additions to RFC 3631? Nico Williams
- Re: [saag] Additions to RFC 3631? Steven Bellovin
- Re: [saag] Additions to RFC 3631? Nico Williams
- Re: [saag] Additions to RFC 3631? Tschofenig, Hannes (NSN - FI/Espoo)
- Re: [saag] Additions to RFC 3631? Steven Bellovin
- Re: [saag] Additions to RFC 3631? Yaron Sheffer
- Re: [saag] Additions to RFC 3631? Nico Williams
- Re: [saag] Additions to RFC 3631? Jeffrey Hutzelman
- Re: [saag] Additions to RFC 3631? Joe Touch
- Re: [saag] Additions to RFC 3631? Hannes Tschofenig
- Re: [saag] Additions to RFC 3631? Nico Williams
- Re: [saag] Additions to RFC 3631? Steven Bellovin
- Re: [saag] Additions to RFC 3631? Tschofenig, Hannes (NSN - FI/Espoo)
- Re: [saag] Additions to RFC 3631? Steve Crocker
- Re: [saag] Additions to RFC 3631? Tschofenig, Hannes (NSN - FI/Espoo)