| To: | kuznet@xxxxxxxxxxxxx |
|---|---|
| Subject: | Re: IPv6 fragmentation and IPv6 header parsing |
| From: | Brad Chapman <kakadu@xxxxxxxxxxxxx> |
| Date: | Wed, 01 Aug 2001 13:30:26 -0400 |
| Cc: | netdev@xxxxxxxxxxx |
| References: | <200108011820.WAA17102@xxxxxxxxxxxxx> |
| Sender: | owner-netdev@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux 2.4.7 i586; en-US; C-UPD: MaxLinux0301) Gecko/20001107 Netscape6/6.0 |
Mr. Kuznetsov, kuznet@xxxxxxxxxxxxx wrote: Hello!answer on the question of why it would need on-the-fly fragmenting: 1.) to make it's life easier when tracking layer-3/4 headers and messing with packet data (inNAT, but that's not important anymore)You confirmed yourself that it is meaningless purpose. Sorry. Well, enough on NAT. and 2.) in case the idiot on the otherend won't allow an MTU of 1500 ;-) This just sounds as full non-sense to me. What is special with 1500?
I read somewhere that the correct size for an IPv6 link was 1500.
Is this wrong? Is the correct MTU smaller? If it is, then sorry in
advance ;-)
Alexey Brad |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: IPv6 fragmentation and IPv6 header parsing, kuznet |
|---|---|
| Next by Date: | Re: IPv6 fragmentation and IPv6 header parsing, kuznet |
| Previous by Thread: | Re: IPv6 fragmentation and IPv6 header parsing, kuznet |
| Next by Thread: | Re: IPv6 fragmentation and IPv6 header parsing, kuznet |
| Indexes: | [Date] [Thread] [Top] [All Lists] |