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]/
[ipv6-wg] internal additional IPv4 assignment policy
- Previous message (by thread): [ipv6-wg] internal additional IPv4 assignment policy
- Next message (by thread): [ipv6-wg] test-ipv6.com
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Geoffroy RIVAT
geo at multi-visp.com
Thu May 6 18:00:58 CEST 2010
Hi, In-Reply-To: <4BE2BAAD.1040906 at casablanca.cz> Lubos Pinkava wrote: > Hello, > > I've raised an idea concerning additional IPv4 assignments for our > customers during RIPE60 beering with quite positive responses, so I > would like to share it here and maybe get some additional feedback. > > We are a company running ISP/collocation business, promoting IPv6 > since 2003 and already having substantial amount of IPv6 enabled > customers. In our point of view, it's still pretty slow growth. > > What I indend to propose for our operations - active imediately - is this: > > - all customers requesting additional /25 (variable) shall have IPv6 > assigned and asked for trying it (if not already done before) > - all customers requesting additional /24 (variable) must already > have active v6 services running (eg. NS/MX/web site for the > beginning) This is a really good idea, on our network for each customers we have configured IPv6 and try to help them to use it. Our last procedure says to add firewall rules in both v4 and v6 when they ask using the last 2 bytes of the v4 address to map to their v6 address -- Geoffroy Rivat
- Previous message (by thread): [ipv6-wg] internal additional IPv4 assignment policy
- Next message (by thread): [ipv6-wg] test-ipv6.com
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]