REPLY: 2:280/5555 61dc2a0f
MSGID: 2:5005/49 61e26e0a
CHRS: CP866 2
TZUTC: 0700
TID: hpt/fbsd 1.9.0-cur 2019-12-05
Dear Michiel,

10 Jan 22 13:39, you wrote to me:


 MV>>> Sure. When 2000::/3 runs out, there is 4000::/3. And when that
 MV>>> runs out, there is 6000::/3. Up until c000::/3.

 VS>> That's great news!

 MV> It is not really news I'd say.

I've never seen an RFC or any other standard referring to a global unicast
address block other than 2000::/3. Of course it looks reasonable that in the
future you can slice 0000::/1 or 8000::/1 into /3 blocks, but I've never read
anything official. So at least it's news for me.

 MV> Ans I suppose when push come to shove
 MV> 1000::/4 coild also be used. And even 0::/4 with the exeption of
 MV> 0::/64.

BTW what is already in use within 0000::/1 and 8000::/1 besides 2000::/3?

Victor Sudakov, VAS4-RIPE, VAS47-RIPN
--- GoldED+/BSD 1.1.5-b20170303-b20170303
 * Origin: Ulthar (2:5005/49)
SEEN-BY: 1/123 15/0 30/0 50/109 80/1 90/1 105/81 106/201 120/340 123/131
SEEN-BY: 153/7715 154/10 221/1 6 226/30 229/110 424 426 428 550 664
SEEN-BY: 229/700 240/1120 5832 249/206 317 400 266/512 280/464 5555
SEEN-BY: 282/464 1038 301/0 1 101 113 812 317/3 320/219 322/757 342/200
SEEN-BY: 396/45 460/58 463/68 467/239 888 633/280 712/848 920/1 5000/111
SEEN-BY: 5001/100 5005/49 53 5015/46 5020/715 830 846 1042 2047 2140
SEEN-BY: 5020/4441 5054/8 5058/104 5064/56 5080/102 5083/1 444
PATH: 5005/49 5020/1042 301/1 229/426