The SecurityParameters contains the signature of a NSD, VLD, PNFD or VNFFGD instance together with information required to validate the signature.
Provides the signature of the signed part of the descriptor.
Identifies the algorithm used to compute the signature.
Provides a certificate or a reference to a certificate to validate the signature.
NOTE: Cardinality of 0 corresponds to the case where the certificate is provided by means outside the NSD
This primitive type defines the version of an element.
type string {
pattern
'[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}'; }
A Universally Unique IDentifier in the string representation defined in RFC 4122. The canonical representation uses lowercase characters.
The following is an example of a UUID in string representation: f81d4fae-7dec-11d0-a765-00a0c91e6bf6 ";
reference
"RFC 4122: A Universally Unique IDentifier (UUID) URN Namespace"
type string;
The uri type represents a Uniform Resource Identifier (URI) as defined by STD 66.
Objects using the uri type MUST be in US-ASCII encoding, and MUST be normalized as described by RFC 3986 Sections 6.2.1, 6.2.2.1, and 6.2.2.2. All unnecessary percent-encoding is removed, and all case-insensitive characters are set to lowercase except for hexadecimal digits, which are normalized to uppercase as described in Section 6.2.2.1.
The purpose of this normalization is to help provide unique URIs. Note that this normalization is not sufficient to provide uniqueness. Two URIs that are textually distinct after this normalization may still be equivalent.
Objects using the uri type may restrict the schemes that they permit. For example, 'data:' and 'urn:' schemes might not be appropriate.
A zero-length URI is not a valid URI. This can be used to express 'URI absent' where required.
In the value set and its semantics, this type is equivalent to the Uri SMIv2 textual convention defined in RFC 5017.
reference
"RFC 3986: Uniform Resource Identifier (URI): Generic Syntax
RFC 3305: Report from the Joint W3C/IETF URI Planning Interest Group: Uniform Resource Identifiers (URIs), URLs, and Uniform Resource Names (URNs): Clarifications and Recommendations
RFC 5017: MIB Textual Conventions for Uniform Resource Identifiers (URIs)"
Primitive type describing a rule.
This primitive type is a superset of the standard UML numbering primitives, e.g. Integer and Real.
priority - processing priority.
object - objects are model elements that represent instances of a class or of classes
key - the key datatype is a tuple which provides the name of a key along with its value and relative order.
keyName - Name of the key.
keyOrder - Relative sequence or order of the key (with respect to other keys).
keyValue - Value of the key.
Specifies the type of rule.
Defines the scope of the rule.
A base / value business entity used to represent a period of time, between two timepoints
An instant of time, starting at the TimePeriod
Notes:
If null, then represents to the beginning of time
An instant of time, ending at the TimePeriod:
Notes:
If null, then represents to the end of time
DateTime - RFC 2822 standard date/time format.
RFC 2822 format
day-of-week, dd MM yyyy HH’:’mm’:’ss ‘GMT’
e.g. Tue, 21 Jun 2016 14:05:20 GMT
the latest unix time aka epoch time associated with the event from any component--as microseconds elapsed since 1 Jan 1970 not including leap seconds
A primitive Type
Legend
Blue - Review Complete
Green - Ready for Review
White - Not Ready for Review
configurableProperties is a datatype
Does NF have a direct asociation to elementgroups, or would that be through a df?
Onboarding??
Onboarding
Abstract
Concrete
Design Time
Runtime
Attributes in Pink are adds (not in IFA 01