[secdir] Secdir last call review of draft-ietf-rtgwg-bgp-pic-12
Tero Kivinen via Datatracker <noreply@ietf.org> Thu, 17 December 2020 22:21 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 2A42E3A046B; Thu, 17 Dec 2020 14:21:54 -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: draft-ietf-rtgwg-bgp-pic.all@ietf.org, last-call@ietf.org, rtgwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <160824371413.9402.11129595558687198049@ietfa.amsl.com>
Reply-To: Tero Kivinen <kivinen@iki.fi>
Date: Thu, 17 Dec 2020 14:21:54 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/K_dj-zoB7xP3LJQvskeiN5gNCaM>
Subject: [secdir] Secdir last call review of draft-ietf-rtgwg-bgp-pic-12
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: Thu, 17 Dec 2020 22:21:54 -0000
Reviewer: Tero Kivinen Review result: Ready This document describes internal algorithm and structure change for the BGP. The security considerations sections says as follows: The behavior described in this document is internal functionality to a router that result in significant improvement to convergence time as well as reduction in CPU and memory used by FIB while not showing change in basic routing and forwarding functionality. As such no additional security risk is introduced by using the mechanisms proposed in this document. I agree on that statement, but of course this proposed method is bit more complicated than old method, thus there might be more implementation bugs or corner cases than before, but perhaps that is obvious and does not need to be mentioned.
- [secdir] Secdir last call review of draft-ietf-rt… Tero Kivinen via Datatracker