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/members-discuss@ripe.net/
[members-discuss] Input from Membership on RIPE NCC Charging Scheme Model
- Previous message (by thread): [members-discuss] Input from Membership on RIPE NCC Charging Scheme Model
- Next message (by thread): [members-discuss] Input from Membership on RIPE NCC Charging Scheme Model
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Dickinson, Ian
Ian.Dickinson at sky.uk
Thu Sep 22 12:18:46 CEST 2016
> I do find it entertaining that the legacy resource holders that probably have WAY WAY more space than they need and refuse to return their surplus for the good of the internet have objections. > I feel this is because their bosses would then start asking if the need it all. They'd then be pressured financially to return their 'cushions'. It boils down to selfishness and not working towards the common good of the internet. Just because you got it when we were careless as an industry doesn't mean you should hoard it now. > We should bill legacy holders per /24 and they can then pay for the unused space or return it. The maintenance fees can then go to reducing costs to LIRs with limited resources who are truly optimising their resources so they can afford to buy more on the transfer market. Or they could do the decent thing and rationalise their requirements and return unused space. > What does newham council need 65000 odd public ips for? What does a uni need a /16 for? I know one uni I visited some friend at that used to give EVERY DEVICE a public IP. That's unacceptable in the current situation. > I even know a trust that has a /20 they use in azure over a VPN that they are using 5-10% of and they frankly said they were keeping it because it was a cheap annual fee. If it was expensive or per IP they would have only kept a /23 and returned the rest. > Maybe an amnesty for legacy holders where if they return 50% of their space or more they can stay on the current charging scheme but if they continue to hoard they are penalised? Wow. Just wow. Legacy space is out of scope for RIPE policy for charging and reclaim. All sorts of organisations have need for addresses that may not be obvious from the outside, but that does not make them selfish. (This applies to PA space too) None of this would make any substantial difference to the exhaustion situation anyway. It would be nice if a little more research was apparent in some of the items in this thread. BTW, How advanced is your IPv6 deployment compared to your deckchair rearrangement project? Ian Information in this email including any attachments may be privileged, confidential and is intended exclusively for the addressee. The views expressed may not be official policy, but the personal views of the originator. If you have received it in error, please notify the sender by return e-mail and delete it from your system. You should not reproduce, distribute, store, retransmit, use or disclose its contents to anyone. Please note we reserve the right to monitor all e-mail communication through our internal and external networks. SKY and the SKY marks are trademarks of Sky plc and Sky International AG and are used under licence. Sky UK Limited (Registration No. 2906991), Sky-In-Home Service Limited (Registration No. 2067075) and Sky Subscribers Services Limited (Registration No. 2340150) are direct or indirect subsidiaries of Sky plc (Registration No. 2247735). All of the companies mentioned in this paragraph are incorporated in England and Wales and share the same registered office at Grant Way, Isleworth, Middlesex TW7 5QD.
- Previous message (by thread): [members-discuss] Input from Membership on RIPE NCC Charging Scheme Model
- Next message (by thread): [members-discuss] Input from Membership on RIPE NCC Charging Scheme Model
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]