1. Define Schema for subscription event responses coming from DMIs (binary: all good, greetings from DMI-X, none)
2. Collate responses during small timeframe (TBD) and either:
   1. Generate complete outcome (all cm handles)
   2. Generate partial outcome (some cm handles)
3. Send (initial) 'Subscription Create Outcome' as message on topic for Client Apps
   1. Define Schema, includes
      1. Status: COMPLETED | PARTIALLY COMPLETED
      2. Type of event
      3. List of cm handle ids (alternatives nothing, %, n out of m)
4. Send (updated) 'Subscription Create Outcome' as message on topic for Client Apps (same schema as #3) upon each DMI-response AFTER initial small timeframe

Out of scope

• NCMP is NOT responsible for retry (clients are)
• Persistence of Status (future user stories)

A/C

1. Impl proposal should record stakeholder decision like
   1. initial timeframe duration
   2. need for partial completed details
2. Agree 'Subscription Event Response' schema with team & stakeholders 
3. Agree 'Subscription Create Outcome' schema with stakeholders (allowing for  multiple future operation )
4. ONAP DMI PLugin will send 'Subscription Create Event'
5. Demo with multiple (stubbed?) ONAP DMI PLugins (using different ports)
   1. all response immediately
   2. one or more respond 'late'