Subject: [mile] Clarifying the use of indicator-uid and set-id

From: "Roman D. Danyliw" <[email-masked]>
Date: Mon, 20 Jan 2014 18:14:39 +0000

Hello!

The response to scoping discussion #2 [1] and the subsequent discussion around conveying timing information [2] began the specification of @indicator-uid and @indicator-set-id in 5070bis.  We agreed that if an element had either an @indicator-uid or set-id then all aggregated elements nested in it were considered part of the indicator.

A few basic question still remain.  This note is an attempt to clarify the community's desires.

(1) What is the format of the of @indicator-uid? @indicator-set-id?

(2) Is the @indicator-uid identifier unique to the document (probably not?)? Unique to a given sender or recipient?  Globally unique (like IncidentID)?

(3) Is there an assumption of shared state between a sender and recipient?  Should a recipient understand/recognize the @indicator-uid or @indicator-set-id, or will it be an opaque blob?

(4)  If there is shared state between the sender and recipient, what should be done when a recipient gets an @indicator-set-id it doesn't recognize?

(5) How should a recipient interpret an indicator that has an @indicator-set-id but no @indicator-uid?

(6) If an indicator is given an @indicator-uid and @indicator-set-id, is it assumed that the uid is part of the described set?

[1] http://www.ietf.org/mail-archive/web/mile/current/msg01182.html
[2] http://www.ietf.org/mail-archive/web/mile/current/msg01256.html

Roman