| To: | Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [RFC/PATCH] "strict" ipv4 reassembly |
| From: | Arthur Kepner <akepner@xxxxxxx> |
| Date: | Tue, 17 May 2005 16:20:07 -0700 (PDT) |
| Cc: | dlstevens@xxxxxxxxxx, rick.jones2@xxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <E1DYBED-0006wa-00@gondolin.me.apana.org.au> |
| References: | <E1DYBED-0006wa-00@gondolin.me.apana.org.au> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Wed, 18 May 2005, Herbert Xu wrote: > .... > Such systems would be violating the spirit of RFC791 which says: > > The identification field is used to distinguish the fragments of one > datagram from those of another. The originating protocol module of > an internet datagram sets the identification field to a value that > must be unique for that source-destination pair and protocol for the > time the datagram will be active in the internet system. > > Are you aware of any extant systems that do this? > .... Are you aware of any (new) systems that _don't_ violate this? I wouldn't want to own one of them! -- Arthur |
| Previous by Date: | Re: [RFC/PATCH] "strict" ipv4 reassembly, David S. Miller |
|---|---|
| Next by Date: | Re: [RFC/PATCH] "strict" ipv4 reassembly, Herbert Xu |
| Previous by Thread: | Re: [RFC/PATCH] "strict" ipv4 reassembly, Herbert Xu |
| Next by Thread: | Re: [RFC/PATCH] "strict" ipv4 reassembly, Herbert Xu |
| Indexes: | [Date] [Thread] [Top] [All Lists] |