[ippm] Zaheduzzaman Sarker's Discuss on draft-ietf-ippm-ioam-direct-export-09: (with DISCUSS)

[Zaheduzzaman Sarker via Datatracker <[e-mail]>]

Zaheduzzaman Sarker has entered the following ballot position for
draft-ietf-ippm-ioam-direct-export-09: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-ippm-ioam-direct-export/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Thanks for working on this specification.

Thanks to Colin Perkins for his valuable TSVART review. I find the TSVART early
reviewer's concern on rate limiting the exported traffic triggered by DEX
Option-type as only protection mechanism
(https://mailarchive.ietf.org/arch/msg/tsv-art/1WNgYWGJmxLd4f3RAiDk-LJ-S8Y/)
very valid but haven't seen it addressed. In this discuss, I would like to
bring back attention to that concern and would like to discuss why there should
not be a circuit breaker kind of functionality required here?

I also think this specification should be explicit about not exporting IOAM
data to any receiver outside of IOAM limited domain. Hence supporting Roman's
discuss.

for example - The introduction section can state-

OLD text-

   A
   "receiving entity" in this context can be, for example, an external
   collector, analyzer, controller, decapsulating node, or a software
   module in one of the IOAM nodes.

New text-

   A
   "receiving entity" in this context can be, for example, an external
   collector, analyzer, controller, decapsulating node, or a software
   module in one of the IOAM nodes with in IOAM limited domain.