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/ipv6-wg@ripe.net/
[ipv6-wg] IPv6 prefix delegation BCOP document available for comments and suggestions
- Previous message (by thread): [ipv6-wg] IPv6 prefix delegation BCOP document available for comments and suggestions
- Next message (by thread): [ipv6-wg] IPv6 prefix delegation BCOP document available for comments and suggestions
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Yannis Nikolopoulos
dez at otenet.gr
Tue Apr 11 11:24:28 CEST 2017
On 04/11/2017 11:57 AM, Mikael Abrahamsson wrote: > On Tue, 11 Apr 2017, Yannis Nikolopoulos wrote: > >> 3.2.2: /48 for all is most practical & most pragmatic? How many /32 we >> need to burn for our end users? We have ~1.6M residential users and >> our /29 is definitely not enough. Is RIPE onboard with that? > > Yes. /48 per site is ok as per all IETF and RIPE documents I am aware of. > > So if your /29 is too small for your customer base, go get another one. > I know ISPs who returned their /29 before they even started serious > deployment, and received larger space. I encourage people to do just this. > That's great to hear but when we upgraded our /32 to a /29 (~2011), this was not the case unfortunately (meaning that RIPE would not accept our long term addressing plan as a reason enough to get multiple /29s
- Previous message (by thread): [ipv6-wg] IPv6 prefix delegation BCOP document available for comments and suggestions
- Next message (by thread): [ipv6-wg] IPv6 prefix delegation BCOP document available for comments and suggestions
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]