Re: Meeting's minutes

[Dan Harkins <dharkins@xxxxxxxxxx>]

  If a stack can't handle fragmentation and reassembly then it is broken. 
I don't think protocols should be constrained because someone's stack
is broken. Also, the 1500 bytes limit is not realistic anyway because
your MTU is not always 1500 bytes-- some wireless cards set it much smaller
(about 1/3 of that if memory serves) for performance reasons. If you're
having problems with fragmentation then setting a limit of 1500 bytes on
a message would not necessarily help you. Better to just fix the stack.

  Dan.

On Tue, 14 Aug 2001 20:33:14 +0200 sarab@xxxxxxxxxxxxxxxxx wrote
> 
> IPSRA Meeting minutes
> ---------------------
> Meeting date : 7-Aug-2001
> Meeting led by Paul Hoffman.
> 
> Hugo gave a presentation of PIC.
> Questions:
> William Dixon (MS): Is PIC going to support Tero's revised hash?
> Hugo: The problem that the revised hash is solving doesn't appear in PIC
> William: Stateless DOS prevention - since there is no DH computation in the
> first two message
> Hugo: We don't plan - DOS protection was not part of the requirement.
> William: Will you include certificate request? The problem is that is might
> create UDP fragmentation, which from our experience caused problems in IKE
> implementation: Try to avoid fragmentation. The certificate request
> shouldn't be long, but the PKCS#12 might include long certificate chain.
> William : Proposal - add wording saying that messages are not longer than
> 1500 bytes.If you can avoid fragmentation - than avoid it.
> William: What about CMC  support?
> Hugo: No