On Mon, Mar 18, 2019 at 3:21 AM Guyunan (Yunan Gu, IP Technology Research Dept. NW) <guyu...@huawei.com> wrote: > > > > > > From: Robert Raszuk [mailto:rob...@raszuk.net] > Sent: Monday, March 18, 2019 6:05 PM > To: Guyunan (Yunan Gu, IP Technology Research Dept. NW) <guyu...@huawei.com> > Cc: grow@ietf.org; Brian Dickson <brian.peter.dick...@gmail.com> > Subject: Re: [GROW] I-D Action: > draft-chen-grow-enhanced-as-loop-detection-00.txt > > > > > > > In the BGP Update received from the eBGP peer, the eBGP peer has already > > placed the local AS number in the > > > AS-PATH. Thus, the device needs to analyze if the local AS is placed > > improperly in the AS-PATH when it receives > > > the Update. > > > > How is this different from basic AS-PATH loop detection done by any real BGP > speaker today ? > > > > Yunan: To the best of my knowledge, currently when an as loop is detected, > the message is simply dropped without further analysis. If using the proposed > inbound check, possible hijack can be detected. >
this is what BMP is for, it'll send along pre-policy content which would include this route. (I believe it would also be fine to use BMP to detect the outbound case you chatted with Robert about already) -chris _______________________________________________ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
