| To: | laforge@xxxxxxxxxxxx, laforge@xxxxxxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | Re: Why is struct ipv6hdr still old-style RFC1883 ? |
| From: | Hideaki YOSHIFUJI (吉藤英明) <yoshfuji@xxxxxxxxxxxxxxxxx> |
| Date: | Mon, 13 Nov 2000 21:14:52 +0900 |
| Cc: | netdev@xxxxxxxxxxx, usagi-users@xxxxxxxxxxxxxx |
| In-reply-to: | <20001112230116.A3817@xxxxxxxxxxxxxxxxxxxxxxx> |
| References: | <20001112230116.A3817@xxxxxxxxxxxxxxxxxxxxxxx> |
| Sender: | owner-netdev@xxxxxxxxxxx |
In article <20001112230116.A3817@xxxxxxxxxxxxxxxxxxxxxxx> (at Sun, 12 Nov 2000 23:01:17 +0100), Harald Welte <laforge@xxxxxxxxxxxxxxxxxxxxxxx> says: > 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? > > 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? Do you mind if we, USAGI Project, decided to use new structures defined in RFC2292 / RFC2292bis? -- Hideaki YOSHIFUJI @ USAGI Project <yoshfuji@xxxxxxxxxxxxxx> PGP5i FP: F731 6599 5EB2 BBA7 1515 1323 1806 A96F 5700 6B25 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Why is struct ipv6hdr still old-style RFC1883 ?, Harald Welte |
|---|---|
| Next by Date: | Re: Why is struct ipv6hdr still old-style RFC1883 ?, kuznet |
| Previous by Thread: | Why is struct ipv6hdr still old-style RFC1883 ?, Harald Welte |
| Next by Thread: | Re: Why is struct ipv6hdr still old-style RFC1883 ?, kuznet |
| Indexes: | [Date] [Thread] [Top] [All Lists] |