Re: bufferbloat-beating customer shaping via LibreQoS

Thanks for the shoutout, Norman. Preseem isn’t at 50Gbps in 1U yet, but we will get there. I hope more folks listen to Dave, open vs. closed source solutions aside — AQM makes a shocking amount of difference to quality of experience. Jeremy On Sun, Sep 18, 2022 at 2:14 PM Norman Jester wrote:

Re: bufferbloat-beating customer shaping via LibreQoS

> On Sep 18, 2022, at 12:25 PM, Dave Taht wrote: > > There's been a huge uptake in interest lately in doing better per > device and per customer shaping, especially for > ISPs, in the libreQoS.io project, which is leveraging the best ideas > bufferbloat project members have had over the > past

Re: [External] Normal ARIN registration service fees for LRSA entrants after 31 Dec 2023

> On 18 Sep 2022, at 2:28 PM, Owen DeLong via NANOG wrote: > >> >> No formal agreement, but those involved in ARIN’s formation did indicate >> that at transition >> the existing registrations would be maintained without a need for agreement >> or fee. >> >> The ARIN Board has maintained tha

Island-wide power blackout in Puerto Rico

Puerto Rico is experiencing an island-wide power blackout (100%). Today's (based on yesterday's information) FCC Communication Status Report only reports 6.9% of cell towers out of service. I expect tomorrow's report (based on today's information) will be worse.

