[secdir] Secdir last call review of draft-ietf-babel-v4viav6-07

Tero Kivinen via Datatracker <noreply@ietf.org> Wed, 02 February 2022 00:07 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: secdir@ietf.org
Delivered-To: secdir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C16863A1715; Tue, 1 Feb 2022 16:07:40 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Tero Kivinen via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
Cc: babel@ietf.org, draft-ietf-babel-v4viav6.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.44.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <164376046073.3024.11843958658714304588@ietfa.amsl.com>
Reply-To: Tero Kivinen <kivinen@iki.fi>
Date: Tue, 01 Feb 2022 16:07:40 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/aeTz_o-b2j71Pu_13Q_Ao6P45jk>
Subject: [secdir] Secdir last call review of draft-ietf-babel-v4viav6-07
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 02 Feb 2022 00:07:41 -0000

Reviewer: Tero Kivinen
Review result: Ready

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.

This document specifies how to add extensions to Babel routing protocol 
so that it can route IPv4 packets over network core without IPv4 addresses.

Its security considerations section do mention the fact that this feature 
might invalidate the assumptions made by the network administrators, and 
suggest packet filters to mitigate this issue. I think the current security
considerations section covers issues caused by this extension.