[tcpm] comment about draft-nishida-tcpm-maxwin-02

[marcelo bagnulo braun <[e-mail]>]

Hi,

Thanks for writing this draft, seems useful to me.

A couple of minor comments:

- I understand that this extension MUST be used with PAWS, correct? I 
mean, using a larger RCVWND without PAWS is likely to result in 
inability to distinguish old duplicate packets from new ones, correct? 
Should this requirement of this being used in conjunction with PAWS be 
explicitly stated?

- If an endpoint that does support this extension communicates with 
endpoints that do not support this extension, it will result in the 
endpoint that does support the extension to be allocating the double 
buffer size for every connection with a legacy endpoint that it should. 
I agree that is not fatal, but wouldnt this be a problem in terms of 
resources? Would this excess of demand in resource usage would make 
adoption of this extension not very attractive? Maybe it would be better 
to use the 15 shift count when the other endpoint also replies with a 15 
shift count or something like this?

- The second paragraph in section 4, it talks about "performance 
degradation caused by misinterpretation of the shift count" I dont 
understand what you are referring to, can you clarify?

thanks, marcelo