Re: [Idr] 答复: WG adoption call for draft-xu-idr-neighbor-autodiscovery

Robert Raszuk <robert@raszuk.net> Tue, 17 July 2018 13:09 UTC

Return-Path: <rraszuk@gmail.com>
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 9D7E7130DC7; Tue, 17 Jul 2018 06:09:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level:
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 MLw7cNuLJqCu; Tue, 17 Jul 2018 06:09:49 -0700 (PDT)
Received: from mail-pf0-x22d.google.com (mail-pf0-x22d.google.com [IPv6:2607:f8b0:400e:c00::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46D1B130F06; Tue, 17 Jul 2018 06:09:48 -0700 (PDT)
Received: by mail-pf0-x22d.google.com with SMTP id e13-v6so483340pff.7; Tue, 17 Jul 2018 06:09:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=WBgst+83M3DenYx+2qHi/NStidxHUUTSXF88wMSHZe0=; b=ZFYFqVcHIIYTAG9wmPK++Hyay28kW5msm5UYqTREJvT+RsLY3K0nqv2xlqLADIXBQG oolWgZQZj99Axk2qKh5jQFwxFj7k7KTXgaPWtfcpwxMobLMRIqZXQdwGirr9M9BDG6Vd O5LbtYe1TQ1Ii1+ReJnyRN11j8TbGh4icpj8nyGQdNFTQ5lCbDOckToobGhW5G+nmlBr 0Jv34z7hgAeCk7QTTfO7yqvuxPljTnyMKvqwJSYt7jg7KfvFrQIaw1jCkAguurnSrldn WXWFJERT6c2qX2mfGrmKTWeUBIAfmJX9GZ5zeP+ae77xWyFX6/6olzK97AjGfMlZ8vT+ oyZg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=WBgst+83M3DenYx+2qHi/NStidxHUUTSXF88wMSHZe0=; b=OIjGVYn7J9q5zx22sJTLy/4K+0BzNR4ArRwPPS/TRyEyF/90q60VQyZtY2xXzt/aXV YRyD1HvHpF4zglycYFfThTZxADD/SzXxHBS0+J1AOk0BUg6mvLBQw4bFul4qhFnLtz+/ zXElQ4uuLDSjEfaJCyvXMaacqZmUyUV8GLwIpvAj1CCapyiWl0yxQx01pYYCusrYzEZh XjJo0N0b+da6EwKc5o0X6pQijJsKuFECI3h6Y1NdxXt76PdW93n1CtmKMvyYWJR6ppUp /GdAhcNHu+J1PH4f7RNeGwsgh4QeZDOx5iThBArC02ENHAfV1erR3/PERttv14mLoJio kUiQ==
X-Gm-Message-State: AOUpUlHjEVoit++ZrENzjIWVprSt+RN69gh3NkcWUIavjZcCHVfvL3C0 mIay00bPhaJH93A1Hmii2uySMsQWELUjiSqIDt4=
X-Google-Smtp-Source: AAOMgpfTfgUkTzelDH2b97PxbLA+sw//wECs+lRWcg/sRkmSyT1zfOB3gEQYbabvGy/KOvnxQdKmu66rozooVWLBWoM=
X-Received: by 2002:a65:5c83:: with SMTP id a3-v6mr1575641pgt.164.1531832987702; Tue, 17 Jul 2018 06:09:47 -0700 (PDT)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 2002:a17:90a:d396:0:0:0:0 with HTTP; Tue, 17 Jul 2018 06:09:46 -0700 (PDT)
In-Reply-To: <fbf60956-9db5-44b5-a215-4dcc058dc474.xiaohu.xxh@alibaba-inc.com>
References: <19AB2A007F56DB4E8257F949A2FB9858DC3B8B4C@NKGEML515-MBX.china.huawei.com> <5A5B4DE12C0DAC44AF501CD9A2B01A8D8F45D82A@DGGEMM532-MBX.china.huawei.com> <CA+b+ER=UVaE61h57m3z=TpaS9-CQs8oahMu-tuA9i1521Jad9w@mail.gmail.com> <1ec22cba-dbee-4b65-8a75-a8afa213e8bb.xiaohu.xxh@alibaba-inc.com> <CA+b+ERmR779wtr3__QUz440z4YUsqixQnvohOTWDEdhuQQm60Q@mail.gmail.com> <fbf60956-9db5-44b5-a215-4dcc058dc474.xiaohu.xxh@alibaba-inc.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Tue, 17 Jul 2018 15:09:46 +0200
X-Google-Sender-Auth: vYaXlrnAv-mxY5UEI1j9e_Ru0fU
Message-ID: <CA+b+ER==0Q21bCaJNXtrCY+jCyoUnpZntwUrokbveApQ6Zn0_g@mail.gmail.com>
To: "徐小虎(义先)" <xiaohu.xxh@alibaba-inc.com>
Cc: Idr <idr-bounces@ietf.org>, Lizhenbin <lizhenbin@huawei.com>, Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000016592b057131a937"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/9hnCqXhDg6IGl6EDm6KHmiTYxjc>
Subject: Re: [Idr] 答复: WG adoption call for draft-xu-idr-neighbor-autodiscovery
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.27
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, 17 Jul 2018 13:09:52 -0000

Xiaohu,


A) Permanently installing routes in RIB & FIB carried in BGP Hellos TLVs
> which are UDP based is something never heard of. Clearly you are up to
> great precedence here. There is no mention in the current draft when such
> routes are removed.
>
> [Xiaohu] It said in the draft that "
>
>    If the timer
>    expires without receipt of a matching Hello from the peer, BGP
>    concludes that the peer no longer wishes to keep BGP session for that
>    link or that the peer has failed.  The BGP peer then deletes the
>    Hello adjacency.  The route towards the BGP neighbor's loopback
>    address that had been dynamically created due to that BGP Hello
>    adjacency SHOULD be deleted accordingly. "
>
>


​You did not responded to the question at all as I never asked about BGP
session above. There is no BGP session between loopbacks till you put
routes in RIB and FIB as loopback is still unreachable. ​In your draft you
are putting the routes from TLVs carried in UDP and not only how to reach
loopback but also all the atomic connected addresses on how to ECMP towards
loopback. Observe that in my proposal I am not doing it.

IMO that is not acceptable.

Now since you quoted the above note that even some of your own co-authors
declared this is going away and session will not be brought down upon
missing hellos. It is sufficient to keep any BGP session up based on the
keepalives, bfd or manual shut.

In fact just few lines below you agree that periodic hellos may not be
necessary when the session is up.

Very confusing picture ...

[Xiaohu] Could you please explicitly point out which TLVs are not needed?
>
>

​All of them. ​

C) Creation of new message instead of using existing BGP message requires
> more changes then necessary. It also allows for extensible framework which
> while normally is a feature here has a clear potential to be rather a bad
> thing.
>
> [Xiaohu] Which existing BGP message could be used for this BGP peer
> auto-discovery purpose from your POV?
>
>

​BGP Open Message. ​





> D) Sending BGP Hellos periodically - after session is up does not seems to
> bring any value especially for p2p links. For LANs on the other hand (if
> such requirement is in place) there are much better solutions other then
> periodic BGP Hellos.
>
> [Xiaohu] Good point. We could consider how to optimize it in the future.
> Do you have any concrete suggestions for such optimization?
>
>

​as above ... ​

​Thx,
R.​