RE: scalar-unit.size for bit rates?

[Arturo Martin De Nicolas <arturo.martin-de-nicolas@ericsson.com>]

Hello Chris,

 

Thanks for the info. I didn’t recall it, or was not aware of it. It exactly addresses the point.

 

Best regards,

Arturo

 

 

From: Chris Lauwers <lauwers@ubicity.com>
Sent: Wednesday, June 13, 2018 7:35 PM
To: Arturo Martin De Nicolas <arturo.martin-de-nicolas@ericsson.com>; Matthew Rutkowski (mrutkows@us.ibm.com) <mrutkows@us.ibm.com>; claude.noshpitz@att.com
Cc: tosca@lists.oasis-open.org
Subject: RE: scalar-unit.size for bit rates?

 

Hi Arturo,

 

As you may recall, we introduced a new scalar-unite.bitrate type in v1.3 for exactly this purpose.

 

Thanks,

 

Chris

 

From: Arturo Martin De Nicolas <arturo.martin-de-nicolas@ericsson.com>
Sent: Wednesday, June 13, 2018 4:55 AM
To: Matthew Rutkowski (mrutkows@us.ibm.com) <mrutkows@us.ibm.com>; Chris Lauwers <lauwers@ubicity.com>; claude.noshpitz@att.com
Cc: tosca@lists.oasis-open.org
Subject: scalar-unit.size for bit rates?

 

Hi,

 

Yesterday, there was a proposal in ETSI NFV SOL001 to use the scalar-unit.size type for the properties that indicate the virtual link bit rates, but we had doubts it is appropriate.  What’s your opinion? If it is not appropriate, do we need a new scalar type to indicate bit rates?

 

Alternative is to use an integer type.

 

Best regards,

Arturo