From: Markku Savela <msa@moth.iki.fi>
To: olaf@bigred.inka.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: ipv4 and ipv6 stacks for new link layers?
Date: Sat, 24 Feb 2007 18:45:03 +0200 [thread overview]
Message-ID: <200702241645.l1OGj3GV023299@moth.iki.fi> (raw)
In-Reply-To: <E1HKzK9-0001aX-TT@bigred.inka.de> (message from Olaf Titz on Sat, 24 Feb 2007 17:00:37 +0100)
>
> > This is a pity, because it would be so easy to make the both stacks
> > totally independent of the actual link layers. It only needs one (or
> > two) new function pointer in net_device. This function should do the
> > conversion from IPv4/IPv6 address into corresponding hardware
> > multicast/broadcast address.
>
> You mean, the link layer drivers should know of IP addressing modes?
> Sounds like a layering violation to me. The mapping from IP to MAC
> address is (for a good reason) part of the IP specs, not of the
> Ethernet, Token Ring etc. specs, so the right place to implement it is
> not the network drivers.
I disagree.
In current architecture, you have to patch kernel IPv6 and IPv4
protocols when you add new link layer that they don't recognize.
I think that is worse than allow a new driver to provide a simple
service function which maps IPv4/6 multicast address into link layer
address, when asked.
next prev parent reply other threads:[~2007-02-24 16:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 11:49 Markku Savela
2007-02-23 13:47 ` Neil Horman
2007-02-24 0:26 ` David Miller
2007-02-24 16:00 ` Olaf Titz
2007-02-24 16:45 ` Markku Savela [this message]
2007-02-25 0:52 ` David Miller
2007-02-25 10:27 ` Olaf Titz
2007-02-25 11:21 Al Boldi
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=200702241645.l1OGj3GV023299@moth.iki.fi \
--to=msa@moth.iki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@bigred.inka.de \
/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®