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] Charging scheme discussion
- Previous message (by thread): [members-discuss] Charging scheme discussion
- Next message (by thread): [members-discuss] Charging scheme discussion
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Rob Golding
rob.golding at othellotech.net
Wed Jul 25 05:05:01 CEST 2012
>> If we're going to "accelerate"the acceptance >> of IPv6 (which is in all of our >> interests) then anyone using PI IPv4 >> _probably_ needs some PI IPv6 >> >> If you're going to charge then for both you >> put an artificial barrier >> (doubling their cost), and they'll never >> want the v6 ... > > Have you considered that one hour of > engineering time would probably > cost a company ~€150 - €300, including > overheads? Regarding IPv6 ... End users don’t know what it is, don’t appear to want it, from take up certainly don’t seem to need it, and basically don’t care about it - they just want their pr0n to turn up quickly. > So your argument is that a cost > equivalent to 10 minutes of engineering > time for a company is too much for > the company to bear if they want a provider > independent v6 presence on the > Internet. No, I'm saying they don’t want ipv6 at all as they see no requirement for it, then you add making them pay for it in addition to their ipv4 will get you the response (from experience) "no thanks, no-one uses that" >> e.g. a /18 is charged more than a /24. >> Why ? >> What more work is there for RIPE to do ? > e.g. requests outside an assignment window. If my window is a /16 then the /18 is less work, than when your window is /26 and you request a /24 :p > Can I suggest you read the RIPE Annual Report > for 2011? Been there, done that, have my own opinions on the expenditure ... > local asn do need to understand ASN32 > natively, but this support has been > available on all cisco ios based platforms > since 2009 and all juniper > platforms since 2008. > If you're running software this old on your > transit > routers, you have bigger problems. You missed the point where I explained that we did all this 10 years ago ! 89% of the worlds desktops are running an OS which does things wrong with IPv6 DNS results when it gets a v6 result from DNS lookups and doesn’t have any v6 routes, so putting a site/service/system on ipv6 only cuts your potential audience by 9/10ths Deliberately putting people off of IPv6 by telling them they'll need expensive tech time (as you say) plus more contributions to ripe fees is not going to help takeup - my experience, YMMV Rob
- Previous message (by thread): [members-discuss] Charging scheme discussion
- Next message (by thread): [members-discuss] Charging scheme discussion
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]