Re: [ippm] [Tsv-art] Tsvart early review of draft-ietf-ippm-ioam-direct-export-06

On Fri, Sep 3, 2021 at 07:54 Colin Perkins via Datatracker <noreply@ietf.org>
wrote:

>
> In particular, the draft mandates that rate limiting is implemented on the
> exported packets, limiting the exporting data rate to 1/N of the interface
> bandwidth (where N can be configured, but defaults to 100). This limits the
> amount of traffic that can be generated, but still appears to allow for a
> significant amplification attack where a single injected IOAM packet can
> trigger flows up to 1% of link capacity (in the default setting) from on
> path
> routers. The provision of a rate limit is therefore important, but I’m
> concerned that it’s not sufficient to prevent abuse.

[BA] That was my take as well. I like the idea of “consent” combined with a
rate limit and perhaps a “circuit breaking” mechanism in extreme cases.

>
> It may be worth considering to require the exporting mechanism to perform
> an
> authenticated handshake with the destination to which it will export data,
> to
> gain explicit consent to export the data to that destination, before
> starting
> to send exported data.  It may also be worth considering to add
> authentication
> of IOAM DEX triggers, to ensure they come from a known and trusted source,
> before acting on export requests.
>
>
>
> _______________________________________________
> Tsv-art mailing list
> Tsv-art@ietf.org
> https://www.ietf.org/mailman/listinfo/tsv-art
>