Subject: [mile] Proposal for adding predefined courses of action

From: "Roman D. Danyliw" <[email-masked]>
Date: Thu, 19 Dec 2013 21:16:45 +0000

Hello!

Ticket #32 (http://tools.ietf.org/wg/mile/trac/ticket/32) outlines the need for a means to specify a predetermined course of action (COA) in the Expectation and HistoryItem class.  Five implementation options were suggested.  After review, I would propose adoption of a blend of #4 and #5.

<proposal>
** Add a class named "DefinedCOA" to Expectation and History Item

   +-------------------+
   | Expectation       |
   +-------------------+
   | ENUM restriction  |<>--{0..*}--[ Description ]
   | ENUM severity     |<>--{0..*}--[ DefinedCOA  ]
   | ENUM action       |<>--{0..1}--[ StartTime   ]
   | STRING ext-action |<>--{0..1}--[ EndTime     ]
   |                   |<>--{0..1}--[ Contact     ]
   +-------------------+

DefinedCOA

      Zero or many.  ML_STRING.  A unique identifier meaningful to the sender and recipient of this document that references a course of action.  This class must be present if the action attribute is set to "defined-coa".

** Add an "defined-coa" to @action in Expectation and HistoryItem

17.  defined-coa.  Perform a predefined course of action (COA).  The COA is named in the DefinedCOA class.

</proposal>

Examples of this approach would look like the following:

[Example 1]

<!-- simple example, no details provided -->

<Expectation action="defined-coa">

   <DefinedCOA>Procedure-A</DefinedCOA>

[Example 2]

<!-- preserves the type of action taken -->

<!-- distinguishes Description from COA easing parsing complexity -->

<Expectation action="watch-and-warning">

   <Description>Do the following ...</Description>
   <DefinedCOA>Procedure-A</DefinedCOA>

[Example 3]

<!-- multiple COA requested -->

<Expectation action="defined-coa">

   <DefinedCOA>Procedure-A</DefinedCOA>

   <DefinedCOA>Procedure-B</DefinedCOA>

Roman