[ippm] Éric Vyncke's No Objection on draft-ietf-ippm-ioam-direct-export-09: (with COMMENT)

Éric Vyncke via Datatracker <noreply@ietf.org> Tue, 28 June 2022 05:56 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Éric Vyncke via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-ippm-ioam-direct-export@ietf.org, ippm-chairs@ietf.org, ippm@ietf.org, tpauly@apple.com, tpauly@apple.com
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Éric Vyncke <evyncke@cisco.com>
Message-ID: <165639578415.47770.16312619369725312621@ietfa.amsl.com>
Date: Mon, 27 Jun 2022 22:56:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/EL0cn5SjF9kdYDKUzFkVm64w390>
Subject: [ippm] Éric Vyncke's No Objection on draft-ietf-ippm-ioam-direct-export-09: (with COMMENT)

Éric Vyncke has entered the following ballot position for
draft-ietf-ippm-ioam-direct-export-09: No Objection

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/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

# Éric Vyncke, INT AD, comments for draft-ietf-ippm-ioam-direct-export-09
CC @evyncke

Thank you for the work put into this document.

Please find below some non-blocking COMMENT points (but replies would be
appreciated even if only for my own education).

Thanks to Bernie Volz for his internet directorate review at:
https://datatracker.ietf.org/doc/review-ietf-ippm-ioam-direct-export-09-intdir-telechat-volz-2022-06-23/
(please consider Bernie's comments as mine).

Special thanks to Tommy Pauly for the shepherd's detailed write-up including
the WG consensus even if it lacks the justification of the intended status and
uses an unusual templte.

I hope that this helps to improve the document,

Regards,

-éric

## COMMENTS

### No export method specified

Just curious... why isn't IPFIX selected as the export method (or even a
streaming telemetry)? The abstract says "The exporting method and format are
outside the scope of this document."

### Repetition in section 3.1

The sentence "The DEX Option-Type is used as a trigger to collect and/or export
IOAM data" appears multiple times in this document and looks quite repetitive.

### Section 3.1

s/MAY export and/or collect/MAY export and/or MAY collect/ ? (just to be clear)

### Section 3.1.1 mandatory sampling ?

The 1st paragraph contains a "MUST" rather than a "SHOULD" making sampling a
mandatory feature. Isn't this too strong ? Especially when aggregation can be
done locally ?

### Section 3.1.1

In `it is recommended to use N>100` should "RECOMMENDED" be used ?

### Section 6

Should network operators also drop packets containing the DEX at their peering
points ?

## Notes

This review is in the ["IETF Comments" Markdown format][ICMF], You can use the
[`ietf-comments` tool][ICT] to automatically convert this review into
individual GitHub issues.

[ICMF]: https://github.com/mnot/ietf-comments/blob/main/format.md
[ICT]: https://github.com/mnot/ietf-comments

[ippm] Éric Vyncke's No Objection on draft-ietf-i… Éric Vyncke via Datatracker