Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Fwd: [homenet] IEEE 1905.1 and 1905.1a
Date: Thu, 26 Mar 2015 20:36:10 -0700	[thread overview]
Message-ID: <CAA93jw7_gBK73jMC2Gs_a2-bHayceYXDxw8J2OsKK9dTHGt23w@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw66GZ0gfw2LCD+z_crapRTWWpacO=1LiQ-ca=BwAgjmgQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1443 bytes --]

---------- Forwarded message ----------
From: Dave Taht <dave.taht@gmail.com>
Date: Thu, Mar 26, 2015 at 8:35 PM
Subject: Re: [homenet] IEEE 1905.1 and 1905.1a
To: Hans Liu <hansliu@gmail.com>
Cc: "STARK, BARBARA H" <bs7652@att.com>, HOMENET Working Group <
homenet@ietf.org>, Claire Cheng <claire.cheng@dlinkcorp.com>, "aqm@ietf.org"
<aqm@ietf.org>


up until this moment I had never heard of

http://en.wikipedia.org/wiki/IEEE_1905

this spec, and it does sound useful.

+10 on more open access to it. +100 on anyone working on open source code
for it.

I would certainly like closer relationships between the IEEE and IETF one
day, perhaps even a truly joint (as opposed to back to back) conference.
For far too long members of these two orgs have been going to different
parties, and many, many cross layer issues have arisen due to this.

In my own case I had hoped (in dropping ietf) to be able to attend more
IEEE 802.11 wg meetings - but I would really prefer to stay home and code
for a while.

I would be very supportive of someone(s) taking on the tasks of better
grokking wifi and other non-ethernet media across both orgs both in the
context of homenet and in aqm.

PS While I have a good grip on cable media layers, I am lacking such on
gpon...



-- 
Dave Täht
Let's make wifi fast, less jittery and reliable again!

https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb

[-- Attachment #2: Type: text/html, Size: 2220 bytes --]

           reply	other threads:[~2015-03-27  3:36 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAA93jw66GZ0gfw2LCD+z_crapRTWWpacO=1LiQ-ca=BwAgjmgQ@mail.gmail.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/cerowrt-devel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=CAA93jw7_gBK73jMC2Gs_a2-bHayceYXDxw8J2OsKK9dTHGt23w@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@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