IETF Logo Mail Archive

[IETFMIBS] Formatted Text of Security Guidelines for IETF MIB Modules

Hiroshi Tsunoda <tsuno@m.ieice.org> Wed, 03 October 2018 06:43 UTC

Return-Path: <dr.h.t@ieee.org>
X-Original-To: ietfmibs@ietfa.amsl.com
Delivered-To: ietfmibs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60B92131203 for <ietfmibs@ietfa.amsl.com>; Tue, 2 Oct 2018 23:43:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.651
X-Spam-Level:
X-Spam-Status: No, score=-1.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 H4kS9LN4BIDz for <ietfmibs@ietfa.amsl.com>; Tue, 2 Oct 2018 23:43:44 -0700 (PDT)
Received: from mail-lf1-f47.google.com (mail-lf1-f47.google.com [209.85.167.47]) (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 081B4131090 for <ietfmibs@ietf.org>; Tue, 2 Oct 2018 23:43:43 -0700 (PDT)
Received: by mail-lf1-f47.google.com with SMTP id o21-v6so3293396lfe.0 for <ietfmibs@ietf.org>; Tue, 02 Oct 2018 23:43:43 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=4kD4a/iqU5rTKan6+Dv7+kvKvMCtb+6bEz6A5tDAX3s=; b=f+ZuNPWQFNfNJpSUjxiMzwJzRYA9dQ3hTZKPO5d1KbFXmMaOzusosJ22xU9TK/UUwh Emdo3YK3eqIaEpK4CaXUN2PMFEGp3lznti2L66C5/q7YHQdFoXMASASEBSWZQFMm7UTY n+h02cxQAIK8d8XEnVr7tyGUfrlbM96e1YlLpv+e6mkd5Z8s4S32AqkIwZF3arPTP/EJ oslivKq2fXeBwjM+49WdYvjdoyjToUUoMRFxXqY67UdGc1N+aEWFWbYwKnYxuloxk1Ee 3vWQeMYc32Jc+UBQYaNzpVKtj0/4pGONsGwN4o30GTEZL41z0ihZWeaubjOsPqcUH+0n sphQ==
X-Gm-Message-State: ABuFfoj7s8wnwINgEIK4IFcktfx003aycm/kQem48o64PIlcaVQgUVll AaNwxQEhn4HehrzAjECNTBoOOmJMKuN2DLbHIrzDEJWGf6E=
X-Google-Smtp-Source: ACcGV61F/XLZytMbi6DGkrQ22QGm60tPZwUlukZ0wPN1P9vE9Nq8HRIzmHB0Q9g4ozzcKHCS7LdQG3vIfgvBO+f7doY=
X-Received: by 2002:a19:d824:: with SMTP id p36-v6mr45188lfg.23.1538549021919; Tue, 02 Oct 2018 23:43:41 -0700 (PDT)
MIME-Version: 1.0
From: Hiroshi Tsunoda <tsuno@m.ieice.org>
Date: Wed, 03 Oct 2018 15:43:06 +0900
Message-ID: <CAPbjwky66vuaPm2Pv5GvFdveggNzY6EEmU2Soyy-uCwypJ25=g@mail.gmail.com>
To: ietfmibs@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietfmibs/1T3fNJIe67-IXNwVYBtY9gHVUmc>
Subject: [IETFMIBS] Formatted Text of Security Guidelines for IETF MIB Modules
X-BeenThere: ietfmibs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF MIB Discussion list <ietfmibs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietfmibs>, <mailto:ietfmibs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietfmibs/>
List-Post: <mailto:ietfmibs@ietf.org>
List-Help: <mailto:ietfmibs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietfmibs>, <mailto:ietfmibs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Oct 2018 06:43:46 -0000

Hi,

I think that https://trac.ietf.org/trac/ops/wiki/mib-security needs to be
updated so that it refers RFC8174 which updates RFC2119.
RFC8174 gives the new phrase to specifies common key words.

Concretely speaking, the beginning of  "Formatted Text" needs to be
updated as follows.

----------------------------------------------------------------------------------------------------------
<OLD>
   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
   this document are to be interpreted as described in BCP 14,
   RFC 2119 [RFC2119].

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
   in this document are to be interpreted as described in [KEYWORDS].

  [KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <http://www.rfc-editor.org/info/rfc2119>.
----------------------------------------------------------------------------------------------------------
<NEW>
   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
   NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",
   "NOT RECOMMENDED",  "MAY", and "OPTIONAL" in this document are
   to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when,
   and only when, they appear in all capitals, as shown here.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
              RFC2119, March 1997, <https://www.rfc-editor.org/info/
              rfc2119>.

   [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
              2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
              May 2017, <https://www.rfc-editor.org/info/rfc8174>.
----------------------------------------------------------------------------------------------------------

Thanks,

-- tsuno

v2.23.0 | Report a Bug | By Email