This is the correct packet capture for IPv6 fragmentation

Thanks,
Thiru 


From: [email protected]
To: [email protected]
CC: [email protected]
Subject: RE: Doubt in Router Advertisement Message
Date: Wed, 13 Jul 2011 18:13:22 +0530








Vishwas,
I am having one more doubt in IPv6 Fragmentation 

Router Interface MTU 1500, Host A wants to send a packet with 3,000 data bytes 
but MTU is 1500, so it needs to fragment the packet.
As per RFC 2460, First Packet 40 bytes (IPv6 Header) + 8 bytes Fragment Header 
+ 1452 Data = 1500  

                    Second Packet 40 bytes (IPv6 Header) + 8 bytes Fragment 
Header + 1452 Data = 1500  
                   Third Packet     40 bytes (IPv6 Header) + 8 bytes Fragment 
Header +    96 Data =  1500 
 


Thanks,
Thiru 


Date: Sat, 9 Jul 2011 15:05:47 -0700
From: [email protected]
To: [email protected]; [email protected]
Subject: Re: Doubt in Router Advertisement Message

Hi Thiruma,

>From the specs it is clear that the MTU is optional. However if MTU sending is 
>enabled it should be sent on change too.

Sounds like a bug in the implementation to me.

Thanks,
Vishwas



Sent from my Palm Pre on AT&T
On Jul 9, 2011 2:51 AM, Thiruma valavan <[email protected]> wrote: 


Hi IETF Group,
While testing IPV6 Router Advertisement part, I noticed some behaviour that if 
I changed router interface MTU value, it won't send Router Advertisement 
message immediately instead of waiting to next interval time.

Is that normal behaviour, 
Thanks & Regards,

Thirumavalavan PCalsoflabs India Pvt Ltd,BangaloreATLEN Group of CompanyMob: 
+91 9790758035 
                                          
                                                                                
  

Attachment: frag-thiru.pcap
Description: Binary data

--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to