Re: [Lsr]

Aijun Wang <> Tue, 09 March 2021 04:06 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 682B93A0E22; Mon, 8 Mar 2021 20:06:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id s159Cc4Tm9IQ; Mon, 8 Mar 2021 20:06:38 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D903F3A0E1C; Mon, 8 Mar 2021 20:06:37 -0800 (PST)
Received: from DESKTOP2IOH5QC (unknown []) by (Hmail) with ESMTPA id 0F2C61C0178; Tue, 9 Mar 2021 12:06:35 +0800 (CST)
From: Aijun Wang <>
To: 'Tony Li' <>, 'Aijun Wang' <>
Cc: 'lsr' <>, 'draft-wang-lsr-prefix-unreachable-annoucement' <>, "'Acee Lindem (acee)'" <>, 'Gyan Mishra' <>
References: <> <> <>
In-Reply-To: <>
Date: Tue, 09 Mar 2021 12:06:34 +0800
Message-ID: <018801d71499$9890feb0$c9b2fc10$>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQLxZrWFi6EiIeKD/IAcznzpxeLHfwGUGnU/AflsCmCoKfds4A==
Content-Language: zh-cn
X-HM-Tid: 0a78152a45f7d993kuws0f2c61c0178
Archived-At: <>
Subject: Re: [Lsr]
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 09 Mar 2021 04:06:40 -0000

Hi, Tony:

-----Original Message-----
From: <> On Behalf Of Tony Li
Sent: Tuesday, March 9, 2021 11:12 AM
To: Aijun Wang <>
Cc: lsr <>; draft-wang-lsr-prefix-unreachable-annoucement <>; Acee Lindem (acee) <>; Aijun Wang <>; Gyan Mishra <>
Subject: Re: [Lsr]

Hi Aijun,

> [WAJ] We just want to avoid such silent discard behavior, especially for the scenario that there is BGP session run on such failure prefix. 

Stuffing things in the IGP seems like a poor way of determining that there’s a BGP failure.  Wouldn’t BFD be a more appropriate way of determining the loss of connectivity?  Or aggressive BGP keepalive timers?
[WAJ] For BFD, you need to configure between each pair of them to track the connectivity.  For BGP keeplive times, the duration is too long.

> The other side of BGP peer can quickly remove the BGP session when it receives such PUA message which tell it the other peer is down now. Other BGP peer protection procedures can then take effects on.
> The immediate notification of the failure prefix can certainly accelerate the switchover of BGP control plane and also the service traffic that such BGP session carries.

The IGP is a very poor way of delivering service liveness information.
[WAJ] why? 

>>> For scenarios 2, because the specified prefixes can be accessed via another ABR, then we can let this ABR to advertise the details prefixes information for the specified address, which behavior is similar with RIFT, as also mentioned in the presentation materials.
>> Agreed.
> [WAJ] Even for this scenario, the advertisement of the detail prefixes is trigger also via the PUA message from other ABR.

That seems 100% unnecessary as the longer prefix will attract the traffic in the way that you want.
[WAJ] If the ABR advertises such detail prefix, it will certainly attract the traffic. But here the PUA message is just to trigger the ABR to advertise such detail prefix, or else, such ABR will still advertise the summary address.


Lsr mailing list