[ippm] FW: New Version Notification for draft-mirsky-ippm-asymmetrical-pkts-01.txt

[Ernesto Ruffini <[e-mail]>]

Dear WG,

After the document was updated, I realized that sometimes, in a multicast environment, you do not want packets to return to the original sender.

 

The one who generates the multicast stream is the STAMP Sender that sends some test packets.

It might be better if the reflected packets go to a different location.

This could be true when the STAMP Sender stays close to the actual multicast frames generator (for example a camera transmitting live video) so that the test packets follow the exact same path as the video stream packets. But the datacenter where test data are analyzed could be far away, and it would be better to have reflected packets return there.

Do you think it could be helpful to add a Sub-TLV to the “Reflected Test Packet Control TLV” that says "and please, send the reflected packets to this IP instead of replying to the original sender"?

Something like:

 

   Reply-to IP Address sub-TLV:  A 20-octet sub-TLV.  The Type value

      is TBA.  The value of the Length field MUST be equal to 16.  The

      Value field consists of a 16-octet field that on transmit MUST

      be filled in with the IPv4 or IPv6 address intended by the

      Session-Sender to be used as the IP destination value of the

      reflected test packet, and processed on receipt.

 

Thanks

               Ernesto

 

-----Original Message-----
From: [e-mail] <[e-mail]> 
Sent: Monday, July 10, 2023 16:14
To: Ernesto Ruffini <[e-mail]>; Greg Mirsky <[e-mail]>; Henrik Nydell <[e-mail]>
Subject: New Version Notification for draft-mirsky-ippm-asymmetrical-pkts-01.txt

 

 

A new version of I-D, draft-mirsky-ippm-asymmetrical-pkts-01.txt

has been successfully submitted by Greg Mirsky and posted to the IETF repository.

 

Name:                  draft-mirsky-ippm-asymmetrical-pkts

Revision:             01

Title:                     Performance Measurement with Asymmetrical Packets in STAMP

Document date:               2023-07-10

Group:                 Individual Submission

Pages:                  10

URL:             <https://www.ietf.org/archive/id/draft-mirsky-ippm-asymmetrical-pkts-01.txt> https://www.ietf.org/archive/id/draft-mirsky-ippm-asymmetrical-pkts-01.txt

Status:          <https://datatracker.ietf.org/doc/draft-mirsky-ippm-asymmetrical-pkts/> https://datatracker.ietf.org/doc/draft-mirsky-ippm-asymmetrical-pkts/

Html:            <https://www.ietf.org/archive/id/draft-mirsky-ippm-asymmetrical-pkts-01.html> https://www.ietf.org/archive/id/draft-mirsky-ippm-asymmetrical-pkts-01.html

Htmlized:        <https://datatracker.ietf.org/doc/html/draft-mirsky-ippm-asymmetrical-pkts> https://datatracker.ietf.org/doc/html/draft-mirsky-ippm-asymmetrical-pkts

Diff:            <https://author-tools.ietf.org/iddiff?url2=draft-mirsky-ippm-asymmetrical-pkts-01> https://author-tools.ietf.org/iddiff?url2=draft-mirsky-ippm-asymmetrical-pkts-01

 

Abstract:

   This document describes an optional extension to a Simple Two-way

   Active Measurement Protocol (STAMP) that enables the use of STAMP

   test and reflected packets of variable length during a single STAMP

   test session.  In some use cases, the use of asymmetrical test

   packets allow for the creation of more realistic flows of test

   packets and, thus, a closer approximation between active performance

   measurements and conditions experienced by the monitored application.

 

   Also, the document includes an analysis of challenges related to

   performance monitoring in a multicast network.  It defines procedures

   and STAMP extensions to achieve more efficient measurements with a

   lesser impact on a network.

 

                                                                                  

 

 

The IETF Secretariat