This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/members-discuss@ripe.net/
[members-discuss] RIPE NCC Charging Scheme 2025 Open House: Recording and Slides Available
- Previous message (by thread): [members-discuss] RIPE NCC Charging Scheme 2025 Open House: Recording and Slides Available
- Next message (by thread): [members-discuss] IPv4 Tweaking (was: RIPE NCC Charging Scheme 2025 Open House: Recording and Slides Available)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Brandon Butterworth
hostmaster at bogons.net
Thu Apr 4 12:39:09 CEST 2024
On Thu Apr 04, 2024 at 01:09:46PM +0300, Aleksi wrote: > Just because prior proposals/methods/ideas didn't work, doesn't mean a > new one wouldn't or that all avenues have been explored. People not wanting to discuss it endlessly on mailing lists are not preventing you from doing the research to create an RFC and two interoperable code bases demonstrating it works. As with Edison the only way to disprove the doubters is to do it and see if people adopt it. > So what's the complete unworkable thing on this? > It requires zero network upgrades, only end points need to understand > this. Therefore, adept coder makes a patch, it gets included in Linux > kernel after a while of testing, and just couple years down the line you > have what 90-95% of servers supporting it already? Anyone can submit those patches to Linux any time. brandon
- Previous message (by thread): [members-discuss] RIPE NCC Charging Scheme 2025 Open House: Recording and Slides Available
- Next message (by thread): [members-discuss] IPv4 Tweaking (was: RIPE NCC Charging Scheme 2025 Open House: Recording and Slides Available)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]