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] 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 05:39:06 CEST 2006
Hi Gert, On Mon, 18 Sep 2006 21:59:35 +0200, Gert Doering wrote: >Of course I hope for a technical solution that will solve everything. > >Until then, I do my best to make sure the network will continue >running - and part of that effort is to make sure that costs are >at least partially paid by those that have the benefits. This is a nice try, however I doubt you will be able to charge those who de-aggregate prefixes and thus cause the vast majority of the table growth. At the end of the day a lot of these de-aggregation results from "security concerns" since 9-11. You may try to charge Mr. Bin Laden, however there are other ones in the queue, too. To keep your network running, you may either: 1. invest or 2. filter those redundant de-agregated announcements (e.g. don't take a /24 with the same AS-path as the /16 it is contained in) However, I know the second (filter) approach _will_ cause your company which pays your salary loosing business, as your company is an transit ISP and thus your customers router will prefer the more specific of your competitor supplying the full table. This should answer the question: # If we accept argument that we should, as a community, advocate no # smaller PI assignments smaller than a /24 because of table # filtration, what happens when the table grows to the size that # operators start to filter on longer masks ? This won't happen, as doing so will cause loss of business for those transit networks which do so. Sadly enough, you should also face that there is nothing, really nothing, that the RIPE can do to stop the table growth influenced by other regions in this world. If the buzzword "security" comes up with large US telcos, this is the end of all discussions in these days. The only thing restrictive policies limited to the RIPE region, as the PI /24 issue and the v6 200 customer rules cause is: - Local ISP's homed in the RIPE region only will be less competitive compared to international ISP's. - People will ly to the hostmasters :-( We should not make policies which cause said disadvantages without having any significant advantage. Best Regards Oliver 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 ]