netdev - Re: IPV4: Enable IP_ID sequencing for all traffic (inquiring mindswant to know why its set to zero)

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:	Wed, 16 Jul 2008 17:37:07 -0500
From:	Christoph Lameter <cl@...ux-foundation.org>
To:	"Templin, Fred L" <Fred.L.Templin@...ing.com>
CC:	David Miller <davem@...emloft.net>, rick.jones2@...com,
	dlstevens@...ibm.com, netdev@...r.kernel.org,
	netdev-owner@...r.kernel.org
Subject: Re: IPV4: Enable IP_ID sequencing for all traffic (inquiring mindswant
 to know why its set to zero)

Templin, Fred L wrote:

> The other implied use for IP_ID is as a uniquifier for
> duplicate packet detection (DPD), e.g., to detect routing
> loops in the network. But, 16 bits doesn't give sufficient
> uniqueness for today's data rates anway, so flooding-based
> protocols like Simplified Multicast Forwarding (SMF) really
> can't use IP_ID by itself for that purpose.

Well yes that was how the issue came about.

> SEAL extends the IP_ID to 32 bits. With 32 bits, it makes
> sense to set it as monotonically-incrementing for every
> packet out since a network-based DPD mechanism could
> potentially make use of it. Also, 32 bits avoids the ID
> wraparound issue such that a segmentation and reassembly
> mechanism can be used even at high data rates.
> 
> SEAL is specified in 'draft-templin-seal', and is also
> implemented at:
> 
>   http://osprey67.com/seal

Ahh... interesting. Maybe that would help. I will have a look at that.
--
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