Jakob, > Several years ago Ignas pointed out that you can use this > information to know whether to install a backup on your > side for the route. Backup routes in the forwarding hardware > are expensive, so it would be good to know if your peer > is using your route before installing a backup for it.
Let's see if I understand what you wrote .... ASN1 ASN2 or ASN3 etc ... R1.1 ---------- R2.1 | R1.2 ---------- R2.2 or R3.1 etc .. Assume your prefix is 1.1.1.0/24 You are advertising it from R1.x to R2.x and R3.x Q1 - This is your prefix (or transit one) so are you describing the case where different IBGP next hop is programmed (or not) into local FIB of R1.1 as backup ? Q2 - R2.1's policy can change N times a day (hint PFR) ... how often are you going to probe R2.1 if your route is installed ? Q3 - Exposing someone's RIB or even bRIB may be indirectly revealing their policy. Last time I checked some operators were rather careful not to publish their eBGP policies to their peers. Thx, R. On Tue, Apr 27, 2021 at 2:01 AM Jakob Heitz (jheitz) <jheitz= 40cisco....@dmarc.ietf.org> wrote: > Rayhaan wanted to know if the peer accepted his route. > A looking glass is a different thing in many ways. > > Several years ago Ignas pointed out that you can use this > information to know whether to install a backup on your > side for the route. Backup routes in the forwarding hardware > are expensive, so it would be good to know if your peer > is using your route before installing a backup for it. > > BGP has a peer-to-peer only signaling mechanism: ORF. > Can we invent an ORF for it? > > Rayhaan, please let me know if I'm on or off track > for your use case. > > Regards, > Jakob. > > -----Original Message----- > From: GROW <grow-boun...@ietf.org> On Behalf Of heasley > Sent: Monday, April 26, 2021 4:23 PM > To: Christopher Morrow <christopher.mor...@gmail.com> > Cc: grow@ietf.org grow@ietf.org <grow@ietf.org> > Subject: Re: [GROW] BGP Looking Glass Capability > > Mon, Apr 26, 2021 at 06:25:44PM -0400, Christopher Morrow: > > (as normal netizen) > > > > On Mon, Apr 26, 2021 at 3:33 PM Randy Bush <ra...@psg.com> wrote: > > > > > > Place LG info in peeringdb.com & peeringdb's api. > > > > > > +1 > > > > > > > huh,I had thought this was already actually included in peeringdb? > > <clipped from 7018's page> > > Looking Glass URL http://route-server.ip.att.net > > </clip> > > afict, its just a string, which does not provide a standard way to > represent location/geo. i presume from earlier comments, that something > more structured is desired. > > _______________________________________________ > GROW mailing list > GROW@ietf.org > https://www.ietf.org/mailman/listinfo/grow > > _______________________________________________ > GROW mailing list > GROW@ietf.org > https://www.ietf.org/mailman/listinfo/grow >
_______________________________________________ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
