General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Hal Murray <hmurray@megapathdsl.net>
To: bloat@lists.bufferbloat.net
Cc: Hal Murray <hmurray@megapathdsl.net>
Subject: [Bloat] UCLA, Cisco & more join forces to replace TCP/IP
Date: Fri, 05 Sep 2014 01:36:19 -0700	[thread overview]
Message-ID: <20140905083619.D7C99406060@ip-64-139-1-69.sjc.megapath.net> (raw)

http://www.networkworld.com/article/2602109/lan-wan/ucla-cisco-more-join-force
s-to-replace-tcpip.html

    "Their aim is to put forth an Internet architecture that's more secure,
     able to support more bandwidth and friendlier to app developers.
     Cryptographic authentication, flow balance and adaptive
     routing/forwarding are among the key underlying principles."

I wonder if bufferbloat is on their radar?


-- 
These are my opinions.  I hate spam.




             reply	other threads:[~2014-09-05  8:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-05  8:36 Hal Murray [this message]
2014-09-05  8:47 ` MUSCARIELLO Luca IMT/OLN

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/bloat.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=20140905083619.D7C99406060@ip-64-139-1-69.sjc.megapath.net \
    --to=hmurray@megapathdsl.net \
    --cc=bloat@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