Re: New Version Notification for draft-leiba-rfc2119-update-00.txt

Stewart Bryant <stewart.bryant@gmail.com> Thu, 11 August 2016 11:44 UTC

Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5CC212D123 for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2016 04:44:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hJowhgbxDdIW for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2016 04:44:28 -0700 (PDT)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A798212D0CA for <ietf@ietf.org>; Thu, 11 Aug 2016 04:44:27 -0700 (PDT)
Received: by mail-wm0-x230.google.com with SMTP id o80so10193856wme.1 for <ietf@ietf.org>; Thu, 11 Aug 2016 04:44:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=aF6RsF52nk5t9b7hMAAO05/cBBE3jt11rZCjYAD1KhA=; b=m9wqOXGDRloW2BlRKmFoR55BE8DruzuaVH16hSDAlI6/IcfIavykr2bPDecK4/YGws ilfRfRmahT9Pi/zV5N+9IiuMRfTnSZzNUsI02SeE1nGycKXIWmVmLmRIMV11U6gTxjfV kTEMTeWZXGRgG1MSYak6Fwfn13RhNlQMpDn7Fuljrx5UqrQKaMGCrEYsu+6AIQhJcSpI h2xKGMRvy1CkQETWSQzbCetohNlR0cauoXpuGn5q6EosLUWtouOXKDEkWW+HZIXpVrEL PbziOgYeWATySYl5IfIhfr2aH0dtwECO/QiBhzImu3Fz6Xa2Vj36nrhQZpGTRLcDqVns nhug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=aF6RsF52nk5t9b7hMAAO05/cBBE3jt11rZCjYAD1KhA=; b=fKcSiP3FKp1vRL2XunJi+tM8eGHS95rCKNCuCLuX4NmTKVhGahz8PqA8EBpeDUuHQk TA2dLsZq6iHlSpS0dqtByY5BMTXaydpH6MXhJovY7rpXhVgGfOrOl3HI9URy4pJ9blDo yGVxrkaVSfATZlxC8plIsUPzDPPg5HLCki6BrtcuddR8pn8OEzuwHbvKatKBtP+FN5tm V9ys7U1ffpKrnfThIw7YqsWFKQ9rdECE7kZNcp8B6c2l+cEmJolxmV+UHJJXBpZRLPHZ QdIEK8ioGhNrhcYRrMrUeNtSb9h19lBa2pt2I0OzxCMQf3fryIWkFWJjD3Ne7uCBtLXE bhKg==
X-Gm-Message-State: AEkoouuPS5+zHXVP4/L3stHu9HxWGlC94nB7i1PvKpvTt8hobhG1ZMYnYsK7uh6JaeO/fw==
X-Received: by 10.28.74.221 with SMTP id n90mr8317000wmi.16.1470915865690; Thu, 11 Aug 2016 04:44:25 -0700 (PDT)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id 190sm2814747wmk.13.2016.08.11.04.44.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Aug 2016 04:44:24 -0700 (PDT)
Subject: Re: New Version Notification for draft-leiba-rfc2119-update-00.txt
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>, Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
References: <147077254472.30640.13738163813175851232.idtracker@ietfa.amsl.com> <CALaySJLHx7ytgZqZ9zQXA3vVSU-pNggQQs+QiDnzQ4tBEH5VAQ@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D9240CC47@GLKXM0002V.GREENLNK.net>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <f30c2fb9-2f84-4ff1-8bd2-f70fe4201838@gmail.com>
Date: Thu, 11 Aug 2016 12:44:23 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D9240CC47@GLKXM0002V.GREENLNK.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/--qRkwaF3WmPprsbje4aTBmCqN4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2016 11:44:29 -0000

Optional is useful in a requirements RFC.

Feature x is REQUIRED

Feature y is OPTIONAL

- Stewart


On 11/08/2016 12:27, Dearlove, Christopher (UK) wrote:
> Grammatically, RECOMMENDED is sometimes useful, as using SHOULD instead can produce less clear sentences. In principal the same applies to OPTIONAL, but I've never had cause to use it.
>
> I wouldn't miss SHALL. Except that SHALL is often the word used outside the IETF rather than must, and there may be many RFCs using it, so do need to keep the explanation, even if deprecated to use it in new documents.
>