North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
Re: soBGP deployment
The database is built just like BGP routing information databases are built today. Each AS originates their piece, and every other AS puts the pieces together to form the whole. There is no centralized registry.o with sbgp, the assertion of the validity of asn A announcing prefix P to asn B is congruent with the bgp signaling itself, A merely signs the assertion in the bgp announcement. o with sobgp, the assertion is in an external database with issues such as - data correctness & completeness
These two are up to the originating AS'. If you update your certificates in real time, the same way you do your routes (and I can easily argue you don't actually update your routes in real time, actually), then you will get congruent, up to date information. Those AS' who do not update their certificates in real time will not have real time data in the database, just like BGP is today.- data consistency - update frequency
- granularity (bgp is per-prefix, and this is used by real folk to do traffic eng etc). consider the mess of keeping this up to date and correct in a super irr.
There is no "super irr." There is no centralized database in soBGP. Period. :-) Russ __________________________________ email@example.com CCIE <>< Grace Alone