[secdir] secdir review of draft-ietf-pim-reserved-bits-03

Dan Harkins <dharkins@lounge.org> Thu, 19 September 2019 19:14 UTC

Return-Path: <dharkins@lounge.org>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDD4A120121; Thu, 19 Sep 2019 12:14:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 cS6fo5gcSayu; Thu, 19 Sep 2019 12:14:17 -0700 (PDT)
Received: from www.goatley.com (www.goatley.com [198.137.202.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EFE78120114; Thu, 19 Sep 2019 12:14:16 -0700 (PDT)
Received: from trixy.bergandi.net (cpe-76-93-158-174.san.res.rr.com [76.93.158.174]) by wwwlocal.goatley.com (PMDF V6.8-0 #1001) with ESMTP id <0PY3001BDERSFH@wwwlocal.goatley.com>; Thu, 19 Sep 2019 14:14:16 -0500 (CDT)
Received: from Dans-MacBook-Pro.local ([69.12.173.8]) by trixy.bergandi.net (PMDF V6.7-x01 #1001) with ESMTPSA id <0PY300IC8EOXNY@trixy.bergandi.net>; Thu, 19 Sep 2019 12:12:35 -0700 (PDT)
Received: from 69-12-173-8.static.dsltransport.net ([69.12.173.8] EXTERNAL) (EHLO Dans-MacBook-Pro.local) with TLS/SSL by trixy.bergandi.net ([10.0.42.18]) (PreciseMail V3.3); Thu, 19 Sep 2019 12:12:35 -0700
Date: Thu, 19 Sep 2019 12:14:13 -0700
From: Dan Harkins <dharkins@lounge.org>
To: "iesg@ietf.org" <iesg@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>, draft-ietf-pim-reserved-bits.all@ietf.org
Message-id: <76082dca-0ffd-452b-42fd-732920b66221@lounge.org>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_Pkfq1q03WF2nC5XAKCq/yw)"
Content-language: en-US
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
X-PMAS-SPF: SPF check skipped for authenticated session (recv=trixy.bergandi.net, send-ip=69.12.173.8)
X-PMAS-External-Auth: 69-12-173-8.static.dsltransport.net [69.12.173.8] (EHLO Dans-MacBook-Pro.local)
X-PMAS-Software: PreciseMail V3.3 [190918] (trixy.bergandi.net)
X-PMAS-Allowed: system rule (rule allow header:X-PMAS-External noexists)
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/7NiexkqSuJAC8M0Nls1ttU7oM-s>
Subject: [secdir] secdir review of draft-ietf-pim-reserved-bits-03
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 19 Sep 2019 19:14:19 -0000

   First of all, I apologize for the tardiness of this review; my bad.
Now onto the boilerplate:

     I have reviewed this document as part of the security directorate's
     ongoing effort to review all IETF documents being processed by the
     IESG.  These comments were written primarily for the benefit of the
     security area directors.  Document editors and WG chairs should treat
     these comments just like any other last call comments.

     The summary of the review is Ready-with-(late)-Nits

The nits are as follows:

   - instead of refering to a bit as the one that "follows" a field or is
     "right in front of" a field I suggest saying the bit is "adjacent"
     to the field.

   - it's not clear how this document updates RFC 6754. Type 11 still has
     8 reserved bits, nothing changes.

The Security Considerations are very light but that seems fine given that
the document is just codifying existing practice (sections 4.1 to 4.4) and
future-proofing (section 5) a limited resource.

   regards,

   Dan.