Re: [External] Normal ARIN registration service fees for LRSA entrants after 31 Dec 2023 (was: Fwd: [arin-announce] Availability of the Legacy Fee Cap for New LRSA Entrants Ending as of 31 December 20

> On 18 Sep 2022, at 20:42, Owen DeLong wrote: > > Since at its best, all RPKI can provide is a hint at how to properly lie > about an announcement (i.e. what > you must prepend in order for it to be believed), I remain unconvinced that > it provides any actual benefit > except, perhaps, to

bufferbloat-beating customer shaping via LibreQoS

There's been a huge uptake in interest lately in doing better per device and per customer shaping, especially for ISPs, in the libreQoS.io project, which is leveraging the best ideas bufferbloat project members have had over the past decade (cake, bpf, xdp) to push an x86 middlebox well past the 10

Re: [External] Normal ARIN registration service fees for LRSA entrants after 31 Dec 2023 (was: Fwd: [arin-announce] Availability of the Legacy Fee Cap for New LRSA Entrants Ending as of 31 December 20

Since at its best, all RPKI can provide is a hint at how to properly lie about an announcement (i.e. what you must prepend in order for it to be believed), I remain unconvinced that it provides any actual benefit except, perhaps, to the largest and most well known ASNs as originators. Owen > O

Re: Normal ARIN registration service fees for LRSA entrants after 31 Dec 2023 (was: Fwd: [arin-announce] Availability of the Legacy Fee Cap for New LRSA Entrants Ending as of 31 December 2023)

* nanog@nanog.org (Owen DeLong via NANOG) [Sun 18 Sep 2022, 19:53 CEST]: I highly recommend that legacy holders who wish to ensure that their rights are respected transfer their registrations to RIPE-NCC, whether they have signed the LRSA or not. Would you say that in hindsight you would have

Re: [External] Normal ARIN registration service fees for LRSA entrants after 31 Dec 2023 (was: Fwd: [arin-announce] Availability of the Legacy Fee Cap for New LRSA Entrants Ending as of 31 December 20

> On 18 Sep 2022, at 20:17, Owen DeLong via NANOG wrote: > > > >> On Sep 15, 2022, at 22:04 , Rubens Kuhl wrote: >> >> On Fri, Sep 16, 2022 at 12:45 PM William Herrin wrote: >>> >>> On Thu, Sep 15, 2022 at 9:09 PM Rubens Kuhl wrote: On Fri, Sep 16, 2022 at 11:55 AM William Herrin

Re: [External] Normal ARIN registration service fees for LRSA entrants after 31 Dec 2023 (was: Fwd: [arin-announce] Availability of the Legacy Fee Cap for New LRSA Entrants Ending as of 31 December 20

> On Sep 17, 2022, at 08:18 , Tom Beecher wrote: > > I would honestly love it if IANA was able to say "As of X date, all LEGACY > IPv4 allocations are transferred to the RIRs . Assignees will not change, but > will now need to comply with each RIRs policies." The first part of that statement

Re: [External] Normal ARIN registration service fees for LRSA entrants after 31 Dec 2023

> On Sep 16, 2022, at 11:49 , John Curran wrote: > > >> On 16 Sep 2022, at 2:21 PM, Aaron Wendel wrote: >> >> I'm not trying to troll, this is a serious question: >> >> Is there a formal agreement that says that all legacy resources will receive >> free registry services forever and ever

Re: [External] Normal ARIN registration service fees for LRSA entrants after 31 Dec 2023

> On Sep 16, 2022, at 10:37 , William Herrin wrote: > > On Fri, Sep 16, 2022 at 10:29 AM John Curran > wrote: >>> On 16 Sep 2022, at 1:22 PM, William Herrin wrote: >>> On Fri, Sep 16, 2022 at 10:12 AM John Curran wrote: Note - if the reason that you are paying "

Re: [External] Normal ARIN registration service fees for LRSA entrants after 31 Dec 2023

> On Sep 16, 2022, at 10:12 , John Curran wrote: > > >> On 16 Sep 2022, at 12:51 PM, Steve Noble wrote: >> >> I appreciate your response, I remember all of the discussions around this >> change and the positive/negative aspects of it, but it did not correct the >> disenfranchisement of AS

Re: [External] Normal ARIN registration service fees for LRSA entrants after 31 Dec 2023 (was: Fwd: [arin-announce] Availability of the Legacy Fee Cap for New LRSA Entrants Ending as of 31 December 20

> On Sep 16, 2022, at 08:53 , John Curran wrote: > > Tom - > > It’s an artifact of our formation that we are presently providing services to > any customers absent any agreement > and while ARIN continues to do so (by providing basic services to legacy > customers), the long-term direction

Re: [External] Normal ARIN registration service fees for LRSA entrants after 31 Dec 2023 (was: Fwd: [arin-announce] Availability of the Legacy Fee Cap for New LRSA Entrants Ending as of 31 December 20

> On 18 Sep 2022, at 20:04, Owen DeLong via NANOG wrote: > > I could be mistaken, but I believe that RIPE NCC provides RPKI services for > Legacy without Contract resource holders. The policy: https://www.ripe.net/publications/docs/ripe-639 The details: https://www.ripe.net/manage-ips-and-

Re: [External] Normal ARIN registration service fees for LRSA entrants after 31 Dec 2023 (was: Fwd: [arin-announce] Availability of the Legacy Fee Cap for New LRSA Entrants Ending as of 31 December 20

> On Sep 15, 2022, at 22:04 , Rubens Kuhl wrote: > > On Fri, Sep 16, 2022 at 12:45 PM William Herrin > wrote: >> >> On Thu, Sep 15, 2022 at 9:09 PM Rubens Kuhl wrote: >>> On Fri, Sep 16, 2022 at 11:55 AM William Herrin wrote: No, the best option for me right now

Re: [External] Normal ARIN registration service fees for LRSA entrants after 31 Dec 2023 (was: Fwd: [arin-announce] Availability of the Legacy Fee Cap for New LRSA Entrants Ending as of 31 December 20

> On Sep 15, 2022, at 21:09 , Rubens Kuhl wrote: > > On Fri, Sep 16, 2022 at 11:55 AM William Herrin > wrote: >> >> On Thu, Sep 15, 2022 at 8:51 PM Rubens Kuhl wrote: >>> On Fri, Sep 16, 2022 at 10:56 AM William Herrin wrote: Well, I'm one of the people who'd pub

Re: [External] Normal ARIN registration service fees for LRSA entrants after 31 Dec 2023 (was: Fwd: [arin-announce] Availability of the Legacy Fee Cap for New LRSA Entrants Ending as of 31 December 20

I could be mistaken, but I believe that RIPE NCC provides RPKI services for Legacy without Contract resource holders. Owen > On Sep 15, 2022, at 15:55 , Rubens Kuhl wrote: > > You could try suggesting IANA/PTI/ICANN to have a different RPKI trust > anchor and provide such services to legacy b

Re: Normal ARIN registration service fees for LRSA entrants after 31 Dec 2023 (was: Fwd: [arin-announce] Availability of the Legacy Fee Cap for New LRSA Entrants Ending as of 31 December 2023)

> Moving to RIPE is not an unalloyed good; Europeans invented bureaucracy, > and RIPE pursues it with vigor. And getting the above treatment may > require firmly asserting to RIPE that you want it, rather than accepting > the defaults. But their motives are more benevolent than ARIN's toward > le

Re: Normal ARIN registration service fees for LRSA entrants after 31 Dec 2023 (was: Fwd: [arin-announce] Availability of the Legacy Fee Cap for New LRSA Entrants Ending as of 31 December 2023)

I highly recommend that legacy holders who wish to ensure that their rights are respected transfer their registrations to RIPE-NCC, whether they have signed the LRSA or not. Transferring to RIPE-NCC as Legacy without Contract will afford you full respect for your rights in your resources in per

Re: [External] Normal ARIN registration service fees for LRSA entrants after 31 Dec 2023 (was: Fwd: [arin-announce] Availability of the Legacy Fee Cap for New LRSA Entrants Ending as of 31 December 20

Tom – While this may be surprising, it’s my personal view that ARIN and our community has benefited significantly from the approach taken with the legacy resource holders – as opposed to what might have occurred with some form of automatic or mandatory conversion of legacy resource holders to A