PSARC 2008/498 datalink sysevents

[Garrett D'Amore]

RCM is "normally" (historically, anyway) used for device *removal*, 
rather than addition.

What do you intend the RCM module to do with this event?

    -- Garrett

Cathy Zhou wrote:
> This event will be consumed by a syseventd module which in turn will 
> generate a RCM event which will then be consumed by the RCM modules.
>
> But the usage of the EC_DATALINK class would not be limited to this.
>
> - Cathy
>
>> completeness question: who's the intended consumer for this event?
>>
>>    Kais
>>
>> Sebastien Roy wrote:
>>> I'm submitting this case for Cathy Zhou.  It is being filed as closed
>>> approved automatic.
>>>
>>> Datalink sysevents
>>> ------------------
>>>
>>> release binding: patch
>>>
>>> Summary
>>> -------
>>>
>>>     This case proposes to introduce a new EC_DATALINK sysevent class to
>>>     report data-link related sysevents.  For now, only one subclass
>>>     (ESC_DATALINK_PHYS_ADD) will be introduced.  It will be generated
>>>     when a new physical data-link shows up on the system.  In the 
>>> future,
>>>     the EC_DATALINK sysevent class can be extended to report other
>>>     data-link sysevents, such as a data-link renaming event.
>>>
>>>     Since we are still experimenting the new sysevent class, the format
>>>     of the ESC_DATALINK_PHYS_ADD sysevent will be classified as Project
>>>     Private.
>>>
>>> Interface Table
>>> ---------------
>>>
>>>      -------------------------------------------------------------
>>>      Interface               Commitment Level         Comments
>>>      -------------------------------------------------------------
>>>      EC_DATALINK             Consolidation Private    Event class
>>>      ESC_DATALINK_PHYS_ADD   Project Private          Event subclass
>>>
>>>
>>>
>>>   
>>
>