From: Al Boldi <a1426z@gawab.com>
To: Bernd Eckenfels <ecki@lina.inka.de>
Cc: netdev@vger.kernel.org, linux-net@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] ip / ifconfig redesign
Date: Wed, 14 Dec 2005 17:19:47 +0300 [thread overview]
Message-ID: <200512141719.47755.a1426z@gawab.com> (raw)
In-Reply-To: <200512022253.19029.a1426z@gawab.com>
Bernd Eckenfels wrote:
> Al Boldi wrote:
> > The current ip / ifconfig configuration is arcane and inflexible. The
> > reason being, that they are based on design principles inherited from
> > the last century.
>
> Yes I agree, however note that some of the asumptions are backed up and
> required by RFCs. For example the binding of addresses to interfaces. This
> is especially strongly required in the IPV6 world with all the scoping and
> renumbering RFCs.
Can you point me to those RFCs? Thanks!
> The things you want to change need to be changed in kernel space, btw.
True.
I mentioned ip / ifconfig not to imply that they are the culprit, but instead
to expose the underlying kernel implementation.
This does not mean though, that ip / ifconfig cannot offer an emulated OSI
compliant mode, which would be an impetus to change the underlying
implementation.
Thanks!
--
Al
next prev parent reply other threads:[~2005-12-14 14:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 19:53 Al Boldi
2005-12-02 19:59 ` Pekka Savola
2005-12-02 20:08 ` Ben Greear
2005-12-02 20:38 ` linux-os (Dick Johnson)
2005-12-02 22:49 ` Jesper Juhl
2005-12-10 18:51 ` Stefan Smietanowski
2005-12-02 21:19 ` Jan-Benedict Glaw
2005-12-08 10:15 ` Eric W. Biederman
2005-12-02 22:40 ` Jeff V. Merkey
2005-12-03 13:46 ` Al Boldi
2005-12-11 4:59 ` Bernd Eckenfels
2005-12-14 14:19 ` Al Boldi [this message]
[not found] <447BB19E14004A4388CB9A864D2BA7630DF693@hq-ex-6.brocade.com>
2005-12-03 14:58 ` Jan-Benedict Glaw
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=200512141719.47755.a1426z@gawab.com \
--to=a1426z@gawab.com \
--cc=ecki@lina.inka.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=netdev@vger.kernel.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
all inboxes | Powered by JetHome®