Historic archive of defunct list bloat-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: "L. Aaron Kaplan" <aaron@lo-res.org>
To: Juliusz Chroboczek <jch@pps.jussieu.fr>
Cc: bloat-devel <bloat-devel@lists.bufferbloat.net>,
	cerowrt-devel@lists.bufferbloat.net,
	babel-users <babel-users@lists.alioth.debian.org>
Subject: Re: DLEP [was: switching cerowrt to quagga-babeld issues]
Date: Mon, 2 Jul 2012 21:50:46 +0200	[thread overview]
Message-ID: <C23893B5-B70E-43A2-9DC4-6930CB0C5EF5@lo-res.org> (raw)
In-Reply-To: <7ibojyozmk.fsf_-_@lanthane.pps.jussieu.fr>

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

Juliusz, remember that there are two approaches right now concernig DLEP:  CISCO and the rest of the world ;-)
nuff said ;)))


On Jul 2, 2012, at 7:13 PM, Juliusz Chroboczek wrote:

>> I would like to point you towards a nice feature that Henning is
>> currently implementing: DLEP - a (mostly routing protocol independent)
>> framework for communicating settings and metrics between a radio and
>> a routing daemon.
> 
> I reviewed an early draft of that.
> 
> As I understand DLEP, it is a standardised way to implement the "thin
> access point" model that Cisco and friends are promoting -- a complex
> (and expensive) controller associated with a number of dumb APs.  This
> is a good way to enable mobility between APs with unmodified stations,
> it's a good way to make network administrators happy (centralised
> administration), and also a good way to make Cisco happy (since the
> controller can be sold for much, much more than an AP).
> 
> Standardising the protocol that the controller uses to communicate with
> the APs is a worthy goal, but pretty much orthogonal to mesh networking
> research.
> 
> -- Juliusz
> 


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 203 bytes --]

      parent reply	other threads:[~2012-07-02 19:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAA93jw40kiOwDnOzG-_jUn7nKpky59bNBTec8ynjVwJJhKxr0Q@mail.gmail.com>
     [not found] ` <2187151341044351@web9d.yandex.ru>
     [not found]   ` <7isjdcpm1q.fsf@lanthane.pps.jussieu.fr>
     [not found]     ` <40851341093226@web25d.yandex.ru>
     [not found]       ` <7ik3yoz7p2.fsf@lanthane.pps.jussieu.fr>
     [not found]         ` <CAA93jw5p9EqoK09Y_AXaHG_DfH-u_QDYU_FKOK_hhxBRDcuqAA@mail.gmail.com>
     [not found]           ` <1521341229978@web13h.yandex.ru>
2012-07-02 15:36             ` [Babel-users] switching cerowrt to quagga-babeld issues Dave Taht
2012-07-02 16:16               ` L. Aaron Kaplan
2012-07-02 16:44                 ` Dave Taht
2012-07-02 16:54                   ` L. Aaron Kaplan
2012-07-02 17:13                 ` DLEP [was: switching cerowrt to quagga-babeld issues] Juliusz Chroboczek
2012-07-02 17:36                   ` [Babel-users] " Henning Rogge
2012-07-02 19:50                   ` L. Aaron Kaplan [this message]

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=C23893B5-B70E-43A2-9DC4-6930CB0C5EF5@lo-res.org \
    --to=aaron@lo-res.org \
    --cc=babel-users@lists.alioth.debian.org \
    --cc=bloat-devel@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=jch@pps.jussieu.fr \
    /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