Re: [lmap] AD evaluation: draft-ietf-lmap-information-model-16

[Alissa Cooper <[e-mail]>]

> On Feb 8, 2017, at 10:23 AM, Juergen Schoenwaelder <[e-mail]> wrote:
> 
> On Tue, Feb 07, 2017 at 10:26:30AM -0500, Alissa Cooper wrote:
>> 
>>> On Jan 31, 2017, at 2:47 PM, Juergen Schoenwaelder <[e-mail]> wrote:
>>> 
>>> On Tue, Jan 31, 2017 at 09:15:52AM -0500, Alissa Cooper wrote:
>>>> 
>>>>> On Jan 31, 2017, at 4:44 AM, Juergen Schoenwaelder <[e-mail]> wrote:
>>>>>> 
>>>>> 
>>>>> The status reports go to the LMAP controller, so I do not really see
>>>>> why there is a specific risk since the controller has access to the
>>>>> device ID anyway.
>>>> 
>>>> I still am missing what is the rationale for sending the device ID in the status reports. I thought the agent ID was meant to uniquely identify the MA.
>>>> 
>>> 
>>> So here we go. I propose the following change:
>>> 
>>> - The ma-status-agent-id becomes optional.
>>> - The ma-status-device-id becomes mandatory again.
>>> 
>>> Rationale:
>>> 
>>> If a device does not yet have an MA-ID, then the device-id must be
>>> accessible such that the controller can configure an MA-ID.
>> 
>> Section 3.1 says:
>> 
>> "The MA may be pre-configured with an MA ID, or may use a Device ID in
>>   the first Controller contact before it is assigned an MA ID.  The
>>   Device ID may be a MAC address or some other device identifier
>>   expressed as a URI.  If the MA ID is not provided at this stage then
>>   it must be provided by the Controller during Configuration.”
>> 
>> Why would an MA be sending a status report before configuration?
>> 
> 
> The ma-status-obj models status information, it is not modeling a
> status report. I think the reason for having the device-id in the
> status information is that this is the only way to obtain it if it is
> not configured.

Ok. But in a setup where the controller doesn’t actually need the device-id (because the agent-id is pre-configured and the controller uses that to uniquely identify the MA), this requires the device-id to be divulged to the controller unnecessarily. That case could be accommodated by making both the agent-id and the device-id optional and specifying that the device-id should be provided if it was not provided in pre-configuration.

Alissa

> 
> /js
> 
> -- 
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   [phone]         <http://www.jacobs-university.de/>