>> Independent of the prefix distribution mechanism, it may be worth revisit=
>ing
>> having a single /48 for an organisation of 4 employees.
>
>Sure, but if we start handing out /40s like there's enough of them,
>eventually there won't be.
I find it weird that the IEEE manages to allocate a
>So you need to somehow build a prefix distribution mechanism, so people
>can have an arbitrary number of PD prefixes in "wherever network they=20
>happen to be". So we're back to multi-level PD, with all the challenges
>(firewall rules, ACLs, internal routing, ...). And even then, a /48
>might
>We are already 90% of the way here: Make IA_PD work for hosts, not
>just for routers. That way Android handsets can have as many addresses
>as they want.
IA_PD 'works' (for small values of works) for hosts today.
The upstream interface of a CPE is defined as a host instead of a router.
The big
>I tried to traceroute one of them (Probe #3009) at
>2002:568:1047:1:220:4aff:fee0:20ac
>and it petered out at 6to4.tyo1.he.net [2001:470:0:17a::2]
>
>The embedded IPv4 address is 5.104.16.71, which is reachable,
>and is indeed the published address of probe #3009, so it does
>indeed look like a
>> And I'm really curious how to got sizes like 989, 990, 993
>>
>>
>
>Did you check the actual contents of the packets?
The contents of the packets look fine. The packets I'm sending contain
a bit of data and then zeros. The error ICMPs I get back contain the
same data and zeros. That aspect
Playing with traceroute I noticed that juniper routers send error ICMPs
with weird sizes. Did anyone else notice this as well, I can't remember
seeing it mentioned anywhere.
Here is some tcpdump output:
11:51:14.691810 IP6 2001:67c:2e8:13:21c:42ff:fe9f:b8b3 > ff02::1:ff00:1: ICMP6,
neighbor
In your letter dated Wed, 15 Jun 2016 11:12:19 +0200 you wrote:
>The interesting question is why they hand out v6 addresses in the first
>place - I'd assume that Netflix is doing the same global DNS content
>steering thing as all the other big content networks, so they should know
>where the user
