[email protected] wrote on 05/22/2010 11:16:20 AM:

> t.petch wrote:
> > I see that this I-D had entered 'Revised I-D needed' which I would 
like to
> > progress.
> > 
> > I see several comments about maximum record size, including a 
> suggestion that we
> > should make the 'SHOULD NOT' a 'MUST NOT' exceed 2**14.
> > 
> > I am dead set against this change.  We had a clear requirment, early 
on, to
> > allow 65k messages, and I think it wrong to MUST NOT that 
> requirement. The text
> > in the other I-Ds is a compromise to strke a balance between this and 
having
> > everything fit in 576 byte; I think we have the balance right.
> 
> My response to Alexey was that this I-D borrows that particular 
> requirement from RFC4347 and that this I-D shouldn't be upping the 
> requirement.  If it's okay with you, I'll forward him your response. 
> The way I read his comment was that he's just asking why - he's not 
> really requesting a change.
> 
 
In this case, could the requirement be rephrased in syslog over dtls. 
Rather than imply that the 2**14 limit is de novo in syslog, a phrasing 
like "RFC 4347 limits the size of DTLS message bodies to 2**14 bytes" 
would be preferable.  The limit will still be an issue for some parts of 
healthcare and this kind of phrasing points to the real source of the 
limit.  Then, if some later version of DTLS changes that limit, the syslog 
over dtls would inherit that change.  This would be consistent with the 
approach taken in syslog over UDP, where the size limits are 
recommendations up until the hard limit for the size of a UDP message, and 
it is made clear that UDP is the reason for the hard limit.

Kind Regards,

Robert Horn | Agfa HealthCare
Research Scientist | HE/Technology Office
T  +1 978 897 4860

Agfa HealthCare Corporation, 100 Challenger Road, Ridgefield Park, NJ, 
07660-2199, United States
http://www.agfa.com/healthcare/
Click on link to read important disclaimer: 
http://www.agfa.com/healthcare/maildisclaimer
_______________________________________________
Syslog mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/syslog

Reply via email to