public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <lindner_marek@yahoo.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] any progress or info on available throughput based routing?
Date: Sat, 9 Jun 2012 22:58:00 +0800	[thread overview]
Message-ID: <201206092258.00955.lindner_marek@yahoo.de> (raw)
In-Reply-To: <CAA_JP8XWzyv5-eYhCxCrMEt-y6RTYu=qe6e=vYTXT1oi-H5O=g@mail.gmail.com>

On Friday, June 08, 2012 07:45:31 dan wrote:
> I have been watching batman-adv for quite a while.  I really love the
> progress that the devs have made and the concepts are great.
> 
> I think the holy grail of mesh routing protocols is to handle 3
> characteristics of routes and route choice per packet type, possibly
> using DSCP/TOS values or something.
> 
> Those 3 characteristics are link quality, latency, and available
> throughput.  And the multiple routing tables would be so that services
> requiring low latency can be routed on lowest latency routes, that may
> not have a lot of throughput, and bulk traffic can be routed through
> paths that have more available throughput.
> 
> I have seen posts discussing interest in adding such features and I am
> interested to do some reading on this subject as it pertains to
> batman-adv.  Is there anything out there?  I couldn't find anything on
> the site.

AFAIK nobody plans to implement multiple routing tables as you are suggesting 
here. Unless I missed something ?

Regards,
Marek

      reply	other threads:[~2012-06-09 14:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-07 23:45 [B.A.T.M.A.N.] any progress or info on available throughput based routing? dan
2012-06-09 14:58 ` Marek Lindner [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=201206092258.00955.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /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