[ipv6-wg] IPv6 Prefix delegation BCOP version 3 is out...
- Previous message (by thread): [ipv6-wg] IPv6 Prefix delegation BCOP version 3 is out...
- Next message (by thread): [ipv6-wg] IPv6 Prefix delegation BCOP version 3 is out...
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
sander at steffann.nl
Tue Jul 4 17:33:14 CEST 2017
Hi, > 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? An LIR will not get PA addresses smaller than a /32 from RIPE NCC, that is true. /32 is the minimum allocation size for IPv6 PA. An LIR might however get a sub-allocation from a different LIR. There is no minimum sub-allocation size, so it might be a /48. In most cases it wouldn't be wise to sub-allocate such a small block, but it is allowed. I could imagine something like that if for example a non-LIR was running a small hosting business where they want to assign a /56 to each customer. They could get a /48 sub-allocation from an LIR, from which they could make the /56 assignments to their customers. I still would recommend sub-allocating and assigning larger prefixes, but this is just an example. :) Cheers! Sander -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 455 bytes Desc: Message signed with OpenPGP URL: <https://lists.ripe.net/ripe/mail/archives/ipv6-wg/attachments/20170704/5a016aee/attachment.sig>
- Previous message (by thread): [ipv6-wg] IPv6 Prefix delegation BCOP version 3 is out...
- Next message (by thread): [ipv6-wg] IPv6 Prefix delegation BCOP version 3 is out...
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]