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/[email protected]/
[address-policy-wg] IPv6 access to K-root
- Previous message (by thread): [address-policy-wg] IPv6 access to K-root
- Next message (by thread): [address-policy-wg] IPv6 access to K-root
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Kurt Erik Lindqvist
kurtis at kurtis.pp.se
Tue Mar 1 21:57:00 CET 2005
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2005-03-01, at 21.09, Iljitsch van Beijnum wrote: > And if we can write up a nice document that outlines how people can > filter out "remote" /48s because having those in their routing tables > has no added value, while allowing "close by" /48s that help optimize > traffic flow, this could work out very well. > > The good part is that if the uptake of this way of multihoming isn't > excessive, there is no need to filter at all and we're all happy. But > if it gets out of hand, people can filter without breaking > connectivity. So this takes having to correctly guess the amount of > multihoming in the future out of the equation. It also have the potential to give us even more asymmetrical routing than what we have today. Which might or might not be a problem. YMMV. - - kurtis - -----BEGIN PGP SIGNATURE----- Version: PGP 8.1 iQA/AwUBQiTXI6arNKXTPFCVEQJJmACgr+FQm5MF2SjqHqJMC66mw7hLFTwAnikA xvQltjWS1J6/B13KNKV9RAck =FCeo -----END PGP SIGNATURE-----
- Previous message (by thread): [address-policy-wg] IPv6 access to K-root
- Next message (by thread): [address-policy-wg] IPv6 access to K-root
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]