Kernel patch for the udp_ping tool (displays information returned by routers for operations & management)

(Identifier/Locator separation protocol, RFC 6740) on stage.

Linux code running, even on small machines (EdgeRouterX) Demo with mobility.

Plus some support from the resolver.

TAPS (abstraction of the transport layer for applications, so the application requests features, not a protocol) in Python, by @NerdResa

The new concept of "framers" is nice but apparently still a little rough.

(interface to network security functions) in

A new acronym, SoA (Security on Air)

LPWAN (Low Power Wide Area Networks like LORA) on stage (SCHC is a header compression protocol pronounced Chic)

Cleaning of the code, OAM functions, writing a user documentation (hackathons are not only about code).

IPwave (IP over Wave, for vehicles, so you can ping other cars on the road, depend on Road-Side Units to relay)

Not tested with real cars, only a simulator :-)

"The code was completely rewritten, from my PHP to another guy's Python"

"There is still an endless loop in the code but at least we now know where it is"

Now, the COIN Research Group (not related to Bitcoin or other cryptocurrencies, COIN = Computing in the Network) with the P4 tool.

Still quite at the beginning, it seems.

"The aguri tree is an implementation of the Patricia trie"

How to represent many (really many) IPv6 addresses in a data structure. (One of the applications is "anonymization" of IP addresses.)

"The team was just me so we agreed on everything"

PBT (Postcard-Based Telemetry, reporting by every router on the path, for instance to find the location where packets are lost)

Many various projects at the hackathon : zone transfers over TLS and/or DSO (stateful DNS), as FastCGI, and in (with the nghttp library), DNS support for , prefix discovery in BIND, interoperability tests for cookies 🍪, temporary records in dynamic updates, and HTTP-SVC.

was one of the largest teams at the hackathon. QUIC is a transport protocol which can replace .

Lots of interoperavbility testing (19 implementations, most of them both client and server.)

On the table, it is funny that some implementations don't interoperate completely with themselves :-)

And last but not least, remote report from the team, who worked entirely remotely on and other crypto security protocols such as SSH.

A lot of work at the goes into finding names for projects/protocols. Here, ICAN == Instant Congestion Assessment Network.

Back to the operators claiming that encrypted layer-4 protocols like deprives them of data. The spin bit allows to see the RTT but not the packet loss. Proposal to add "loss bits".

Now, in the session (new and unshaved work), a proposal for an "Internet of rules".


transparency a project to store historical DNS data. (Pushed from registries.)

@bortzmeyer for some reason that doesn't sound like a good idea to me. Also, the questions on that form ...

@jpmens Yes, one of the concerns was data privacy, of course. Another was the project itself: not enough details, and not a clear business model.

Inscrivez-vous pour prendre part à la conversation
Mastodon - Gougère Network

Vive les gougères ! mnt-by: @yapret @papaeng89