docs: update note on transport proto for oversized messages with RFC6313

Signed-off-by: Alexander Bartolomey <[email protected]>

doc.go

@@ -70,6 +70,9 @@ all those data types implement the DataType interface. For more details on the d
 Notably, RFC 6313 defines mechanisms for (recursively) nesting records in data records. The SubTemplateList and SubTemplateMultiList
 data types allow for nesting data records created from *possibly different* templates than the containing data set, thus creating
 a tree-like structure, where records can be nested up to a certain extent (not exceeding the maximum message size of 2^16-1 bytes minus a couple of bytes for headers).
+Note that these message sizes are also bound by the transport protocol of your choice: via TCP, this is no problem, but considering that
+UDP packet fragmentation due to IP MTUs might cause the loss of entire packets, make sure that you pick a protocol that ensures
+reliable message transfer when sending IPFIX messages that exceed ~1500 Bytes of payload.
 
 The coupling of templates and records (read: data semantics are detached from the actual data) requires a stateful management of
 the templates such that incoming data records can be decoded if and only if the corresponding template was received before. RFC 7011