From: Dave Taht <dave.taht@gmail.com>
To: make-wifi-fast@lists.bufferbloat.net
Subject: [Make-wifi-fast] Fwd: IEEE Call for Papers
Date: Thu, 10 Aug 2017 11:28:03 -0700 [thread overview]
Message-ID: <CAA93jw7UfHFp_F2-msT6c4dmScsj3MW_-At5Uotmj2KHTJh7NQ@mail.gmail.com> (raw)
In-Reply-To: <82E3794B-28AA-41DB-B105-C92949C1C20E@cable.comcast.com>
Does anyone actually read IEEE's journals anymore?
I liked them stating the obvious " This is causing a shift from
traditional standards development to a hybrid approach that includes
open-source development techniques, tooling, and full lifecycle
management. Keeping pace with the changes to the standards ecosystem
and evolution of the way networks are built and deployed is
challenging."
but I'm not sure how that turns into content people would read.
---------- Forwarded message ----------
From: Livingood, Jason
Date: Thu, Aug 10, 2017 at 6:03 AM
Subject: IEEE Call for Papers
To: Dave Taht <dave.taht@gmail.com>
This may be a chance to write about Make WiFi Fast, whether you or
someone else for IEEE Communications Standards… See
http://www.comsoc.org/comstandardsmag/cfp/networking-standards
parent reply other threads:[~2017-08-10 18:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <82E3794B-28AA-41DB-B105-C92949C1C20E@cable.comcast.com>]
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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw7UfHFp_F2-msT6c4dmScsj3MW_-At5Uotmj2KHTJh7NQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=make-wifi-fast@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