netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Michael Richardson <mcr@sandelman.ottawa.on.ca>,
	hadi@znyx.com, hormuzd.m.khosravi@intel.com, ak@suse.de,
	kuznet@ms2.inr.ac.ru, "'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: Re: rfc-editor@rfc-editor.org: RFC 3549 on Linux Netlink as an IP Services Protocol
Date: Thu, 03 Jul 2003 11:00:54 -0700	[thread overview]
Message-ID: <3F046F56.1080808@candelatech.com> (raw)
In-Reply-To: <12785.1057250058@marajade.sandelman.ottawa.on.ca>

Please make the 'table-id' field to be at least
16 bits.  Now that we have VLANs and other types of virtual
interfaces, it would be nice to be able to have a routing table
for each interface, for example.  640k was not enough for everyone,
and ~250 routing tables isn't either :)


 From section 3.1.1:

    Table ID: 8 bits
    Table identifier.  Up to 255 route tables are supported.
                  RT_TABLE_UNSPEC    An unspecified routing table.
                  RT_TABLE_DEFAULT   The default table.
                  RT_TABLE_MAIN      The main table.
                  RT_TABLE_LOCAL     The local table.

                  The user may assign arbitrary values between
                  RT_TABLE_UNSPEC(0) and RT_TABLE_DEFAULT(253).

Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com>       <Ben_Greear AT excite.com>
President of Candela Technologies Inc      http://www.candelatech.com
ScryMUD:  http://scry.wanfear.com     http://scry.wanfear.com/~greear

      reply	other threads:[~2003-07-03 18:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-03 16:34 rfc-editor@rfc-editor.org: RFC 3549 on Linux Netlink as an IP Services Protocol Michael Richardson
2003-07-03 18:00 ` Ben Greear [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=3F046F56.1080808@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ak@suse.de \
    --cc=hadi@znyx.com \
    --cc=hormuzd.m.khosravi@intel.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=mcr@sandelman.ottawa.on.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;
as well as URLs for NNTP newsgroup(s).