public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Peddemors <michael@linuxmagic.com>
To: Craig Milo Rogers <rogers@ISI.EDU>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [UPDATE] zerocopy.. While working on ip.h stuff
Date: Mon, 26 Feb 2001 17:53:30 -0800	[thread overview]
Message-ID: <0102261753300I.02007@mistress> (raw)
In-Reply-To: <2137.983232656@ISI.EDU>
In-Reply-To: <2137.983232656@ISI.EDU>

On Mon, 26 Feb 2001, Craig Milo Rogers wrote:

> > > I have a whole 40 bytes (+/-) to share...  Now although I don't see
> > > anything explicitly prohibiting the use of unused IP Header option 
..
> > > in between.. Has anyone seen any RFC that explicitly says I MUST NOT?
> >
> >Not to my knowledge.  Routers already change the time to live field,
> >so I see no reason why they can't do smart things with special IP
> >options either (besides efficiency concerns :-).

I know they 'rewrite/extend' existing options, but have never seen a case 
where a router adds an option to a packet beyond those based on what the 
original sender set..

> I've forgotten how the Stream ID option was implemented, but I
> won't be surprised if a router inserted it on the fly (but it was
> probably inserted by end systems).  On the other hand, there was also

Hmm, have to look at a little history..

> a competing philosophy that said that the IP checksum must be
> recomputed incrementally at routers to catch hardware problems in the
> routers, and an incremental recomputation when changing the size of
> the header would be more work.

ah.. we do recalculate IP Checksums now..  when we update any of the 
timestamp rr options etc..

> The one thing I would worry about is unleashing mutant IP
> packets upon the world at large.  I hope the proposed experiments have
> a very good firewall.  It would be very nice to attempt to acquire an
> officially blessed IP option number for such experiments before
> unleashing these packets upon an unprepared world.
>
> 					Craig Milo Rogers

Ah, we better have a good firewall <wink> No, if this goes past concept 
phase, we will try for de official bless.



-- 
"Catch the magic of Linux...."
--------------------------------------------------------
Michael Peddemors - Senior Consultant
Unix Administration - WebSite Hosting
Network Services - Programming
Wizard Internet Services http://www.wizard.ca
Linux Support Specialist - http://www.linuxmagic.com
--------------------------------------------------------
(604) 589-0037 Beautiful British Columbia, Canada
--------------------------------------------------------

       reply	other threads:[~2001-02-27  0:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2137.983232656@ISI.EDU>
2001-02-27  1:53 ` Michael Peddemors [this message]
2001-02-27  2:31   ` [UPDATE] zerocopy.. While working on ip.h stuff Craig Milo Rogers
2001-02-23  6:59 [UPDATE] zerocopy BETA 3 David S. Miller
2001-02-25  3:38 ` Chris Wedgwood
2001-02-25  3:54   ` Jan Rekorajski
2001-02-26 23:46     ` [UPDATE] zerocopy.. While working on ip.h stuff Michael Peddemors
2001-02-26 23:23       ` Andi Kleen
2001-02-26 23:25       ` David S. Miller
2001-02-26 23:47         ` Benjamin C.R. LaHaise
2001-02-27  0:05           ` David S. Miller
2001-02-27  0:11             ` Benjamin C.R. LaHaise
2001-02-27  3:41               ` Michael Peddemors
2001-02-27  3:24         ` Michael Peddemors

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=0102261753300I.02007@mistress \
    --to=michael@linuxmagic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rogers@ISI.EDU \
    /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