Re: [Idr] WG LC on draft-ietf-idr-rpd-05.txt (7/15 to 7/29/2020)

Gert Doering <gert@space.net> Tue, 28 July 2020 06:20 UTC

Return-Path: <gert@space.net>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D67A93A0CE0 for <idr@ietfa.amsl.com>; Mon, 27 Jul 2020 23:20:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=space.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BL5oyfNtrcs8 for <idr@ietfa.amsl.com>; Mon, 27 Jul 2020 23:20:25 -0700 (PDT)
Received: from gatekeeper1-relay.space.net (gatekeeper1-relay.space.net [IPv6:2001:608:3:85::38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7AA9C3A0CDB for <idr@ietf.org>; Mon, 27 Jul 2020 23:20:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=space.net; i=@space.net; q=dns/txt; s=esa; t=1595917224; x=1627453224; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=9hhDX+rhM6MZdGPW/cbUDgnamok7sVHZcDD8RkgJu8w=; b=Z1aP9gMHKSyPZ/RsFstqPvuvSl13BM9I3jEhTtv0dOHOYjy90K3bI//D xzGkmGXD5GV2seklC0W+dfrnKNMLEZfMLvhcf9sGHsB/BLMcTBT5T4usT guaGofIDK/h7OoWvwF+WtBDFWa1kGrCXxeqPxjQs2G9OPNX7nwu7O2zaa EAFQBOgyCA/UJ2r+j6dbfjqdDtC0gWjRQItC1f4ER7rIaDd08ThV/mS5q faxzHO0wNthVeubO1XnB1EXGj3egAYXHQoN+dRIqijk808gpxs7OexG+7 WutXRUG1Su+H8GAt8V1lvpedvyX746Gk4Qr/XbydgBvA0tQ5aLWs/mT+F Q==;
IronPort-SDR: Cy03O2WY698K2Nv37eccTyuQKuX+hw9FR8upE1YiujK1DzlONgRvIJJIS0SDu61+n13yt7Rymm Wc8zESZyqpFSDFxa3/owIZnG80LaoF/ttOdKavnHxGzB3DoTzFfLApEKus6bhsSz7q3uYklo5Y 8ydsz6HtM/tu6zO1qbOEFfh3sbHRUz7ngmDwp8+1qPQq9E4r7ytZZY7sForOvR+pz9Y3udF+1A Oj4RW2hwXxrJFviMGM7ETHQiSKhDEECvuSXzTShknnxJAB0hzmGxLuy+/M/6z3AeGdAxQPb3Pc p4Q=
X-SpaceNet-SBRS: None
Received: from mobil.space.net ([195.30.115.67]) by gatekeeper1-relay.space.net with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Jul 2020 08:20:11 +0200
X-Original-To: idr@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id A059541C02 for <idr@ietf.org>; Tue, 28 Jul 2020 08:20:11 +0200 (CEST)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 86C08418BA; Tue, 28 Jul 2020 08:20:11 +0200 (CEST)
Received: by moebius4.space.net (Postfix, from userid 1007) id 7FC3F2207A; Tue, 28 Jul 2020 08:20:11 +0200 (CEST)
Date: Tue, 28 Jul 2020 08:20:11 +0200
From: Gert Doering <gert@space.net>
To: Huaimo Chen <huaimo.chen@futurewei.com>
Cc: "Ketan Talaulikar (ketant)" <ketant=40cisco.com@dmarc.ietf.org>, Robert Raszuk <robert@raszuk.net>, Susan Hares <shares@ndzh.com>, "idr@ietf. org" <idr@ietf.org>
Message-ID: <20200728062011.GL2485@Space.Net>
References: <003701d65aa9$689a64d0$39cf2e70$@ndzh.com> <CAOj+MMGG6usHpQrn020LwWd7obt8PRPk9oii1drk0UPhyG5_gw@mail.gmail.com> <MW3PR11MB457041054724225FB0DEB25DC1760@MW3PR11MB4570.namprd11.prod.outlook.com> <MN2PR13MB3117CEF5726D2711D21C97BBF2720@MN2PR13MB3117.namprd13.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <MN2PR13MB3117CEF5726D2711D21C97BBF2720@MN2PR13MB3117.namprd13.prod.outlook.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/oUaMlWQMWEcFlf9jlcSOX2p9i98>
Subject: Re: [Idr] WG LC on draft-ietf-idr-rpd-05.txt (7/15 to 7/29/2020)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jul 2020 06:20:28 -0000

Hi,

On Mon, Jul 27, 2020 at 08:57:22PM +0000, Huaimo Chen wrote:
>      *   How does the controller or provisioning entity know the status of the Route Policy provisioning on the target router. Even that it was successfully propagated to it and installed on it?
> 
> [HC]:  It seems that BGP protocols guarantees the BGP UPDATE with the 
> route policy reaches the target router. When a BGP speaker as a 
> controller sends a BGP UPDATE to a peer, there is no need for the ack 
> from the peer about whether it is received, processed, and installed. 

This sounds as if the controller would have / need to have a direct BGP 
session to each of the target routers.

Which makes the use of BGP as transport protocol even more a bad choice.

If you have point-to-point connections anyway, do not choose a transport
protocol that is built for "distribute information to devices many hops 
away".


Do not stuff BGP with more stuff that is not related to "transport of
routing information".  Vendors are having a hard time building robust and
interoperable BGP implementations already today.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279