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] address-policy-wg / Revision of Last /8 Allocation Criteria
- Previous message (by thread): [address-policy-wg] address-policy-wg / Revision of Last /8 Allocation Criteria
- Next message (by thread): [address-policy-wg] address-policy-wg / Revision of Last /8 Allocation Criteria
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Radu-Adrian FEURDEAN
ripe-wgs at radu-adrian.feurdean.net
Thu Oct 29 21:04:29 CET 2015
On Thu, Oct 29, 2015, at 14:44, Christopher Kunz wrote: > It cannot be reiterated enough: The final /22 is a migration tool for > IPv6. There is a large number of viable solutions to use IPv6 as your > main addressing scheme for a eyeball ISP, especially if you have started > from scratch only a few years ago. While this has beed understood and accepted by some small players, deploying IPv6 doesn't spare you of situations like: - residential users that will cancel and make you bad press because their PS4 doesn't work. Not with CGN, and for the moment not over v6(*) - business users that will just not sign with you if you cannot provide them their block of X public v4 addresses. Be happy if they don't explicitely ask you to disable IPv6. > I think that focusing on IPv6 adoption should be the first order of business. And once you have IPv6 as standard for everyone, but public dedicated v4 either unavailable of extremely expensive, you do what ? -- Radu-Adrian FEURDEAN fr.ccs
- Previous message (by thread): [address-policy-wg] address-policy-wg / Revision of Last /8 Allocation Criteria
- Next message (by thread): [address-policy-wg] address-policy-wg / Revision of Last /8 Allocation Criteria
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]