| RE: Question on LWAPP-03 draft | <– Date –> <– Thread –> |
|
From: Vishwas Manral (Vishwas |
|
| Date: Wed, 4 Jan 2006 20:38:55 -0800 (PST) | |
Hi Puneet, One small typo!! I had stated "I guess for IPv6 it is already stated that we do not do fragmentation at LWAPP level" I meant at "IPv6 level" I meant. Thanks, Vishwas -----Original Message----- From: Vishwas Manral [mailto:Vishwas [at] sinett.com] Sent: Thursday, January 05, 2006 9:54 AM To: Puneet Agarwal; Abhijit Choudhury; capwap [at] frascone.com Subject: RE: [Capwap] Question on LWAPP-03 draft Hi Puneet, I think you mean all middleboxes and not just firewalls. I guess for IPv6 it is already stated that we do not do fragmentation at LWAPP level because we have to do MTU discovery and hence fragments can be done at the application level itself. I think only if Path MTU discovery is done for IPv4 too, can we avoid fragmentation. Are you saying that the F, L and Fragment Id fields were only valid for Layer-2 transport and not for Layer-3 transport earlier? Thanks, Vishwas ________________________________________ From: Puneet Agarwal [mailto:pagarwal [at] broadcom.com] Sent: Thursday, January 05, 2006 4:16 AM To: Abhijit Choudhury; capwap [at] frascone.com Subject: RE: [Capwap] Question on LWAPP-03 draft The main issue is passing IP fragments via firewalls. Most firewalls drop fragmented packets (in fact the note is section 3.3.4 also refers to that). Hence the question. Hope this helps. Thanks. -Puneet ________________________________________ From: Abhijit Choudhury [mailto:Abhijit [at] sinett.com] Sent: Wednesday, January 04, 2006 11:42 AM To: Puneet Agarwal; capwap [at] frascone.com Subject: RE: [Capwap] Question on LWAPP-03 draft For L3 transport, as the spec says, only the first IP fragment would have an LWAPP header. Standard IP reassembly is used to put the fragments together. F, L, and FragID fields in the LWAPP header are not neeed for reassembly. Am I missing something ? Thanks, Abhijit -----Original Message----- From: Puneet Agarwal [mailto:pagarwal [at] broadcom.com] Sent: Tuesday, January 03, 2006 7:57 PM To: capwap [at] frascone.com; Pat Calhoun (pacalhou) Subject: [Capwap] Question on LWAPP-03 draft Question of IPv4 frag/reassembly (Section 3.3.4): There was some talk in the past about performing the fragmentation/reassembly at the application level to avoid IP fragments. In that case, the F,L and FragID bits would need to be used even for L3 transport. Did we ever reach a consensus on this one? My recommendation would be to do the frag/reassembly at application level. Thanks. -Puneet _________________________________________________________________ To unsubscribe or modify your subscription options, please visit: http://lists.frascone.com/mailman/listinfo/capwap Archives: http://lists.frascone.com/pipermail/capwap
- Question on LWAPP-03 draft, (continued)
- Question on LWAPP-03 draft Puneet Agarwal, January 3 2006
- RE: Question on LWAPP-03 draft Abhijit Choudhury, January 4 2006
- RE: Question on LWAPP-03 draft Puneet Agarwal, January 4 2006
- RE: Question on LWAPP-03 draft Vishwas Manral, January 4 2006
- RE: Question on LWAPP-03 draft Vishwas Manral, January 4 2006
- RE: Question on LWAPP-03 draft sujay, January 4 2006
- RE: Question on LWAPP-03 draft Pat Calhoun (pacalhou), January 5 2006
- RE: Question on LWAPP-03 draft Puneet Agarwal, January 5 2006
- RE: Question on LWAPP-03 draft Darren Loher, January 5 2006
Results generated by Tiger Technologies using MHonArc.