| To: | laforge@xxxxxxxxxxxx |
|---|---|
| Subject: | Re: Why is struct ipv6hdr still old-style RFC1883 ? |
| From: | kuznet@xxxxxxxxxxxxx |
| Date: | Mon, 13 Nov 2000 21:16:16 +0300 (MSK) |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <20001112230116.A3817@xxxxxxxxxxxxxxxxxxxxxxx> from "Harald Welte" at Nov 13, 0 03:15:40 pm |
| Sender: | owner-netdev@xxxxxxxxxxx |
Hello! > Why is struct ipv6hdr still implementing the old RFC1883 style > 4-bit prio and 24-bit flowlabel fields instead of the RFC2460 > 8-bit tc and 20-bit flowlabel fields? Because none of them are used by clear reason (byte wide filed spanning byte boundary is a non-sense). 0th word of header is accesed only as whole. > Is this just some legacy which nobody got around to change? If this is > the case, I'm going to update this. Are there any other reasons? If update consists in removing these bitfield crap and replacing with single word, I see no problems. Alexey |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Why is struct ipv6hdr still old-style RFC1883 ?, 吉藤英明 |
|---|---|
| Next by Date: | RE: colliding ip detection!, Vernon Wells |
| Previous by Thread: | Re: Why is struct ipv6hdr still old-style RFC1883 ?, 吉藤英明 |
| Next by Thread: | 2.2.18pre kernel net problem, Shawn Houston |
| Indexes: | [Date] [Thread] [Top] [All Lists] |