Dear Paolo, Maxence and co-authors, Thanks for raising on the last slide at https://datatracker.ietf.org/meeting/124/materials/slides-124-grow-bmp-v2-tlv-support-01, the question
Shall we merge draft-younsi-grow-bmp-snts? At its current stage, if been merged in the same document, we would have in BMPv4 implementation two possible variants. A BMPv4 per peer header carrying either the trigger or export timestamp or/and carry additional trigger and/or export timestamp in TLV's. None of the solution removes the timestamp from the per peer header. I suggest to remove https://datatracker.ietf.org/doc/html/draft-ietf-grow-bmp-tlv-19#section-6 when draft-younsi-grow-bmp-snts is being merged to reduce complexity and aim simplicity. Below the relevant references from the document. Best wishes Thomas https://datatracker.ietf.org/doc/html/draft-ietf-grow-bmp-tlv-19#section-6 An event timestamp MUST always be defined. The observation timestamp SHOULD always be preferred as reference for its inherent maximum accuracy in reporting a given event; would that not be available in an implementation, the next accurate timestamp SHOULD be picked up to, as a last resort, the time at which the information was exported. https://datatracker.ietf.org/doc/html/draft-younsi-grow-bmp-snts-01#section-1 In this document, we deprecate the Timestamp field of the Per-Peer Header and define a Timestamp TLV that can carry multiple types of Timestamps. This allows implementations of BMP to export all the timestamps available while being explicit about the their meaning.
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
