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] 2006-05 New Policy Proposal (PI Assignment Size)
- Previous message (by thread): [address-policy-wg] 2006-05 New Policy Proposal (PI Assignment Size)
- Next message (by thread): [address-policy-wg] 2006-05 New Policy Proposal (PI Assignment Size)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Oliver Bartels
oliver at bartels.de
Tue Sep 19 15:16:44 CEST 2006
Hi Max, ( and Randy, too, as it hits the same topic ) On Tue, 19 Sep 2006 15:47:51 +0000, Max Tulyev wrote: >It is a good idea to set up the default route to one of upstreams when >you set up filtering. This saves routers' memory, but leaves your >connectivity fine. You can even accept 0.0.0.0/0 from several upstreams >with different localprefs to keep channels back-up working. This doesn't help the transit provider who is selling upstream to BGP clients. Your default route and Randy's reduced table compete against the full unfiltered table of the other upstream. The more specific prefix _always_ wins. >P.S. I don't believe backbone carriers who don't have upstreams at all >need to conserve some extra kilobytes of memory ;) Ack. In this case there are simply some anti-competitive arguments hidden as resource conservation arguments. Best Regards Oliver Bartels Oliver Bartels F+E + Bartels System GmbH + 85435 Erding, Germany oliver at bartels.de + http://www.bartels.de + Tel. +49-8122-9729-0
- Previous message (by thread): [address-policy-wg] 2006-05 New Policy Proposal (PI Assignment Size)
- Next message (by thread): [address-policy-wg] 2006-05 New Policy Proposal (PI Assignment Size)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]