Subject: Re: [lmap] comments on lmap-requirements - terminology

From: Henning Schulzrinne <[email-masked]>
Date: Mon, 5 Nov 2012 01:38:32 +0000

Sent: Tuesday, September 25, 2012 12:08 PM

In these cases, as Marcelo and Al point out, the definition of client and server are probably not quite right / too specific. Indeed, if the measurement protocol itself is a "pluggable" thing, then the measurement client and server aren't really part of the LMAP architecture; there's simply a measurement _point_ -- if that's an active client, or an active server, or a passive observation point isn't really relevant, and the other side of the measurement is simply a parameter of the request to the measurement point.

I agree that the terminology could use work. I see two types of entities - the large-scale (possibly millions) entity that largely does the bidding of the controller(s), and the much smaller number of controllers. The measurement server (as named currently) is really only necessary for active measurements, so suggestions for a name are appreciated. "Active measurement sink" is one option.

Best regards,

Brian