Hello Mark...
Yes, until when I was decided to Fight Agins IPv4, I tried the Fixes.
But after some time, I saw that very little of the problems were due to
inadequacies of the ISP's responsibility equipment.
Most of the difficulties stemmed from:
A) Choices of end-users in their networks.
(Somet
Dear all,
We just turned on our RPKI Route Origin Validation yesterday, then
something weird happened:
[Reference: We are running NLnet Labs’ Routinator 3000, feeding a Cisco ASR
1000 Series router. I know, I know, we haven’t started a second validator
yet.]
When we tested against the two tester
Based on the difficulties I have already experienced, I would bet on some
default route (or for example 2001::/16) statically placed on your FIB
pointing to an Upstream.
Or even the simple absence of the default route (::/0) pointing to null.
Em ter., 2 de mar. de 2021 às 11:21, Pirawat WATANAPONG
Does IANA
(https://www.iana.org/assignments/ipv6-multicast-addresses/ipv6-multicast-addresses.xml#variable)
run the registry for IPv6 Multicast groups? "We do not make allocations
directly to ISPs or end users except in specific circumstances, such as
allocations of multicast addresses"
There
Globally unique multicast destination addresses have become
unnecessary since the advent of SSM. If you look at the IPv4 registry,
you'll what was essentially a land-grab of Group D address space back when
global multicast delivery was considered "on the horizon", and ASM was the
only option. Then
NANOG Community,
The NANOG Program Committee (PC) would like to remind you they are
accepting proposals for all sessions at NANOG 82, June 14-16, 2021. Below
is a summary of key details and dates from the Call For Presentations on
the NANOG website, which can be found at
https://www.nanog.org/part
6 matches
Mail list logo
