26 Sep
2020
26 Sep
'20
12:18 p.m.
Hi,
44-net space is not RPKI invalid, since there is no 44net RPKI.
So unless your upstreams require RPKI valid rather than the more normal
only drop RPKI invalids, this shouldn't be an issue.
Thanks,
Q
On Sat, 26 Sep 2020 at 13:16, Damien Gardner via 44Net <
44net(a)mailman.ampr.org> wrote:
On Sat, 26 Sep 2020 at 9:44 pm, G1FEF via 44Net
<44net(a)mailman.ampr.org>
wrote:
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
If you have a BGP announced subnet allocated then we are now allowing
delegation of reverse DNS to your own servers. Contact me off list if you
want to arrange this.
oooh, that would be very cool! Although maybe not a lot of point..
Perhaps this is specific to your subnet? The subnet I have announced over
BGP is reaching far and wide last time I checked.
Hmm I’m told it’s world wide. All peering exchanges and transit carriers
(at least in the APNIC controlled section of the world.) have started
enforcing rPKI route signing at the registries at the start of September,
though some are doing a soft start with warning emails sent weekly rather
than just hard blocking invalid prefixes.
My /24 is no longer accepted on any peering exchange in .au, and only
accepted at one of our four transit carriers here. I’m told that on 1st
October that carrier will cease accepting the ‘invalid’ prefix, and then
44-net will be no more? :(