netdev - Re: [RFC PATCH 5/6] firewire net: IPv6 support (RFC3146).

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]

Date:	Sat, 12 Jan 2013 18:00:58 +0100
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	YOSHIFUJI Hideaki <yoshfuji@...ux-ipv6.org>,
	Stephan Gatzka <stephan.gatzka@...il.com>,
	netdev@...r.kernel.org, linux1394-devel@...ts.sourceforge.net
Subject: Re: [RFC PATCH 5/6] firewire net: IPv6 support (RFC3146).

On Jan 12 Stefan Richter wrote:
> At least one thing which is still missing (also
> missing in Stephan's patch from previous week) is the RFC 3146 clause 5
> Configuration ROM entry.

Another thing:  As far as I understand, the current code assumes that
peers will use the same unicast_FIFO for IPv4 unicast as for IPv6
unicast.  This is not necessarily true.  Either firewire-net needs to
maintain two lists of peers (one for IPv4, another for IPv6), or it needs
to maintain two unicast_FIFOs per peer.
-- 
Stefan Richter
-=====-===-= ---= -==--
http://arcgraph.de/sr/
--
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