IETF Logo Mail Archive

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

Sam Hartman <hartmans-ietf@mit.edu> Fri, 08 May 2009 01:49 UTC

Return-Path: <hartmans@mit.edu>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 055583A7042; Thu, 7 May 2009 18:49:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.278
X-Spam-Level:
X-Spam-Status: No, score=-2.278 tagged_above=-999 required=5 tests=[AWL=-0.013, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 BLYc+BBZDXxZ; Thu, 7 May 2009 18:49:18 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) by core3.amsl.com (Postfix) with ESMTP id 410C63A7031; Thu, 7 May 2009 18:49:18 -0700 (PDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id EFB854163; Thu, 7 May 2009 21:50:40 -0400 (EDT)
To: "David B. Nelson" <dnelson@elbrysnetworks.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> <DD929100D04E45C1BAD655F69E35F0C6@xpsuperdvd2>
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Thu, 07 May 2009 21:15:47 -0400
In-Reply-To: <DD929100D04E45C1BAD655F69E35F0C6@xpsuperdvd2> (David B. Nelson's message of "Tue\, 5 May 2009 16\:07\:48 -0400")
Message-ID: <tslk54sl7i4.fsf@mit.edu>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: 'David B Harrington' <dbharrington@comcast.net>, isms@ietf.org, secdir@ietf.org, isms-chairs@tools.ietf.org, iesg@ietf.org, 8 'Barry Leiba' <barryleiba@computer.org>, draft-ietf-isms-transport-security-model@tools.ietf.org, 'Jeffrey Hutzelman' <jhutz@cmu.edu>
Subject: Re: [Isms] [secdir] secdir review of draft-ietf-isms-transport-security-model-12
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 May 2009 01:49:19 -0000

>>>>> "David" == David B Nelson <dnelson@elbrysnetworks.com> writes:

    David> David B Harrington writes...
    >> What is the correct non-RFC2119 phrase in which to couch our
    >> deployment advice?

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

8
    David> _______________________________________________ secdir
    David> mailing list secdir@ietf.org
    David> https://www.ietf.org/mailman/listinfo/secdir

Or just use lower case should.  I think the advice is important enough
it does not belong in an appendix.

v2.23.0 | Report a Bug | By Email