This morning at : ILNP, an experimental protocol that separates identifier and locator. They implemented this protocol in Linux.
See also RFC6740 to 6748.

Next up at : Low Latency Low Loss with scalable throughput.
Sounds too good to be true, but it's an experiment, let's see how it goes. :)

Improvements to UDP message receive calls presented at :
rcvmsg - Receive one message on one socket
recvmmsg - Receive multiple messages on one socket
--> recvmmmsg - Receive multiple messages on multiple sockets

I appreciate the naming :)

At there was also a talk proposing to make some more IPv4 address space usable:
- 240/4 and 0/8 which are "Reserved for Future Use"
- 127/8 and 224/4 which are under-utilized
- Zeroth address of every subnet and broadcast address of some subnets

They have running code, now they want to do the politics.

The keynote was given by Alissa Cooper, chair: "Open Source, the IETF, and You".
She told the story of joint development of standards and code for TLS 1.3 and QUIC, and then invited people in the Linux community to come and contribute in the IETF - joining the hackathon, writing drafts, or otherwise.


Now presented at by Hajime Tazaki: Is reimplementing the network stack a good idea? - Of course not!
With some protocol conformance measurements to back up the claim. Sadly using a closed-source tool.

Also, the protocol implementation conformance tests in this talk treated MAY and SHOULD as a MUST (i.e., counted fails for them), and I think the IPv6 RFCs on the slide were the obsoleted ones.
Nevertheless - reinventing the wheel is not a good idea.

Sign in to participate in the conversation

cybrespace: the social hub of the information superhighway jack in to the mastodon fediverse today and surf the dataflow through our cybrepunk, slightly glitchy web portal support us on patreon or liberapay!