| | | | | | | | |
|
|
|
You're here: Home |
- suggested_sia_head is a filesystem path so it should be some sort of lowest common denominator of the PATH_MAX of the platforms that will be running this (typically 1K) - cert serial length(decimal(2^(8*20))) (RFC 3280 says 20 octets) - msg_ref is length(decimal(2^64)) (or maybe length(decimal(2^128)))
These sound reasonable.
The remaining fields, sender, recipient, class name and the resource_set_*, we could take one of two approaches: - try to estimate what would be "sensible" maximums based on the conceivable maximum number of entities involved. eg, sender, recipient, and classname are 255 chars, resource_set_* are 4k
classname: okresource_set: this could be larger, sepacially if we did lots of RIR2RIR transfers. OTOH, I think the value of this field will be parsed and split into db records anyway - at least that's how I would do it.
- make the maximums stupidly large. eg, sender, recipient, and classname can be 1K (or 4K, or....), resource_set_* are 8k (or 16k, or....)
WFM too. The point is not to let them grow to insane sizes as that could lead to failed processes DOS attacks.
Robert
Rob
