From: Christoph Lameter <cl@linux-foundation.org>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Cc: David Miller <davem@davemloft.net>,
rick.jones2@hp.com, dlstevens@us.ibm.com, netdev@vger.kernel.org,
netdev-owner@vger.kernel.org
Subject: Re: IPV4: Enable IP_ID sequencing for all traffic (inquiring mindswant to know why its set to zero)
Date: Wed, 16 Jul 2008 17:37:07 -0500 [thread overview]
Message-ID: <487E7813.2040708@linux-foundation.org> (raw)
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A104AFDAA4@XCH-NW-7V2.nw.nos.boeing.com>
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.
next prev parent reply other threads:[~2008-07-16 22:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 14:56 IPV4: Enable IP_ID sequencing for all traffic (inquiring minds want to know why its set to zero) Christoph Lameter
2008-07-16 19:03 ` David Stevens
2008-07-16 19:06 ` David Stevens
2008-07-16 19:22 ` Christoph Lameter
2008-07-16 20:30 ` David Miller
2008-07-16 20:39 ` Rick Jones
2008-07-16 21:01 ` David Miller
2008-07-16 21:16 ` IPV4: Enable IP_ID sequencing for all traffic (inquiring mindswant " Templin, Fred L
2008-07-16 22:37 ` Christoph Lameter [this message]
2008-07-16 20:27 ` IPV4: Enable IP_ID sequencing for all traffic (inquiring minds want " David Miller
2008-07-17 16:12 ` Andi Kleen
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=487E7813.2040708@linux-foundation.org \
--to=cl@linux-foundation.org \
--cc=Fred.L.Templin@boeing.com \
--cc=davem@davemloft.net \
--cc=dlstevens@us.ibm.com \
--cc=netdev-owner@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.