Re: [secdir] [Isms] secdir review ofdraft-ietf-isms-transport-security-model-12
Barry Leiba <barryleiba@computer.org> Tue, 05 May 2009 20:02 UTC
Return-Path: <barryleiba@gmail.com>
X-Original-To: secdir@core3.amsl.com
Delivered-To: secdir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4ABC33A67EA; Tue, 5 May 2009 13:02:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.14
X-Spam-Level:
X-Spam-Status: No, score=-2.14 tagged_above=-999 required=5 tests=[AWL=-0.163, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id waff0qxjJ8YL; Tue, 5 May 2009 13:02:29 -0700 (PDT)
Received: from mail-ew0-f224.google.com (mail-ew0-f224.google.com [209.85.219.224]) by core3.amsl.com (Postfix) with ESMTP id E61E728C16E; Tue, 5 May 2009 13:02:28 -0700 (PDT)
Received: by ewy24 with SMTP id 24so5347919ewy.37 for <multiple recipients>; Tue, 05 May 2009 13:03:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=sv8oTgEQ8oMuiDWDkPQWplPFflqJ6w8ydcDEHTONgFw=; b=J/7+wVj1L+Onocd0Zc5KbKCizEEO5DmK8Eo8iUyjEckkECv54aMSW1qU3q4rB/4RGZ DSTxNwbtf4HjWyI5Xwis7e7lNcCddR0bUuPhyGDjd+KaNabt8tJtHa8AeX2CQx/OY+WA CbE2ujOUBeMQxQtUgXvFR5xUNKUuS34ku4Lzc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=BWbHu/a5dBvf2VYE2eKYD1436ydCCSqJcpN8cW6aqt/7S4SC8LDwviMLJUv2aoqK3k tgd9RYoOoz05cI8fBWhy4z7dlrF8ZnDme3YdyQ7NG84Zth74ov3jV0SEuH2YBqzmlIhQ LUSNUccrsFT1U8PMKAaeCacuxtv/B6fQh7faI=
MIME-Version: 1.0
Sender: barryleiba@gmail.com
Received: by 10.211.137.19 with SMTP id p19mr5023185ebn.69.1241553832236; Tue, 05 May 2009 13:03:52 -0700 (PDT)
In-Reply-To: <06a701c9cdb7$aed00f30$0600a8c0@china.huawei.com>
References: <6c9fcc2a0905021333j3dd58821v4726af092e30c1c1@mail.gmail.com> <200905051750.n45HorPw023985@mx02.srv.cs.cmu.edu> <0FBA56D16F71437450BC2779@minbar.fac.cs.cmu.edu> <06a701c9cdb7$aed00f30$0600a8c0@china.huawei.com>
Date: Tue, 05 May 2009 16:03:52 -0400
X-Google-Sender-Auth: 8ab2eb4451dce772
Message-ID: <9abf48a60905051303h1543f323u1a8e3679445384f6@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: David B Harrington <dbharrington@comcast.net>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 05 May 2009 22:53:27 -0700
Cc: isms@ietf.org, iesg@ietf.org, isms-chairs@tools.ietf.org, secdir@ietf.org
Subject: Re: [secdir] [Isms] secdir review ofdraft-ietf-isms-transport-security-model-12
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 May 2009 20:02:30 -0000
> That is a deployment decision made by an administrator who has an > understanding of what is appropriate to the system in question. > > What is the correct non-RFC2119 phrase in which to couch our > deployment advice? Well, this would make me happy; would it work for you (and others)?: OLD: by the RFC 3411 architecture. However, the Transport Security Model does not provide security mechanisms such as authentication and encryption itself, so it SHOULD always be used with a Transport Model that provides appropriate security. Which threats are addressed and how they are mitigated depends on the Transport Model. NEW: by the RFC 3411 architecture. However, the Transport Security Model does not provide security mechanisms such as authentication and encryption itself, so it MUST always be used with a Transport Model that provides appropriate security. What is "appropriate" for a particular deployment is an administrative decision. Which threats are addressed and how they are mitigated depends on the Transport Model. Barry
- [secdir] secdir review of draft-ietf-isms-transpo… Barry Leiba
- Re: [secdir] secdir review ofdraft-ietf-isms-tran… David B Harrington
- Re: [secdir] [Isms] secdir review ofdraft-ietf-is… Jeffrey Hutzelman
- Re: [secdir] [Isms] secdir review ofdraft-ietf-is… David B Harrington
- Re: [secdir] [Isms] secdir review ofdraft-ietf-is… Jeffrey Hutzelman
- Re: [secdir] [Isms] secdir review ofdraft-ietf-is… David B Harrington
- Re: [secdir] [Isms] secdir review ofdraft-ietf-is… Barry Leiba
- Re: [secdir] [Isms] secdirreview ofdraft-ietf-ism… Randy Presuhn
- Re: [secdir] [Isms] secdir review ofdraft-ietf-is… Glen Zorn
- Re: [secdir] [Isms] secdir review ofdraft-ietf-is… Juergen Schoenwaelder
- Re: [secdir] [Isms] secdir review of draft-ietf-i… David B. Nelson
- Re: [secdir] [Isms] secdir review of draft-ietf-i… Sam Hartman
- Re: [secdir] [Isms] secdir review of draft-ietf-i… Barry Leiba
- Re: [secdir] [Isms] secdir reviewofdraft-ietf-ism… Barry Leiba
- Re: [secdir] [Isms] secdir reviewofdraft-ietf-ism… Juergen Schoenwaelder
- Re: [secdir] [Isms] secdirreviewofdraft-ietf-isms… David Harrington
- Re: [secdir] [Isms] secdirreviewofdraft-ietf-isms… David Harrington
- Re: [secdir] [Isms] secdir reviewofdraft-ietf-ism… David Harrington
- Re: [secdir] [Isms] secdir reviewofdraft-ietf-ism… tom.petch
- Re: [secdir] [Isms] secdir reviewofdraft-ietf-ism… tom.petch
- Re: [secdir] secdir reviewofdraft-ietf-isms-trans… Wes Hardaker
- Re: [secdir] secdir reviewofdraft-ietf-isms-trans… Wes Hardaker
- Re: [secdir] [Isms] secdirreviewofdraft-ietf-isms… tom.petch