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] Idea for aggregating IP addresses
- Previous message (by thread): [address-policy-wg] Idea for aggregating IP addresses
- Next message (by thread): [address-policy-wg] Idea for aggregating IP addresses
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jörg Kost
jk at rz089.de
Thu Sep 22 16:11:48 CEST 2016
Hi, I like the idealism of this idea, but it is too little, too late and much too many work to save a few bytes on the ip4 routing table. This race is lost, adding more memory to the board or block and remove certain routes will be the solution. My focus shifted already to the future (?) disaggregation of ip6, where we had hit the 32k lately. Jörg On 22 Sep 2016, at 14:37, Ping IP wrote: > Hello, > > One of the goals of RIPE is to aggregate IP addresses. I'd like to > suggest > the ability for a LIR and End User to exchange number of blocks of IP > ranges for a greater block. > > For example: > LIR/End User has 4 different /22 subnets and LIR/End User can exchange > these subnets for 1 x /20 subnet. > > This gives a LIR or End User the possibility to announce larger IP > subnets > to the Internet. Helping the goal of aggregating the IP addresses on > the > Internet. > > According one of the RIPE trainer, this is currently not possible > according > the RIPE policy. Because there's no policy to give a LIR/End User this > ability. > > I'm curious to what you think of this idea. > > Best regards, > > Abdelouahed > Ping IP network
- Previous message (by thread): [address-policy-wg] Idea for aggregating IP addresses
- Next message (by thread): [address-policy-wg] Idea for aggregating IP addresses
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]