Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Mike O'Dell <mo@ccr.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Cerowrt-devel Digest, Vol 31, Issue 4
Date: Sat, 07 Jun 2014 15:20:49 -0400	[thread overview]
Message-ID: <20140607192049.8206C119C54@ccr.org> (raw)
In-Reply-To: Your message of "Sat, 07 Jun 2014 12:07:33 PDT." <CAA93jw4i_kusuqWh759c0GXONGt-OP5Nnh7c2U8cgFutGzsz1w@mail.gmail.com>


look at what John Moy did in the Cascade 9000s back circa 1997
he used OSFP, of course, instead of ISIS and he did full constraint
resolution path identification along with with per-flow (aka VC) 
ingress rate monitoring which allowed completely distributed load shedding 
(policing) subject to a precedence lattice. once the path was identified
the only rate management was at the ingress points, and that's only per-port state. 

extending the model it to carry ethernet MAC addresses isn't very hard.

	-mo

  reply	other threads:[~2014-06-07 19:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.51111.1402070994.1815.cerowrt-devel@lists.bufferbloat.net>
2014-06-07 18:02 ` Mike O'Dell
2014-06-07 18:21   ` Dave Taht
2014-06-07 18:54     ` Mike O'Dell
2014-06-07 19:07       ` Dave Taht
2014-06-07 19:20         ` Mike O'Dell [this message]
2014-06-07 19:41           ` Dave Taht
2014-06-07 19:54             ` Dave Taht

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=20140607192049.8206C119C54@ccr.org \
    --to=mo@ccr.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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