Iotdir last call review of draft-ietf-rtgwg-bgp-pic-12

Ines Robles via Datatracker <noreply@ietf.org> Sun, 17 January 2021 20:57 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: rtgwg@ietf.org
Delivered-To: rtgwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C99393A03FB; Sun, 17 Jan 2021 12:57:38 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Ines Robles via Datatracker <noreply@ietf.org>
To: iot-directorate@ietf.org
Cc: draft-ietf-rtgwg-bgp-pic.all@ietf.org, last-call@ietf.org, rtgwg@ietf.org
Subject: Iotdir last call review of draft-ietf-rtgwg-bgp-pic-12
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <161091705878.30489.6097804261671946160@ietfa.amsl.com>
Reply-To: Ines Robles <mariainesrobles@googlemail.com>
Date: Sun, 17 Jan 2021 12:57:38 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/jU3aJrFZdnidWxCwEAZ_pkH5Wcw>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Jan 2021 20:57:39 -0000

Reviewer: Ines Robles
Review result: Ready with Nits

This document proposes a hierarchical and shared forwarding chain  organization
that allows traffic to be restored to pre-calculated  alternative equal cost
primary path or backup path in a time period that does not depend on the number
of BGP prefixes.

Comment/Question to the authors:
1- In the document states: "The proposed technique achieves prefix independent
convergence while ensuring incremental deployment, complete automation, and
zero management and provisioning effort." What is the scope involved in zero
management? It would be nice if the text explains how the technique achieves
the zero management and the provisioning efforts. 2- "it benefits from all its
benefits" --> it would be nice to mention some of the benefits in brakets. 3-
Is this technique not affected by any type of bpg prefix hijacking attack? 4-
If there is no privacy issues I would states that explicitly.

Thank you for this document,

Ines.