[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

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
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

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