Capwap Mailing List: RE: Question on LWAPP-03 draft

[Puneet Agarwal (pagarwal]

Title: Message

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