Nick, Would you allow to query yr router via such API to anyone in the world ? I believe this is the real use case Rayhaan is bringing up ...
Thx, R. On Sun, Apr 25, 2021 at 4:07 PM Nick Hilliard <[email protected]> wrote: > Rayhaan Jaufeerally (IETF) wrote on 24/04/2021 14:38: > > I would like to propose draft-jaufeerally-bgp-lg-cap-00 > > (https://datatracker.ietf.org/doc/draft-jaufeerally-bgp-lg-cap/) as a > > mechanism for in-band dissemination of looking glass endpoints in BGP, > > using a new OPEN message capability. > > Hi Rayhaan, > > what we need from routers is a consistent API endpoint which serves RIB > data, that can be consumed by client apps. > > I.e. this should be done using json/xml/etc; it should be available over > over https; it should be accessible via a REST API; it should be aimed > at having a front-end HTTP cache server to implement rate limiting / > limited access control / etc (i.e. remove as much complication from the > router as possible), and the data model should be flexible enough to > handle a variety of different deployment configurations (e.g. ibgp / > ebgp / l3vpn / l2vpn / evpn / ixp route server / etc). > > INEX has done this for BIRD (see github.com/inex/birdseye, which > provides both the data model and the LG), but the data model is designed > around constructs which are only available in BIRD, so this isn't really > portable to other BGP stacks. But the principle works, and works well. > > Nick > > _______________________________________________ > GROW mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/grow >
_______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
