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] dynamic or static IPv6 prefixes to residential customers
- Previous message (by thread): [ipv6-wg] dynamic or static IPv6 prefixes to residential customers
- Next message (by thread): [ipv6-wg] dynamic or static IPv6 prefixes to residential customers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniele Orlandi
daniele at orlandi.com
Wed Jul 27 18:47:19 CEST 2011
On Wednesday 27 July 2011 15:45:05 Ivan Pepelnjak wrote: > Unfortunately you have to do static prefix delegation because it's > impossible to renumber the customer's inside LAN within a reasonable time > interval with today's state of IPv6 SLAAC. > > However, static delegations might cause IPv6 routing table explosion unless Hi, My policy is to give semi-static prefixes, that is, prefixes that are statically associated to the customer for what concerns radius & such but have NO written GUARANTEE to remain permamently assigned to the user. So, if I need to renumber I can do it with little worries, maybe a notice to the user if I'm really good. The customer knows that he has to consider the prefix as not assigned to him, thus, if he wants to run a service on those addresses he has to be prepared to use a dynamic DNS service or such. Bye,
- Previous message (by thread): [ipv6-wg] dynamic or static IPv6 prefixes to residential customers
- Next message (by thread): [ipv6-wg] dynamic or static IPv6 prefixes to residential customers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]