Le 2013-12-03 09:42, Tom Taylor a écrit :
You either generate session or BIB if destination information is
optional.
I don’t see why it causes additional events. I don’t understand why it is
Confusing, but I will add some text here.
[PTT] My point here is not the semantics, but the frequency of logging.
A BIB entry is created when an address mapping is associated with a port
mapping. A session entry is created every time a new destination is
contacted, which could be many times for the same BIB entry (virtual or
real, depending on the implementation). Thus if you enable session
logging you may get many times the volume of logs you would get just
logging BIB entry creation, and these would differ only in the timestamp
value contained in them.
Yes, and this fact has been noted in RFC 6888:
REQ-12: A CGN SHOULD NOT log destination addresses or ports unless
required to do so for administrative reasons.
Justification: Destination logging at the CGN creates privacy
issues. Furthermore, readers should be aware of logging
recommendations for Internet-facing servers [RFC6302]. With
compliant servers, the destination address and port do not need to
be logged by the CGN. This can help reduce the amount of logging.
Simon
--
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca
STUN/TURN server --> http://numb.viagenie.ca
_______________________________________________
OPSAWG mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg
