IETF Logo Mail Archive

Re: [secdir] [Isms] secdir review of draft-ietf-isms-transport-security-model-12

"David B. Nelson" <dnelson@elbrysnetworks.com> Thu, 07 May 2009 21:06 UTC

Return-Path: <dnelson@elbrysnetworks.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 D8E8B3A6802 for <secdir@core3.amsl.com>; Thu, 7 May 2009 14:06:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.623
X-Spam-Level:
X-Spam-Status: No, score=-0.623 tagged_above=-999 required=5 tests=[AWL=-0.624, BAYES_50=0.001]
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 0dAG+w9-uzF1 for <secdir@core3.amsl.com>; Thu, 7 May 2009 14:06:39 -0700 (PDT)
Received: from gumby.elbrysnetworks.com (mail.elbrysnetworks.com [64.140.243.164]) by core3.amsl.com (Postfix) with SMTP id 3D4823A68A0 for <secdir@ietf.org>; Thu, 7 May 2009 14:06:21 -0700 (PDT)
Received: (qmail 19308 invoked from network); 5 May 2009 16:07:46 -0400
Received: from xpsuperdvd2.elbrysnetworks.com (HELO xpsuperdvd2) (172.22.18.93) by gumby.elbrysnetworks.com with SMTP; 5 May 2009 16:07:46 -0400
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
To: 'David B Harrington' <dbharrington@comcast.net>, 'Jeffrey Hutzelman' <jhutz@cmu.edu>, 'Barry Leiba' <barryleiba@computer.org>, secdir@ietf.org, iesg@ietf.org
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:07:48 -0400
Organization: Elbrys Networks, Inc.
Message-ID: <DD929100D04E45C1BAD655F69E35F0C6@xpsuperdvd2>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
In-Reply-To: <06a701c9cdb7$aed00f30$0600a8c0@china.huawei.com>
Thread-Index: AcnNtSYsrMOk66M4RPGOpg+msofHJgAAhTKAAAFePSA=
X-Mailman-Approved-At: Thu, 07 May 2009 14:17:47 -0700
Cc: draft-ietf-isms-transport-security-model@tools.ietf.org, isms@ietf.org, isms-chairs@tools.ietf.org
Subject: Re: [secdir] [Isms] secdir review of draft-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: Thu, 07 May 2009 21:06:39 -0000

David B Harrington writes...

> What is the correct non-RFC2119 phrase in which to
> couch our deployment advice?

One suitable strategy would be to include any "advice to operators" in a
non-normative section or appendix, clearly labeled as non-normative.  I
don't think the "keyword police" will bother with non-normative text.  :-)

v2.23.0 | Report a Bug | By Email