Differences in Derived Data Types of

Managed Object Model for virtual MRF

Managed Information Model (MIM) identity
     Name   : MrfMOM
     Version : 2
     Release : 6
     Correction : 0
    

Compared to

MergedModel


Managed Information Model (MIM) identity
     Name   : MrfMOM
     Version : 2
     Release : 5
     Correction : 0
    

 

Contents

derivedDataType ComSnmp_Snmp_engineId new
derivedDataType SEC_CertM_NodeCredential_enrollmentTimer new
derivedDataType SEC_CertM_NodeCredential_subjectAltName new
derivedDataType CipherList changed
derivedDataType DateTime changed
derivedDataType DateTimeWithoutOffset changed
derivedDataType DifferenceFromUTC changed
derivedDataType Fingerprint changed
derivedDataType ProbableCause changed
 

 
derivedDataType ComSnmp_Snmp_engineId
derivedDataType SEC_CertM_NodeCredential_enrollmentTimer
derivedDataType SEC_CertM_NodeCredential_subjectAltName
derivedDataType CipherList
description
  Derived string for the specification of a cipher suite list.

Contains colon-delimited (':') cipher strings that can be of any value of the members contained by a Cipher struct. A cipher string indicates an individual cipher or a set of ciphers that use the same protocol version, key exchange etc. The cipher strings can be combined in logical order and operation by character '+'. They can be optionally preceded by either an '!' or a '-' character. Character '!' means that the preceded cipher suite or cipher suite type is permanently deleted from the list. Character '-' means that the preceded cipher suite or cipher suite type is deleted from the list, but any of the cipher suites can be added by later options.

They must contain at least one positive expression, that is, without character '!' or '-' in the cipher string, otherwise the filter results in an empty cipher suite list.

Cipher strings with special meaning:
ALL - all cipher suites except for the NULL encryption ciphers, which must be explicitly enabled. NULL authentication ciphers are included.
DEFAULT - all cipher suites except the NULL authentication and NULL encryption ciphers.


Example:

ALL:!SSLv2:!RSA:!aRSA:!3DES:!DES:!MD5
ALL:!EXP-EDH-RSA-DES-CBC-SHA
AES:-kRSA
AES:RC4
kEDH+EXPORT:-MD5

The examples above demonstrate the syntax only and may contain unsupported cipher suites.


derivedDataType DateTime
domainExtension
validationRules
description
  Represents the International Standard international standard for the representation of date and time ( ISO 8601) . 8601).
The string format is "YYYY-MM-DDThh:mm:ss.SSSZ" (excluding quotes).
A DateTime string consists of a date part, a time part, and an optional time zone information part. The time zone part may be a "Z" "Z", representing UTC the Coordinated Universal Time (UTC) time zone (equals to +00) or a time zone offset (e.g., (for example, +02:00).
If the time zone part is not present, the DateTime value represents local time.

The following pattern describes the DateTime format in detail: format:
YYYY-MM-DDThh:mm:ss[.S+][Z|+-hh:mm]
Where:
YYYY = four Four digit year
MM = two Two digit month (01=January, etc.) and so on)
DD = two Two digit day of month (01 through 31)
T = time Time designator (shows start of time component)
hh = two Two digits of hour (00 through 23, AM/PM not allowed)
mm = two Two digits of minute (00 through 59)
ss = two Two digits of second (00 through 59, leap second not allowed)
S+ = one One or more digits of decimal fraction of a second
Z = time is Coordinated Universal Time (UTC) is UTC
+- = + or - character indicating positive or negative offset to UTC

DateTime values are compliant with ISO 8601 "Representation of dates and times" but are restricted according to RFC 3339 "Date and Time on the Internet: Timestamps". The DateTime format is further restricted: restricted as follows:
- T and Z designators are upper case.
- . (dot) is used to indicate start of fractions of seconds (ISO 8601 also allows comma)


baseType
string
stringLength
validValues
old:  ^([0-9]{4})-(1[0-2]|0[1-9])-(0[1-9]|[1|2][0-9]|3[0-1])T(0[0-9]|1[0-9]|2[0-3]):([0-5][0-9]):([0-5][0-9])([\.][0-9]+)*(([\+|\-](0[0-9]|1[0-9]|2[0-4])(:[0-5][0-9])?)|(Z)?)$
new:  ^([0-9]{4})-(1[0-2]|0[1-9])-(0[1-9]|[1|2][0-9]|3[0-1])T(0[0-9]|1[0-9]|2[0-3]):([0-5][0-9]):([0-5][0-9])([\.][0-9]+){0,1}(([\+|\-](0[0-9]|1[0-9]|2[0-4])(:[0-5][0-9])?)|(Z)?)$

derivedDataType DateTimeWithoutOffset
domainExtension
validationRules
description
  Represents the international standard for the representation of local date and time ( ISO 8601) . (ISO 8601).
The following pattern describes the DateTimeWithoutOffset format in detail: format:
YYYY-MM-DDThh:mm:ss[.S+]
Where:
YYYY = four Four digit year
MM = two Two digit month (01=January, etc.) and so on)
DD = two Two digit day of month (01 through 31)
T = time Time designator (shows start of time component)
hh = two Two digits of hour (00 through 23, AM/PM not allowed)
mm = two Two digits of minute (00 through 59)
ss = two Two digits of second (00 through 59, leap second not allowed)
S+ = one One or more digits of decimal fraction of a second

DateTimeWithoutOffset values are compliant with ISO 8601 (Representation "Representation of dates and times) times" but are restricted according to RFC 3339 (Date "Date and Time on the Internet: Timestamps). Timestamps". The DateTimeWithoutOffset format is further restricted: restricted as follows:
- T designator is upper case.
- . (dot) is used to indicate start of fractions of seconds (ISO 8601 also allows comma)


baseType
string
stringLength
validValues
old:  ^([0-9]{4})-(1[0-2]|0[1-9])-(0[1-9]|[1|2][0-9]|3[0-1])T(0[0-9]|1[0-9]|2[0-4]):([0-5][0-9]):([0-5][0-9])([\.][0-9]+)*$
new:  ^([0-9]{4})-(1[0-2]|0[1-9])-(0[1-9]|[1|2][0-9]|3[0-1])T(0[0-9]|1[0-9]|2[0-3]):([0-5][0-9]):([0-5][0-9])([\.][0-9]+){0,1}$

derivedDataType DifferenceFromUTC
domainExtension
validationRules
description
  Time zone difference between the local current time and UTC (Coordinated Coordinated Universal Time). Time (UTC).
The following format shall be used is as follows:
[+/-]hh:mm

It is expressed as positive (i.e. (that is, with the leading plus sign [+]) if the local time is ahead of or equal to UTC of day and as negative (i.e. (that is, with the leading minus sign [-]) if it is behind UTC. the UTC of day.
Example: +01:00
baseType
string
stringLength

derivedDataType Fingerprint
description
  A derived string type that allows hexadecimal digits.

The string must be entered in two-digit groups separated by colons. For example: b7:a8:c6:d5:43:fa:50:43 'b7:a8:c6:d5:43:fa:50:43'

derivedDataType ProbableCause
description
  Probable cause as specified in ITU recommendations M.3100, X.733 and X.736, and in ETSI recommendation GSM 12.11. This attribute value corresponds a Probable cause number. Reference the Ericsson Alarm Probable Cause MIB 4/196 03-CXC 172 7549 (Rev. A) recommendations.
The values are aligned
to see the valid values for probable causes. ERICSSON-ALARM-MIB.



  Differences in Derived Data Types