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/address-policy-wg@ripe.net/
[address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
- Previous message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
- Next message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Masataka Ohta
mohta at necom830.hpcl.titech.ac.jp
Wed May 10 13:44:32 CEST 2006
Sascha Lenz wrote: Hi, >>My understanding is that the IPv4 Internet failed to limit the >>size of DFZ that BGP convergence is taking prphibitively long >>time for mission critical applications. > Based on what? I think you can use google with keywords like "BGP convergence". But, I should show you an extreme example. That is, if we have only 1 AS, there is no convergence problem of BGP. > (I run Corporate Networks with routing table sizes >> Internet DFZ due > to /32 announcements and such stuff, no BGP Problems on good setups.) Convergence heavily depends on your policy. Masataka Ohta
- Previous message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
- Next message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]