[Bier] Secdir last call review of draft-ietf-bier-ospfv3-extensions-07

Vincent Roca via Datatracker <noreply@ietf.org> Tue, 06 February 2024 16:03 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: bier@ietf.org
Delivered-To: bier@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D59AC151983; Tue, 6 Feb 2024 08:03:59 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Vincent Roca via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
Cc: bier@ietf.org, draft-ietf-bier-ospfv3-extensions.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.4.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <170723543910.465.12847857146852633912@ietfa.amsl.com>
Reply-To: Vincent Roca <vincent.roca@inria.fr>
Date: Tue, 06 Feb 2024 08:03:59 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/zTscc-t6Hw9BO1E30e9f5Lw39jI>
Subject: [Bier] Secdir last call review of draft-ietf-bier-ospfv3-extensions-07
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.39
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <bier.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bier>, <mailto:bier-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bier/>
List-Post: <mailto:bier@ietf.org>
List-Help: <mailto:bier-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bier>, <mailto:bier-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Feb 2024 16:03:59 -0000

Reviewer: Vincent Roca
Review result: Ready

Hello,

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.

Summary: Ready

I have no particular secdir-related comment for this document.
The "Security Considerations" section is well documented and understandable.

However I have a few extra comments for this ID, totally disconnected from this
secdir review:

- s/is/are/ in: "Existing security concerns documented in [RFC8362] is
applicable" - s/is/are/ in: "both BIER and OSPF layer is under a single
administrative domain" - Question: in section 2.2, only the lowest 20 bits of
the "Label" field are used ("The 4 leftmost bits MUST be ignored."), whereas
there is an extra 4-bit field, "BS Len". Why not shrinking a bit field "Label"
and moving "BS Len" there to save 4 extra bytes in this sub-TLV? There's
probably a good reason not to do so, but nothing is said. - Comment: field
"Reserved" is discussed in section 2.2, but nothing is said about "Reserved" in
section 2.1.

Regards,    Vincent