[mile] Definition of Contact@role value

"Roman D. Danyliw" <rdd@cert.org> Mon, 29 July 2013 13:54 UTC

From: "Roman D. Danyliw" <rdd@cert.org>
To: "mile@ietf.org" <mile@ietf.org>
Thread-Topic: Definition of Contact@role value
Thread-Index: Ac6MU+caXs+MWqFrR0CoutO8XzK6Cw==
Date: Mon, 29 Jul 2013 13:52:51 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFC13C561D2@marathon>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [mile] Definition of Contact@role value
Precedence: list

Hi!

Contact@role currently has the following enumerated values:

1.  creator.  The entity that generate the document.
2.  admin.  An administrative contact for a host or network.
3.  tech.  A technical contact for a host or network.
4.  irt.  The CSIRT involved in handling the incident.
5.  cc.  An entity that is to be kept informed about the handling of the incident.
6.  ext-value.  An escape value used to extend this attribute.

This text from RFC5070 strikes me as fairly ambiguous.  Do these read more clearly?

1.  creator.  The entity that reported the event or activity.
2.  admin.  The business owner of a host or network.
3.  tech.  The entity managing the host or network.
4.  irt. The primary CSIRT responding to this event or activity.
5.  cc.  same as above
6.  ext-value.  same as above

Is there a need to define additional roles?  Perhaps, the following:

7. user.  The end-user of the host or network
8. cc-irt.  The CSIRT or ISAC coordinating response to this event or activity

Roman

[mile] Definition of Contact@role value Roman D. Danyliw