<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-ippm-encrypted-pdmv2" target="https://datatracker.ietf.org/doc/html/draft-ietf-ippm-encrypted-pdmv2-09">
   <front>
      <title>IPv6 Performance and Diagnostic Metrics Version 2 (PDMv2) Destination Option</title>
      <author initials="N." surname="Elkins" fullname="Nalini Elkins">
         <organization>Inside Products</organization>
      </author>
      <author initials="M." surname="ackermann" fullname="michael ackermann">
         <organization>BCBS Michigan</organization>
      </author>
      <author initials="A." surname="Deshpande" fullname="Ameya Deshpande">
         <organization>NITK Surathkal/Google</organization>
      </author>
      <author initials="T." surname="Pecorella" fullname="Tommaso Pecorella">
         <organization>University of Florence</organization>
      </author>
      <author initials="A." surname="Rashid" fullname="Adnan Rashid">
         <organization>Politecnico di Bari</organization>
      </author>
      <date month="October" day="5" year="2024" />
      <abstract>
	 <t>   RFC8250 describes an optional Destination Option (DO) header embedded
   in each packet to provide sequence numbers and timing information as
   a basis for measurements.  As this data is sent in clear-text, this
   may create an opportunity for malicious actors to get information for
   subsequent attacks.  This document defines PDMv2 which has a
   lightweight handshake (registration procedure) and encryption to
   secure this data.  Additional performance metrics which may be of use
   are also defined.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-ippm-encrypted-pdmv2-09" />
   
</reference>
