Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: Jack Haverty <jack@3kitty.org>
To: nnagain@lists.bufferbloat.net
Subject: [NNagain] Email and The Internet?
Date: Thu, 22 Feb 2024 12:15:32 -0800	[thread overview]
Message-ID: <05dbadb4-b14c-4cc3-9f94-2e4b9ac6104a@3kitty.org> (raw)
In-Reply-To: <CAA93jw7su9Pws3y65tNEkj0bnqqnjC-3UFu0G8ukA10G6zVZOQ@mail.gmail.com>


[-- Attachment #1.1.1.1: Type: text/plain, Size: 1360 bytes --]

On 2/22/24 05:39, Dave Taht via Nnagain wrote:
> I do hope that
> email makes a comeback.
>
> But someones need to start maintaining it better.

Someone?

In the 1980s, I was very involved in the early Internet.  At the time, 
it was funded by the US government, and the policy-makers and 
technologists were tightly coupled.   If we didn't build what they 
needed, the funding would stop.   Simple and effective feedback loop.

At the time, electronic mail was probably the most important service for 
the end-users.  People didn't send datagrams to each other. They sent 
email.   Email had to work or the Internet was useless.

A lot of effort was put into making sure that email worked, such as the 
"Mailbridges" that were crucial components of the Defense Data Network 
as it emerged from the research world.   Policy-makers and technologists 
were pursuing a common mission.   The people who funded,or built, or 
operated the various pieces of The Internet felt responsible, and were 
responsible, for all the Internet elements necessary for the end users 
to use the net.

Forty years later, email has degenerated.  Why?

Question -- is Email now still an important component of Internet 
service?  Do IXPs believe they have a responsibility to make sure email 
works?

Who is "someone"?

Jack Haverty


[-- Attachment #1.1.1.2: Type: text/html, Size: 1847 bytes --]

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2469 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 665 bytes --]

  parent reply	other threads:[~2024-02-22 20:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21 22:54 [NNagain] The Whys of the Wichita IXP Project Brent Legg
2024-02-22  8:14 ` Bill Woodcock
2024-02-22 13:39 ` Dave Taht
2024-02-22 18:58   ` rjmcmahon
2024-02-22 23:31     ` Bill Woodcock
2024-02-23  0:03       ` Dave Cohen
2024-02-23  0:04         ` Bill Woodcock
2024-02-23  0:09           ` Dave Cohen
2024-02-23  0:51             ` Bill Woodcock
2024-02-23  1:47               ` Dave Cohen
2024-02-24 12:05     ` Fearghas Mckay
2024-02-24 12:27       ` Dave Taht
2024-02-24 13:12         ` Fearghas Mckay
2024-02-24 13:24           ` Bill Woodcock
2024-02-24 14:03             ` Dave Taht
2024-02-24 21:30               ` Bill Woodcock
2024-02-24 19:30       ` Robert McMahon
2024-02-25  6:04         ` Bill Woodcock
2024-02-22 20:15   ` Jack Haverty [this message]
2024-02-23  0:02   ` Bill Woodcock

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

  List information: https://lists.bufferbloat.net/postorius/lists/nnagain.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=05dbadb4-b14c-4cc3-9f94-2e4b9ac6104a@3kitty.org \
    --to=jack@3kitty.org \
    --cc=nnagain@lists.bufferbloat.net \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox