This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/routing-wg@ripe.net/
[routing-wg] Historical routing question
- Previous message (by thread): [routing-wg] Historical routing question
- Next message (by thread): [routing-wg] Historical routing question
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tassos Chatzithomaoglou
achatz at forthnet.gr
Wed Apr 11 10:28:07 CEST 2018
Since AD is a vendor thing and not a standard, i guess you'll have to ask Cisco. My idea would be that since you are more likely to filter prefixes on ingress eBGP rather on IGP and eBGP usually carries the majority of prefixes, eBGP maybe was considered more "trustworthy" for the majority of traffic. In any case, eBGP AD can be changed (plus the network backdoor option) and some recommendations propose so. PS: If i remember correctly, Juniper does it the "right" way. -- Tassos Hank Nussbacher wrote on 10/4/2018 7:52 μμ: > While giving a routing lecture today someone asked me > "Why was eBGP assigned an administrative distance of 20 which is better > than OSPF's administrative distance of 110. What was the logic behind > that decision?" > I was unable to think of an answer. > Ideas? > > Thanks, > Hank > > -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/routing-wg/attachments/20180411/ff61a170/attachment.html>
- Previous message (by thread): [routing-wg] Historical routing question
- Next message (by thread): [routing-wg] Historical routing question
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]