[art] conflict review for draft-grimminck-safe-ioc-sharing

[Andy Newton <[e-mail]>]

Hi all,

I am conducting a conflict review for the IESG on draft-grimminck-safe-ioc-sharing [1].

Conflict reviews are governed by RFC5742 [2].

For convenience, the abstract is:

    This document codifies a consistent and reversible convention used in
    the threat intelligence and security communities for sharing
    potentially malicious indicators of compromise (IOCs), such as URLs,
    IP addresses, email addresses, and domain names.  It describes a safe
    obfuscation format that reduces the risk of accidental execution or
    activation when IOCs are displayed or transmitted.  The
    transformation renders an indicator syntactically invalid as a URI
    while keeping it recognizable to a human reader, and the original
    value can be recovered deterministically.  Safe-IOC strings are a
    textual rendering convention, not URIs, and are not intended to be
    processed by generic URI parsers.  These conventions aim to improve
    interoperability among tools and feeds that exchange threat
    intelligence data.

I am unaware of any work in the IETF conflicting with this document, but I don't know everything.
If you are aware of any conflicts with IETF work, please respond either to this list or to me privately.

-andy, ART AD


[1] https://datatracker.ietf.org/doc/draft-grimminck-safe-ioc-sharing/
[2] https://www.rfc-editor.org/info/rfc5742/