all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nathan Dehnel <ncdehnel@gmail.com>
To: edou@rdklein.fr, guix-devel@gnu.org
Subject: A paper about Plan 9 and Guix
Date: Tue, 9 Apr 2024 03:06:14 -0500	[thread overview]
Message-ID: <CAEEhgEuXsfPbTyPBXOM-hyaQhS8k=8S7Wpj0Y0UG2spKn5U_rQ@mail.gmail.com> (raw)

Wow, that's incredible.

>Port number themselves stem from TCP emerging from earlier protocols (see the early RFCs 322, 349, 433 and those that obsolete them), and a clean design would probably elect to eschew them, leveraging a \(2^{128}\) address space to allow process-to-process communication, instead of the route-to-host, then route-to-process dance we do know.
>
>The host to process frontier should be an implementation detail on the receiving end, not baked so deeply in the stack.
>This barrier may even change from request to request as new hosts come up or down depending on load.
>This already happens anyway with e.g. kubernetes, but we would have less cruft if it was baked into the protocol.

That sounds like some of the problems RINA was trying to solve.
https://en.wikipedia.org/wiki/Recursive_Internetwork_Architecture


             reply	other threads:[~2024-04-09  8:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-09  8:06 Nathan Dehnel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-04 20:20 A paper about Plan 9 and Guix Edouard Klein
2024-04-08  5:44 ` Pjotr Prins
2024-04-10 15:08 ` Ludovic Courtès
2024-06-02 13:14   ` Edouard Klein
2024-06-06 14:20     ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAEEhgEuXsfPbTyPBXOM-hyaQhS8k=8S7Wpj0Y0UG2spKn5U_rQ@mail.gmail.com' \
    --to=ncdehnel@gmail.com \
    --cc=edou@rdklein.fr \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.