From: Steven Blake <slblake@petri-meat.com>
To: hadi@cyberus.ca
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] Clean up fib_hash datastructures
Date: Wed, 22 Sep 2004 07:56:21 -0400 [thread overview]
Message-ID: <1095854181.2342.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1095822637.1048.23.camel@jzny.localdomain>
On Tue, 2004-09-21 at 23:10, jamal wrote:
> On Tue, 2004-09-21 at 19:38, Steven Blake wrote:
>
> > RFC 1812 was written before TOS routes were pulled out of OSPFv2 (due to
> > too fee independent implementations). No one implements FIB lookup as
> > described in RFC 1812 in the core. What people do implement is PBR, as
> > well as DSCP-based nexthop selection for MPLS DIFF-TE (RFC 3564).
>
> What about edge?
I've seen no evidence that any HW-based router is doing this.
> The PBR nh selection is a post routing policy though. Do you see it
> valuable to have DSCP replace TOS for lookup?
No. No protocol is distributing DSCP-based routes.
Regards,
// Steve
next prev parent reply other threads:[~2004-09-22 11:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-19 3:33 [PATCH] Clean up fib_hash datastructures David S. Miller
2004-09-20 0:39 ` jamal
2004-09-20 2:46 ` David S. Miller
2004-09-20 3:14 ` Herbert Xu
2004-09-20 3:17 ` David S. Miller
2004-09-20 13:33 ` jamal
2004-09-20 1:51 ` jamal
2004-09-20 2:53 ` David S. Miller
2004-09-20 13:24 ` jamal
2004-09-20 19:11 ` David S. Miller
2004-09-21 3:42 ` Herbert Xu
2004-09-21 6:18 ` David S. Miller
2004-09-21 9:04 ` Andi Kleen
2004-09-21 9:32 ` Herbert Xu
2004-09-21 11:03 ` jamal
2004-09-21 12:07 ` Andi Kleen
2004-09-21 12:22 ` jamal
2004-09-21 23:38 ` Steven Blake
2004-09-22 3:10 ` jamal
2004-09-22 11:56 ` Steven Blake [this message]
2004-09-22 12:12 ` jamal
2004-09-22 20:04 ` Steven Blake
2004-09-22 2:07 ` Herbert Xu
2004-09-22 2:32 ` David S. Miller
2004-09-22 3:57 ` [IPv4] Check PAGE_SIZE in fz_hash_alloc Herbert Xu
2004-09-23 20:05 ` David S. Miller
2004-09-22 3:30 ` [PATCH] Clean up fib_hash datastructures jamal
2004-09-22 3:36 ` David S. Miller
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=1095854181.2342.2.camel@localhost.localdomain \
--to=slblake@petri-meat.com \
--cc=hadi@cyberus.ca \
--cc=netdev@oss.sgi.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