Re: ForCES TLV size

While I am perfectly happy not to do anything, I will point out that 
the proposed solution avoids needing to change all the TLVs.
All the controlling TLVs would just have their normal (less than 64K) 
length, because the content of the PDU is less then 64K.  Only the 
path-data (sparse or dense) TLVs would need to change.
Yes, it is a hack.  But it is designed in aprt to avoid the problem 
of having to change everything.

Yours,
Joel

At 07:49 AM 8/19/2007, Wang,Weiming wrote:
>To break down a Oper-TLV into 64k fragments, then we have to break 
>down a LFB-select TLV which includes  even one 64k Oper-TLV  into 
>more fragments. We then also need to define a Redirect-TLV, 
>Redirect-data TLV on how they are broken down into less than 64k fragments.
>
>Things are getting mess more or less.
>
>thanks,
>Weiming