26 Sep
2020
26 Sep
'20
9:54 p.m.
Thanks everyone,
From all the replies I got here, I got in touch with
all our upstreams and
peering providers before I headed to bed last night, and
basically they all
came back with the same response - ‘Blocking unknowns would be madness,
less than 25% of routes are currently signed, we are NOT going to do
that!’. So I will be having a ‘talk’ with our NOC when I get back to work
on Tuesday, and find out why exactly my /24 isn’t being propogated to all
the places it’s not making it right now. Someone would appear to have
messed something up, and is giving the wrong explanation for it!
73’s
Damien / VK2TDG
On Sat, 26 Sep 2020 at 10:29 pm, Zhaofeng Li via 44Net <
44net(a)mailman.ampr.org> wrote:
I'm a bit confused. There are several major
providers blocking RPKI
invalids but not unknowns, and your 44 routes will have the "unknown"
state. Do you have any reference to the exact wording that your providers
are using?
Zhaofeng / AJ6IA
On Sat, Sep 26, 2020, at 5:14 AM, Damien Gardner via 44Net wrote:
>
>
>
>
>
>
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
On Sat, 26 Sep 2020 at 9:44 pm, G1FEF via 44Net
<44net(a)mailman.ampr.org>
wrote:
> 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? :(
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org