Dear Maxence and Paolo, +1 on Maxence comment. This needs to be clarified and defined.
Best wishes Thomas -----Original Message----- From: Maxence Younsi <[email protected]> Sent: Monday, November 17, 2025 3:30 AM To: Paolo Lucente <[email protected]> Cc: Graf Thomas, SCS-INI-NET-VNC-E2E <[email protected]>; draft-ietf-grow-bmp-tlv authors <[email protected]>; draft-younsi-grow-bmp-snts authors <[email protected]>; grow <[email protected]> Subject: Re: [GROW] Re: draft-ietf-grow-bmp-tlv, draft-younsi-grow-bmp-snts, timestamps Be aware: This is an external email. Hi Thomas, Paolo Completely agree as well! If merged, what should we do with the existing Timestamp field? Remove it or just deprecate and zero-fill it? Maxence ----- Mail original ----- De: "Paolo Lucente" <[email protected]> À: "Thomas Graf" <[email protected]>, "draft-ietf-grow-bmp-tlv authors" <[email protected]>, "draft-younsi-grow-bmp-snts authors" <[email protected]> Cc: "grow" <[email protected]> Envoyé: Dimanche 16 Novembre 2025 21:26:05 Objet: [GROW] Re: draft-ietf-grow-bmp-tlv, draft-younsi-grow-bmp-snts, timestamps Hi Thomas, Entirely with you on removing section 6 of draft-ietf-grow-bmp-tlv-19 merging the documents. +1 Paolo On 7/11/25 00:17, [email protected] wrote: > Dear Paolo, Maxence and co-authors, > > Thanks for raising on the last slide at > https://data/ > tracker.ietf.org%2Fmeeting%2F124%2Fmaterials%2Fslides-124-grow-bmp-v2- > tlv-support-01&data=05%7C02%7CThomas.Graf%40swisscom.com%7Cea217d15b73 > 14daabf3608de2581451c%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C638 > 989434312669002%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOi > IwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C% > 7C%7C&sdata=Y7agDVx3Wj9bAn3lrCexq7b8moGFzUBXthyePE9C4j0%3D&reserved=0 > <https://dat/ > atracker.ietf.org%2Fmeeting%2F124%2Fmaterials%2Fslides-124-grow-bmp-v2 > -tlv-support-01&data=05%7C02%7CThomas.Graf%40swisscom.com%7Cea217d15b7 > 314daabf3608de2581451c%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C63 > 8989434312688465%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiO > iIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C > %7C%7C&sdata=j0pvx7qJZ4GkwvSB2XXPXeQYlCj4IW1Wc1tJCRnpyck%3D&reserved=0 > >, 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 > <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://data/ > tracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-grow-bmp-tlv-19%23section-6 > &data=05%7C02%7CThomas.Graf%40swisscom.com%7Cea217d15b7314daabf3608de2 > 581451c%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C63898943431272150 > 5%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIs > IlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=tH > AGE7sXE0k5ObyIU%2F1pQyH3H4l6fhrt7Yq1lRhih9Q%3D&reserved=0 > <https://dat/ > atracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-grow-bmp-tlv-19%23section- > 6&data=05%7C02%7CThomas.Graf%40swisscom.com%7Cea217d15b7314daabf3608de > 2581451c%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C6389894343127321 > 92%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCI > sIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=l > l2QQMkYycXks8uRiz85ZVhyxS0XNRgv0QiQiA1GKiM%3D&reserved=0> > > 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://data/ > tracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-younsi-grow-bmp-snts-01%23sectio > n-1&data=05%7C02%7CThomas.Graf%40swisscom.com%7Cea217d15b7314daabf3608 > de2581451c%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C63898943431274 > 2887%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwM > CIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata > =rptm5AzikNPEno0qwIUs38WN4%2FftDMWIca9bA8UUKT0%3D&reserved=0 > <https://dat/ > atracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-younsi-grow-bmp-snts-01%23secti > on-1&data=05%7C02%7CThomas.Graf%40swisscom.com%7Cea217d15b7314daabf360 > 8de2581451c%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C6389894343127 > 53316%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAw > MCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdat > a=GwR2S%2FiHTQlSJXRQ9cZwMCcO20ULfpNyTewITho3wbo%3D&reserved=0> > > 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. > > > _______________________________________________ > GROW mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
