You’re right, if you assume that a LIR got a /48 from a RIR, but this is not normal, right? What I read from that is that the an ISP is getting and end-user /48, as is the only way to get a /48, at least in a normal situation, right? Regards, Jordi -----Mensaje original----- De: ipv6-wg <ipv6-wg-bounces@ripe.net> en nombre de Gert Doering <gert@space.net> Responder a: <gert@space.net> Fecha: martes, 4 de julio de 2017, 17:21 Para: JORDI PALET MARTINEZ <jordi.palet@consulintel.es> CC: <ipv6-wg@ripe.net> Asunto: Re: [ipv6-wg] IPv6 Prefix delegation BCOP version 3 is out... Hi, On Tue, Jul 04, 2017 at 03:20:58PM +0200, JORDI PALET MARTINEZ wrote: > I think you somehow answered yourself. It is non-acceptable usage (according policy), and not just in RIPE but also the other RIRs. Huh, what? Sub-allocations are perfectly fine according to RIPE policy, and initially for all other RIRs (as that was part of the very first IPv6 policy document). So if you have an ISP customer that has no own LIR, sub-allocating a /40 to them so they can give their customers /48s is the thing to do. (But indeed, it's out of scope of this document which is really focused on end user assignments) Gert Doering -- APWG chair -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.consulintel.es The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.