On Fri, Mar 23, 2018, 2:41 PM Mats Wichmann <m.wichm...@ieee.org> wrote:
> Here's the full spec for piid: > > A unique and immutable Device identifier. A Client can detect that a >> single Device supports multiple communication protocols if it discovers >> that the Device uses a single Protocol Independent ID value for all the >> protocols it supports. > > > I'm not sure it answers the question. > Yeah, not really. If "single device" means "single di" there would seem to be no need for piid. AFAIK "device" means "uuid called di". > > At least it should be clear pi and di are different things, one "platform" > may host many "devices" (doesn't sound like that was in question anyway). > Yep, that distinction makes sense to me. > > I'm left with some of the same questions - Instead of this clunky > description, oic.wk.res contains an mpro field which lists supported > protocols. Why would you look elsewhere? Or are these different layer > protocols? > Indeed. "Protocol" is way too general a term. I'm guessing there was an original use case motivating this, but I cannot figure it out. Maybe because these things may change during onboarding or crudn ops? G
_______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
