Draft: draft-ietf-sacm-terminology

Commentary: In order to update the current draft ( which will expire soon ) , I would propose to pull the current reconciliation version into master and prepare a commit ( so we do not submit in the last minute ) . 
 Hardware Component from 13 into 15 ... Segregate the definition from exposition ; ensure expositional text mentions the composite nature and that it is referenced PSA . Remove MIB bit .
In the context of SACM, an assertion is the output of a SACM
component in the form of a statement (including metadata about the
data source and data origin, e.g. timestamps).  While the validity of
an assertion cannot be verified without, for example, an additional
attestation protocol, an assertion (and therefore a statement,
respectively) can be accomplished by evidence of the validity of its
metadata provided by a SACM component.
An assessment is a specific workflow that incorporates the SACM
tasks discovery, collection and evaluation.  A prominent instance
of the assessment workflow is illustrated in the Vulnerability
Assessment Scenario I-D.ietf-sacm-vuln-scenario.
In the context of SACM, an assertion is the output of a SACM
Component in the form of a SACM Statement (including metadata
about the data source and data origin, e.g. timestamps).  While
the validity of an assertion about Content and Content Metadata
cannot be verified without, for example, Integrity Proofing of the
Data Source, an assertion (and therefore a SACM statement,
respectively) of the validity of Statement Metadata can by enabled
by including corresponding Integrity Evidence created by the Data
Origin.
Is a system resource, as defined in RFC4949, that may be composed
of other assets.
Examples of Assets include: Endpoints, Software, Guidance, or
X.509 public key certificates.  An asset is not necessarily owned
by an organization.
Is a SACM Role that contains functions to receive information from
other SACM Components.
A SACM Role that requires a SACM Component to include SACM
Functions enabling it to receive information from other SACM
Components.
The SACM architecture and corresponding models focus on data in
motion.
In the context of SACM, data models for data at rest are out of
scope.
In SACM work-flows, (Target) Endpoint Characteristics are
represented via Information Elements.
Input directing SACM processes or tasks.
Machine-processable input directing SACM processes or tasks.
Prominent examples include: modification of the configuration of a
SACM component or updating a target endpoint profile that resides
on an evaluator.  In essence, guidance is transported via the
management plane.
The composition of an endpoint can be changed over time by adding
or removing hardware components.  In essence, every physical
endpoint is potentially a composite of multiple hardware
components, typically resulting in a hierarchical composition of
hardware components.  The composition of hardware components is
based on interconnects provided by specific hardware types (e.g. a
mainboard is a hardware type that provides local busses as an
interconnect or an FRU is a hardware type that is itself connected
via an interconnect to a chassis and can provide further
interconnects for additional hardware components, such as
interfaces modules).  In general, a hardware component can be
distinguished by its serial number.  Occasionally, hardware
components are referred to as power sucking aliens.
The composition of an endpoint can be changed over time by adding
or removing hardware components.  In essence, every physical
endpoint is potentially a composite of multiple hardware
components, typically resulting in a hierarchical composition of
hardware components.  The composition of hardware components is
based on interconnects provided by specific hardware types (e.g.
FRU in a chassis are connected via redundant busses).  In general,
a hardware component can be distinguished by its serial number.
Occasionally, hardware components are referred to as power sucking
aliens.
Is an architectural component providing common functions to steer
the behavior of SACM components, e.g. their behavior on the
control plane.
Prominent examples include: modification of the configuration of a
SACM component or updating a target endpoint profile that resides
on an evaluator.  In essence, guidance is transported via the
management plane.  Typically, a SACM component can fulfill its
purpose without continuous input from the management plane.  In
contrast, without continuous availability of control plane
functions a typical SACM component could not function properly.
In general, interaction on the management plane is less frequent
and less regular than on the control plane.  Input via the
management plane can be manual (e.g. via a CLI), or can be
automated via management plane functions that are part of other
SACM components.
An architectural component providing common functions to steer the
behavior of SACM components, e.g. their behavior on the control
plane.
Typically, a SACM component can fulfill its purpose without
continuous input from the management plane.  In contrast, without
continuous availability of control plane functions a typical SACM
component could not function properly.  In general, interaction on
the management plane is less frequent and less regular than on the
control plane.  Input via the management plane can be manual (e.g.
via a CLI), or can be automated via management plane functions
that are part of other SACM components.
A layer-specific address that follows a layer-specific address
scheme.
The following characteristics are a summery derived from the
Common Information Model and ITU-T X.213.  Each Network Interface
of a specific layer can be associated with one or more addresses
appropriate for that layer.  There is no guarantee that a network
address is globally unique.  A dedicated authority entity can
provide a level of assurance that a network address is unique in
its given scope.  In essence, there is always a scope to a network
address, in which it is intended to be unique.
An Endpoint is connected to a network via one or more Network
Interfaces.  Network Interfaces can be physical (Hardware
Component) or logical (virtual Hardware component, i.e. a
dedicated Software Component).  Network Interfaces of an Endpoint
can operate on different layers, most prominently what is now
commonly called layer 2 and 3.  Within a layer, interfaces can be
nested.
In SACM, the association of Endpoints and Network Addresses via
Network Interfaces is vital to maintain interdependent autonomous
processes that can be targeted at Target Endpoints, unambiguously.
Examples include: physical Ethernet port, layer 2 VLAN interface,
a MC-LAG setup, layer 3 Point-to-Point tunnel ingress or egress.
A behavioral aspect of a SACM component that provides external
SACM Interfaces or internal interfaces to other SACM Functionse.
For example, a SACM Function with SACM Interfaces on the Control
Plane can provide a brokering function to other SACM Components.
Via Data Plane interfaces, a SACM Function can act as a provider
and/or as a consumer of information.  SACM Functions can be
propagated as the Capabilities of a SACM Component and can be
discovered by or negotiated with other SACM Components.
Local state is created by the interaction of components with other
components via the control plane, via processing data plane
payload, or via the functional properties of local hardware and
software components.  Dynamic configuration (e.g.  IP address
distributed dynamically via an address distribution and management
services, such as DHCP) is considered state that is the result of
the interaction with another component that provides configuration
via the control plane (e.g. provided by a DHCP server with a
specific configuration).
A statement is a subject defined in the SACM information model.
When a statement is used to provide content to a SACM domain, it
is a top-level subject that bundles Content Elements into one
subject and includes metadata about the data origin.
Local state is created by the interaction of components with other
components via the control plane, via processing data plane
payload, or via the functional properties of local hardware and
software components.  Dynamic configuration (e.g.  IP address
distributed dynamically via an address distribution and management
services, such as DHCP) is considered state that is the result of
the interaction with another component (e.g. provided by a DHCP
server with a specific configuration).
A statement is the root/top-level subject defined in the SACM
information model.
A statement is used to bundle Content Elements into one subject
and includes metadata about the data origin.
An address that is layer specific and which follows layer specific
address schemes.
Each interface of a specific layer can be associated with one or
more addresses appropriate for that layer.  There is no guarantee
that an address is globally unique.  In general, there is a scope
to an address in which it is intended to be unique.
Defined in RFC4949 as "with respect to a data object, a label or
marking in which is recorded the time (time of day or other
instant of elapsed time) at which the label or marking was affixed
to the data object" and as "with respect to a recorded network
event, a data field in which is recorded the time (time of day or
other instant of elapsed time) at which the event took place.".
This term is used in SACM to describe a recorded point in time at
which, for example, an information element is created or updated
on a target endpoint, and observed, transmitted or processed by a
SACM component.  Timestamps can be created by target endpoints or
SACM components and are associated with SACM statements provided
or consumed by SACM components.  Outside of the domain of SACM
components the assurance of correctness of time stamps is
typically significantly lower than inside a SACM domain.  In
general, it cannot be simply assumed that the source of time a
target endpoint uses is synchronized or trustworthy.
Defined in RFC4949 as "with respect to a data object, a label or
marking in which is recorded the time (time of day or other
instant of elapsed time) at which the label or marking was affixed
to the data object".
A timestamp always requires context, i.e. additional information
elements that are associated with it.  Therefore, all timestamps
wrt information elements are always metadata.  Timestamps in SACM
Content Elements may be generated outside a SACM Domain and may be
encoded in an unknown representation.  Inside a SACM domain the
representation of timestamps is well-defined and unambiguous.