netdev - Re: [RFC:] struct net_device_ops: Add function pointer to fill device specific ndisc information

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <50FD4D79.1000308@linux-ipv6.org>
Date:	Mon, 21 Jan 2013 23:15:21 +0900
From:	YOSHIFUJI Hideaki <yoshfuji@...ux-ipv6.org>
To:	unlisted-recipients:; (no To-header on input)
CC:	YOSHIFUJI Hideaki <yoshfuji@...ux-ipv6.org>,
	Stefan Richter <stefanr@...6.in-berlin.de>,
	stephan.gatzka@...il.com,
	"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@...el.com>,
	linux1394-devel@...ts.sourceforge.net, netdev@...r.kernel.org,
	davem@...emloft.net
Subject: Re: [RFC:] struct net_device_ops: Add function pointer to fill device
 specific ndisc information

YOSHIFUJI Hideaki wrote:
> Stefan Richter wrote:
> 
>>   b) RFC 2734 MCAP (Multicast Channel Allocation Protocol):  currently not
>>      implemented; not sure if needed (I see a few big downsides to using
>>      per-multicast-group channels); not sure if networking core support
>>      would be needed for this
> 
> It is definitely needed because we need to listen on multicast group
> for NDP, which might have already had its own channel.

Sorry, this was unclear and incorrect.  RFC3146 Section 9
(IPv6 Multicast) says that packets for all-nodes/all-routers/
solicited-node multicast addresses must be sent via broadcast
channel.  So, NDP should work without MCAP.

But, even so, I do not want to have broken implementation without
MCAP, or at least, we need prepare to support full multicast.
I do NOT want to have patchy implementation just for NDISC.

With extended MAC, networking core (including IPv4/IPv6) does not
need to be changed very much for supporting MCAP; no new hooks,
no new callbacks.

--yoshfuji
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html