<?xml version="1.0" encoding="UTF-8"?>
  <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
  <!-- generated by https://github.com/cabo/kramdown-rfc2629 version 1.2.9 -->

<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
]>

<?rfc toc="yes"?>
<?rfc sortrefs="yes"?>
<?rfc symrefs="yes"?>

<rfc ipr="trust200902" docName="draft-ietf-sacm-terminology-16" category="info">

  <front>
    <title abbrev="SACM Terminology">Security Automation and Continuous Monitoring (SACM) Terminology</title>

    <author initials="H." surname="Birkholz" fullname="Henk Birkholz">
      <organization abbrev="Fraunhofer SIT">Fraunhofer SIT</organization>
      <address>
        <postal>
          <street>Rheinstrasse 75</street>
          <city>Darmstadt</city>
          <code>64295</code>
          <country>Germany</country>
        </postal>
        <email>henk.birkholz@sit.fraunhofer.de</email>
      </address>
    </author>
    <author initials="J." surname="Lu" fullname="Jarrett Lu">
      <organization>Oracle Corporation</organization>
      <address>
        <postal>
          <street>4180 Network Circle</street>
          <city>Santa Clara</city>
          <region>CA</region>
          <code>95054</code>
          <country>USA</country>
        </postal>
        <email>jarrett.lu@oracle.com</email>
      </address>
    </author>
    <author initials="J." surname="Strassner" fullname="John Strassner">
      <organization>Huawei Technologies</organization>
      <address>
        <postal>
          <street>2330 Central Expressway</street>
          <city>Santa Clara</city>
          <region>CA</region>
          <code>95138</code>
          <country>USA</country>
        </postal>
        <email>john.sc.strassner@huawei.com</email>
      </address>
    </author>
    <author initials="N." surname="Cam-Winget" fullname="Nancy Cam-Winget">
      <organization>Cisco Systems</organization>
      <address>
        <postal>
          <street>3550 Cisco Way</street>
          <city>San Jose</city>
          <region>CA</region>
          <code>95134</code>
          <country>USA</country>
        </postal>
        <email>ncamwing@cisco.com</email>
      </address>
    </author>
    <author initials="A." surname="Montville" fullname="Adam Montville">
      <organization abbrev="CIS">Center for Internet Security</organization>
      <address>
        <postal>
          <street>31 Tech Valley Drive</street>
          <city>East Greenbush</city>
          <region>NY</region>
          <code>12061</code>
          <country>USA</country>
        </postal>
        <email>adam.w.montville@gmail.com</email>
      </address>
    </author>

    <date year="2018" month="December" day="14"/>

    <area>Security</area>
    <workgroup>SACM Working Group</workgroup>
    <keyword>Internet-Draft</keyword>

    <abstract>


<t>This memo documents terminology used in the documents produced by SACM (Security Automation and Continuous Monitoring).</t>



    </abstract>


  </front>

  <middle>


<section anchor="introduction" title="Introduction">

<t>Our goal with this document is to improve our agreement on the terminology used in documents produced by the IETF Working Group for Security Automation and Continuous Monitoring.  Agreeing on terminology should help reach consensus on which problems we’re trying to solve, and propose solutions and decide which ones to use.</t>

</section>
<section anchor="terms-and-definitions" title="Terms and Definitions">

<t>This section describes terms that have been defined by other RFC’s and defines new ones.  The predefined terms will reference the RFC and where appropriate will be annotated with the specific context by which the term is used in SACM. Note that explanatory or informational augmentation to definitions are segregated from the definitions themselves. The definition for the term immediately follows the term on the same line, whereas expositional text is contained in subsequent paragraphs immediately following the definition.</t>

<t><list style="hanging">
  <t hangText='Assertion:'>
  Defined by the ITU in <xref target="X.1252"/> as “a statement made by an entity without accompanying evidence of its validity”.</t>
  <t>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.</t>
  <t hangText='Assessment:'>
  Defined in <xref target="RFC5209"/> as “the process of collecting posture for a set of capabilities on the endpoint (e.g., host-based firewall) such that the appropriate validators may evaluate the posture against compliance policy.”</t>
  <t hangText='Attribute:'>
  Is a data element, as defined in <xref target="RFC5209"/>, that is atomic.</t>
  <t>In the context of SACM, attributes are “atomic” information elements and an equivalent to attribute-value-pairs.  Attributes can be components of Subjects, the basic composite definitions that are defined in the SACM Information Model.</t>
  <t hangText='Capability:'>
  A set of features that are available from a SACM Component.</t>
  <t>See also “capability” in <xref target="I-D.ietf-i2nsf-terminology"/>.</t>
  <t>In the context of SACM, the extent of a SACM component’s ability is enabled by the functions it is composed of.  Capabilities are registered at a SACM broker (potentially also at a proxy or a repository component if it includes broker functions) by a SACM component via the SACM component registration task and can be discovered by or negotiated with other SACM components via the corresponding tasks.  For example, the capability of a SACM provider may be to provide target endpoint records (declarative guidance about well-known or potential target endpoints), or only a subset of that data.</t>
  <t>A capability’s description is in itself imperative guidance on what functions are exposed to other SACM components in a SACM domain and how to use them in workflows.</t>
  <t>The SACM Vulnerability Assessment Scenario <xref target="I-D.ietf-sacm-vuln-scenario"/> defines the terms Endpoint Management Capabilities, Vulnerability Management Capabilities, and Vulnerability Assessment Capabilities, which illustrate specific sets of SACM capabilities on an enterprise IT department’s point of view and therefore compose sets of declarative guidance.</t>
  <t hangText='Collection Result:'>
  Is a composition of one or more content elements carrying information about a target endpoint, that is produced by a collector when conducting a collection task.</t>
  <t hangText='Collection Task:'>
  A targeted task that collects attributes and/or corresponding attribute values from target endpoint.</t>
  <t>There are four types of frequency collection tasks can be conducted with:</t>
  <t>ad-hoc, e.g. triggered by a unsolicited query</t>
  <t>conditional, e.g. triggered in accordance with policies included in the compositions of workflows</t>
  <t>scheduled, e.g. in regular intervals, such as every minute or weekly</t>
  <t>continuously, e.g. a network behavior observation</t>
  <t>There are three types of collection methods, each requiring an appropriate set of functions to be included in the SACM component conducting the collection task:</t>
  <t>Self-Reporting: A SACM component located on the target endpoint itself conducts the collection task.</t>
  <t>Remote-Acquisition: A SACM component located on an Endpoint different from the target endpoint conducts the collection task via interfaces available on the target endpoint, e.g. SNMP/NETCONF or WMI.</t>
  <t>Behavior-Observation: A SACM component located on an Endpoint different from the target endpoint observes network traffic related to the target endpoint and conducts the collection task via interpretation of that network traffic.</t>
  <t hangText='Collector:'>
  A piece of software that acquires information about one or more target endpoints by conducting collection tasks.</t>
  <t>A collector can be distributed across multiple endpoints, e.g. across a target endpoint and a SACM component.  The separate parts of the collector can communicate with a specialized protocol, such as PA-TNC <xref target="RFC5792"></xref>.  At least one part of a distributed collector has to take on the role of a provider of information by providing SACM interfaces to propagate capabilities and to provide SACM content in the form of collection results.</t>
  <t hangText='Configuration:'>
  A non-volatile subset of the endpoint attributes of a endpoint that is intended to be unaffected by a normal reboot-cycle.</t>
  <t>Configuration is a type of imperative guidance that is stored in files (files dedicated to contain configuration and/ or files that are software components), directly on block devices, or on specific hardware components that can be accessed via corresponding software components.  Modification of configuration can be conducted manually or automatically via management (plane) interfaces that support management protocols, such as SNMP or WMI. A change of configuration can occur during both run-time and down- time of an endpoint.  It is common practice to scheduled a change of configuration during or directly after the completion of a boot-cycle via corresponding software components located on the target endpoint itself.</t>
  <t>Examples: The static association of an IP address and a MAC address in a DHCP server configuration, a directory-path that identifies a log-file directory, a registry entry.</t>
  <t hangText='Configuration Drift:'>
  The disposition of endpoint characteristics to change over time.</t>
  <t>Configuration drift exists for both hardware components and software components.  Typically, the frequency and scale of configuration drift of software components is significantly higher than the configuration drift of hardware components.</t>
  <t hangText='Consumer:'>
  A SACM Role that requires a SACM Component to include SACM Functions enabling it to receive information from other SACM Components.</t>
  <t hangText='Content Element:'>
  Content elements constitute the payload data (SACM content) transferred via statement Subjects emitted by providers of information. Every content element Subject includes a specific content Subject and a corresponding content metadata Subject.</t>
  <t hangText='Content Metadata:'>
  Data about content Subjects. Every content-element includes a content metadata Subject. The Subject can include any information element that can annotate the content transferred. Examples include time stamps or data provenance Subjects.</t>
  <t hangText='Control Plane:'>
  An architectural component that provides common control functions to all SACM components.</t>
  <t>Typically used as a term in the context of routing, e.g. <xref target="RFC6192"/>. SACM components may include authentication, authorization, (capability) discovery or negotiation, registration and subscription. The control plane orchestrates the flow on the data plane according to imperative guidance (i.e. configuration) received via the management plane. SACM components with interfaces to the control plane have knowledge of the capabilities of other SACM components within a SACM domain.</t>
  <t hangText='Controller:'>
  A controller is a SACM Role that is assigned to a SACM component containing control plane functions managing and facilitating information sharing or execute on security functions.</t>
  <t>There are three types of SACM controllers: Broker, Proxy, and Repository. Depending on its type, a controller can also contain functions that have interfaces on the data plane.</t>
  <t hangText='Data Confidentiality:'>
  Defined in <xref target="RFC4949"/> as “the property that data is not disclosed to system entities unless they have been authorized to know the data.”</t>
  <t hangText='Data In Motion:'>
  Data that is being transported via a network; also referred to as “Data in Transit” or “Data in Flight”.</t>
  <t>Data in motion requires a data model to transfer the data using a specific encoding. Typically, data in motion is serialized (marshalling) into a transport encoding by a provider of information and deserialized (unmarshalling) by a consumer of information. The termination points of provider of information and consumer of information data is transferred between are interfaces. In regard to data in motion, the interpretation of the roles consumer of information and provider of information depends on the corresponding OSI layer (e.g. on layer2: between interfaces connected to a broadcast domain, on layer4: between interfaces that maintain a TCP connection). In the context of SACM, consumer of information and provider of information are SACM components.</t>
  <t hangText='Data At Rest:'>
  Data that is stored.</t>
  <t>Data at rest requires a data model to encode the data to be stored. In the context of SACM, data at rest located on a SACM component can be provided to other SACM components via discoverable capabilities.</t>
  <t hangText='Data Integrity:'>
  Defined in <xref target="RFC4949"/> as “the property that data has not been changed, destroyed, or lost in an unauthorized or accidental manner.”</t>
  <t hangText='Data Origin:'>
  The SACM Component that initially acquired or produced data about an endpoint.</t>
  <t>Data Origin enables a SACM component to identify the SACM component that initially acquired or produced data about a (target) endpoint (e.g. via collection from a data source) and made it available to a SACM domain via a SACM statement.  Data Origin can be expressed by an endpoint label information element (e.g. to be used as metadata in statement).</t>
  <t hangText='Data Plane:'>
  Is an architectural component providing operational functions enabling information exchange that is not command and control or management related.</t>
  <t>Typically used as a term in the context of routing (and used as a synonym for forwarding plane, e.g. <xref target="RFC6192"/>). In the context of SACM, the data plane is an architectural component providing operational functions to enable a SACM component to provide and consume SACM statements and therefore SACM content, which composes the actual SACM content. The data plane in a SACM domain is used to conduct distributed SACM tasks by transporting SACM content via specific transport encodings and corresponding operations defined by SACM data models.</t>
  <t hangText='Data Provenance:'>
  An historical record of the sources, origins and evolution, as it pertains to data, that is influenced by inputs, entities, functions and processes.</t>
  <t>Additional Information - In the context of SACM, data provenance is expressed as metadata that identifies SACM statements and corresponding content elements a new statement is created from. In a downstream process, this references can cascade, creating a data provenance tree that enables SACM components to trace back the original data sources involved in the creation of SACM statements and take into account their characteristics and trustworthiness.</t>
  <t hangText='Data Source:'>
  Is an endpoint from which a particular set of attributes and/or attribute values have been collected.</t>
  <t>Data Source enables a SACM component to identify - and potentially characterize - a (target) endpoint that is claimed to be the original source of endpoint attributes in a SACM statement.  Data Source can be expressed as metadata by an endpoint label information element or a corresponding subject of identifying endpoint attributes.</t>
  <t hangText='Endpoint:'>
  Defined in <xref target="RFC5209"/> as “any computing device that can be connected to a network.”</t>
  <t>Additional Information - The <xref target="RFC5209"/> definition continues, “Such devices normally are associated with a particular link layer address before joining the network and potentially an IP address once on the network.  This includes: laptops, desktops, servers, cell phones, or any device that may have an IP address.”</t>
  <t>To further clarify the <xref target="RFC5209"/> definition, an endpoint is any physical or virtual device that may have a network address.  Note that, network infrastructure devices (e.g. switches, routers, firewalls), which fit the definition, are also considered to be endpoints within this document.</t>
  <t>Physical endpoints are always composites that are composed of hardware components and software components. Virtual endpoints are composed entirely of software components and rely on software components that provide functions equivalent to hardware components.</t>
  <t>The SACM architecture differentiates two essential categories of endpoints: Endpoints whose security posture is intended to be assessed (target endpoints) and endpoints that are specifically excluded from endpoint posture assessment (excluded endpoints).</t>
  <t>Based on the definition of an asset, an endpoint is a type of asset.</t>
  <t hangText='Endpoint Attribute:'>
  Is a discreet endpoint characteristic that is computably observable.</t>
  <t>Endpoint Attributes typically constitute Attributes that can be bundled into Subject (e.g. information about a specific network interface can be represented via a set of multiple AVP).</t>
  <t hangText='Endpoint Characteristics:'>
  The state, configuration and composition of the software components and (virtual) hardware components a target endpoint is composed of, including observable behavior, e.g. sys-calls, log-files, or PDU emission on a network.</t>
  <t>In SACM work-flows, (Target) Endpoint Characteristics are represented via Information Elements.</t>
  <t hangText='Endpoint Characterization Task:'>
  The task of endpoint characterization that uses endpoint attributes that represent distinct endpoint characteristics.</t>
  <t hangText='Endpoint Classification:'>
  The categorization of of the endpoint into one or more taxonomic structures.</t>
  <t>Endpoint classification requires declarative guidance in the form of an endpoint profile, discovery results and potentially collection results. Types, classes or the characteristics of an individual target endpoint are defined via endpoint profiles.</t>
  <t hangText='Endpoint Classification Task:'>
  The task of endpoint classification that uses an endpoint’s characteristics to determine how to categorize the given endpoint into one or more taxonomic structures.</t>
  <t hangText='Endpoint Label:'>
  A unique label associated with a unique endpoint.</t>
  <t>Endpoint specializations have corresponding endpoint label specializations. For example, an endpoint label used on a SACM Component is a SACM Component Label.</t>
  <t hangText='Endpoint Management Capabilities:'>
  Enterprise IT management capabilities that are tailored to manage endpoint identity, endpoint information, and associated metadata.</t>
  <t hangText='Evaluation Task:'>
  A task by which an endpoint’s asserted attribute value is evaluated against a policy-compliant attribute value.</t>
  <t hangText='Evaluation Result:'>
  The resulting value from having evaluated a set of posture attributes.</t>
  <t hangText='Expected Endpoint Attribute State:'>
  The policy-compliant state of an endpoint attribute that is to be compared against.</t>
  <t>Sets of expected endpoint attribute states are transported as declarative guidance in target endpoint profiles via the management plane. This, for example, can be a policy, but also a recorded past state. An expected state is represented by an Attribute or a Subject that represents a set of multiple attribute value pairs.</t>
  <t hangText='Guidance:'>
  Machine-processable input directing SACM processes or tasks.</t>
  <t>Examples of such processes/tasks include automated device management, remediation, collection, evaluation. Guidance influences the behavior of a SACM Component and is considered content of the management plane. In the context of SACM, guidance is machine-readable and can be manually or automatically generated or provided. Typically, the tasks that provide guidance to SACM components have a low-frequency and tend to be sporadic.</t>
  <t>There are two types of guidance:</t>
  <t>Declarative Guidance: Guidance that defines the configuration or state an endpoint is supposed to be in, without providing specific actions or methods to produce that desired state. Examples include Target Endpoint Profiles or network topology based requirements.</t>
  <t>Imperative Guidance: Guidance that prescribes specific actions to be conducted or methods to be used in order to achieve an outcome. Examples include a targeted Collection Task or the IP-Address of a SACM Component that provides a registration function.</t>
  <t>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.</t>
  <t hangText='Endpoint Hardware Inventory:'>
  The set of hardware components that compose a specific endpoint representing its hardware configuration.</t>
  <t hangText='Hardware Component:'>
  A distinguishable physical component used to compose an endpoint.</t>
  <t>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.</t>
  <t hangText='Information Element:'>
  A representation of information about physical and virtual “objects of interest”.</t>
  <t>Information elements are the building blocks that constitute the SACM information model. In the context of SACM, an information element that expresses a single value with a specific name is referred to as an Attribute (analogous to an attribute-value-pair). A set of attributes that is bundled into a more complex composite information element is referred to as a Subject. Every information element in the SACM information model has a unique name. Endpoint attributes or time stamps, for example, are represented as information elements in the SACM information model.</t>
  <t hangText='Information Model:'>
  An abstract representation of data, their properties, relationships between data and the operations that can be performed on the data.</t>
  <t>While there is some overlap with a data model, <xref target="RFC3444"/> distinguishes an information model as being protocol and implementation neutral whereas a data model would provide such details. The purpose of the SACM information model is to ensure interoperability between SACM data models (that are used as transport encoding) and to provide a standardized set of information elements for communication between SACM components.</t>
  <t hangText='Interaction Model:'>
  The definition of specific sequences regarding the exchange of messages (data in motion), including, for example, conditional branching, thresholds and timers.</t>
  <t>An interaction model, for example, can be used to define operations, such as registration or discovery, on the control plane. A composition of data models for data in motion and a corresponding interaction model is a protocol.</t>
  <t hangText='Internal Collector:'>
  A collector that runs on a target endpoint to acquire information from that target endpoint.</t>
  <t hangText='Management Plane:'>
  An architectural component providing common functions to steer the behavior of SACM components, e.g. their behavior on the control plane.</t>
  <t>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.</t>
  <t hangText='Network Address:'>
  A layer-specific address that follows a layer-specific address scheme.</t>
  <t>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.</t>
  <t>Examples include: physical Ethernet port with a MAC address, layer 2 VLAN interface with a MAC address, layer 3 interface with multiple IPv6 addresses, layer 3 tunnel ingress or egress with an IPv4 address.</t>
  <t hangText='Network Interface:'>
  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.</t>
  <t>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.</t>
  <t>Examples include: physical Ethernet port, layer 2 VLAN interface, a MC-LAG setup, layer 3 Point-to-Point tunnel ingress or egress.</t>
  <t hangText='Metadata:'>
  Data about data.</t>
  <t>In the SACM information model, data is referred to as Content. Metadata about the content is referred to as Content-Metadata, respectively. Content and Content-Metadata are combined into Subjects called Content-Elements in the SACM information model. Some information elements defined by the SACM information model can be part of the Content or the Content-Metadata. Therefore, if an information element is considered data or data about data depends on which kind of Subject it is associated with. The SACM information model also defines metadata about the data origin via the Subject Statement-Metadata. Typical examples of metadata are time stamps, data origin or data source.</t>
  <t hangText='Posture:'>
  Defined in <xref target="RFC5209"/> as “configuration and/or status of hardware or software on an endpoint as it pertains to an organization’s security policy.”</t>
  <t>This term is used within the scope of SACM to represent the configuration and state information that is collected from a target endpoint in the form of endpoint attributes (e.g. software/hardware inventory, configuration settings, dynamically assigned addresses).  This information may constitute one or more posture attributes.</t>
  <t hangText='Posture Attributes:'>
  Defined in <xref target="RFC5209"/> as “attributes describing the configuration or status (posture) of a feature of the endpoint.  A Posture Attribute represents a single property of an observed state.  For example, a Posture Attribute might describe the version of the operating system installed on the system.”</t>
  <t>Within this document this term represents a specific assertion about endpoint configuration or state (e.g. configuration setting, installed software, hardware) represented via endpoint attributes.  The phrase “features of the endpoint” highlighted above refers to installed software or software components.</t>
  <t hangText='Provider:'>
  A provider is a SACM role assigned to a SACM component that provides role-specific functions to provide information to other SACM components.</t>
  <t hangText='Repository:'>
  A repository is a controller that contains functions to consume, store and provide information of a particular kind.</t>
  <t>Such information is typically data transported on the data plane, but potentially also data and metadata from the control and management plane.  A single repository may provide the functions of more than one specific repository type (i.e. configuration baseline repository, assessment results repository, etc.)</t>
  <t hangText='SACM Broker Controller:'>
  A SACM Broker Controller is a controller that contains control plane functions to provide and/or connect services on behalf of other SACM components via interfaces on the control plane.</t>
  <t>A broker may provide, for example, authorization services and find, upon request, SACM components providing requested services.</t>
  <t hangText='SACM Component:'>
  Is a component, as defined in <xref target="I-D.ietf-i2nsf-terminology"/>, that is composed of SACM capabilities.</t>
  <t>In the context of SACM, a set of SACM functions composes a SACM component.  A SACM component conducts SACM tasks, acting on control plane, data plane and/or management plane via corresponding SACM interfaces.  SACM defines a set of standard components (e.g. a collector, a broker, or a data store).  A SACM component contains at least a basic set of control plane functions and can contain data plane and management plane functions.  A SACM component residing on an endpoint assigns one or more SACM roles to the corresponding endpoint due to the SACM functions it is composed of.  A SACM component “resides on” an endpoint and an endpoint “contains” a SACM component, correspondingly.  For example, a SACM component that is composed solely of functions that provide information would only take on the role of a provider.</t>
  <t hangText='SACM Component Discovery:'>
  The task of discovering the capabilities provided by SACM components within a SACM domain.</t>
  <t>This is likely to be performed via an appropriate set of control plane functions.</t>
  <t hangText='SACM Component Label:'>
  A specific endpoint label that is used to identify a SACM component.</t>
  <t>In content-metadata, this label is called data origin.</t>
  <t hangText='SACM Content:'>
  The payload provided by SACM components to the SACM domain on the data plane.</t>
  <t>SACM content includes the SACM data models.</t>
  <t hangText='SACM Domain:'>
  Endpoints that include a SACM component compose a SACM domain.</t>
  <t>(To be revised, additional definition content TBD, possible dependencies to SACM architecture)</t>
  <t hangText='SACM Function:'>
  A behavioral aspect of a SACM component that provides external SACM Interfaces or internal interfaces to other SACM Functionse.</t>
  <t>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.</t>
  <t hangText='SACM Interface:'>
  An interface, as defined in <xref target="I-D.ietf-i2nsf-terminology"/>, that provides SACM-specific operations.</t>
  <t><xref target="I-D.ietf-i2nsf-terminology"/> defines interface as a “set of operations one object knows it can invoke on, and expose to, another object,” and further defines interface by stating that an interface “decouples the implementation of the operation from its specification. An interface is a subset of all operations that a given object implements. The same object may have multiple types of interfaces to serve different purposes.”</t>
  <t>In the context of SACM, SACM Functions provide SACM Interfaces on the management, control, or data plane. Operations a SACM Interface provides are based on corresponding data model defined by SACM. SACM Interfaces are used for communication between SACM components.</t>
  <t hangText='SACM Proxy Controller:'>
  A SACM Proxy Controller is a controller that provides data plane and control plane functions, information, or services on behalf of another component, which is not directly participating in the SACM architecture.</t>
  <t hangText='SACM Role:'>
  Is a role, as defined in <xref target="I-D.ietf-i2nsf-terminology"/>, that requires the SACM Component assuming the role to bear a set of SACM functions or interfaces.</t>
  <t>SACM Roles provide three important benefits.  First, it enables different behavior to be supported by the same Component for different contexts.  Second, it enables the behavior of a Component to be adjusted dynamically (i.e., at runtime, in response)to changes in context, by using one or more Roles to define the behavior desired for each context. Third, it decouples the Roles of a Component from the Applications that use that Component.”</t>
  <t>In the context of SACM, SACM roles are associated with SACM components and are defined by the set of functions and interfaces a SACM component includes.  There are three SACM roles: provider, consumer, and controller.  The roles associated with a SACM component are determined by the purpose of the SACM functions and corresponding SACM interfaces the SACM component is composed of.</t>
  <t hangText='SACM Statement:'>
  Is an assertion that is made by a SACM Component.</t>
  <t hangText='Security Automation:'>
  The process of which security alerts can be automated through the use of different components to monitor, analyze and assess endpoints and network traffic for the purposes of detecting misconfigurations, misbehaviors or threats.</t>
  <t>Security Automation is intended to identify target endpoints that cannot be trusted (see “trusted” in <xref target="RFC4949"/>. This goal is achieved by creating and processing evidence (assessment statements) that a target endpoint is not a trusted system <xref target="RFC4949"/>.</t>
  <t hangText='Software Package:'>
  A generic software package (e.g. a text editor).</t>
  <t hangText='Software Component:'>
  A software package installed on an endpoint.</t>
  <t>The software component may include a unique serial number (e.g. a text editor associated with a unique license key).</t>
  <t hangText='Software Instance:'>
  A running instance of a software component.</t>
  <t>For example, on a multi-user system, one logged-in user has one instance of a text editor running and another logged-in user has another instance of the same text editor running, or on a single-user system, a user could have multiple independent instances of the same text editor running.</t>
  <t hangText='State:'>
  A volatile set of endpoint attributes of a (target) endpoint that is affected by a reboot-cycle.</t>
  <t>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).</t>
  <t>Examples: The static association of an IP address and a MAC address in a DHCP server configuration, a directory-path that identifies a log-file directory, a registry entry.</t>
  <t hangText='Statement:'>
  A statement is the root/top-level subject defined in the SACM information model.</t>
  <t>A statement is used to bundle Content Elements into one subject and includes metadata about the data origin.</t>
  <t hangText='Subject:'>
  A semantic composite information element pertaining to a system entity that is a target endpoint.</t>
  <t>Like Attributes, subjects have a name and are composed of attributes and/or other subjects. Every IE that is part of a subject can have a quantitiy associated with it (e.g. zero-one, none-unbounded).  The content IE of a subject can be an unordered or an ordered list.</t>
  <t>In contrast to the definitions of subject provided by <xref target="RFC4949"></xref>, a subject in the scope of SACM is neither “a system entity that causes information to flow among objects or changes the system state” nor “a name of a system entity that is bound to the data items in a digital certificate”.</t>
  <t>In the context of SACM, a subject is a semantic composite of information elements about a system entity that is a target endpoint.  Every acquirable subject–as defined in the scope of SACM–about a target endpoint represents and therefore identifies every subject–as defined by <xref target="RFC4949"></xref>–that is a component of that target endpoint.  The semantic difference between both definitions can be subtle in practice and is in consequence important to highlight.</t>
  <t hangText='Supplicant:'>
  A  component seeking to be authenticated via the control plane for the purpose of participating in a SACM domain.</t>
  <t hangText='System Resource:'>
  Defined in <xref target="RFC4949"/> as “data contained in an information system; or a service provided by a system; or a system capacity, such as processing power or communication bandwidth; or an item of system equipment (i.e., hardware, firmware, software, or documentation); or a facility that houses system operations and equipment.”</t>
  <t hangText='Target Endpoint:'>
  Is an endpoint that is under assessment at some point in, or region of, time.</t>
  <t>Every endpoint that is not specifically designated as an excluded endpoint is a target endpoint.  A target endpoint is not part of a SACM domain unless it contains a SACM component (e.g. a SACM component that publishes collection results coming from an internal collector).</t>
  <t>A target endpoint is similar to a device that is a Target of Evaluation (TOE) as defined in Common Criteria and as referenced by {{RFC4949}.</t>
  <t hangText='Target Endpoint Address:'>
  An address that is layer specific and which follows layer specific address schemes.</t>
  <t>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.</t>
  <t>Examples include: physical Ethernet port with a MAC address, layer 2 VLAN interface with a MAC address, layer 3 interface with multiple IPv6 addresses, layer 3 tunnel ingress or egress with an IPv4 address.</t>
  <t hangText='Target Endpoint Characterization:'>
  The description of the distinctive nature of a target endpoint, that is based on its characteristics.</t>
  <t hangText='Target Endpoint Characterization Record:'>
  A set of endpoint attributes about a target endpoint that was encountered in a SACM domain, which are associated with that target endpoint as a result of a Target Endpoint Characterization Task.</t>
  <t>A characterization record is intended to be a representation of an endpoint. It cannot be assured that a record distinctly represents a single target endpoint unless a set of one or more endpoint attributes that compose a unique set of identifying endpoint attributes are included in the record. Otherwise, the set of identifying attributes included in a record can match more than one target endpoints, which are - in consequence - indistinguishable to a SACM domain until more qualifying endpoint attributes can be acquired and added to the record. A characterization record is maintained over time in order to assert that acquired endpoint attributes are either about an endpoint that was encountered before or an endpoint that has not been encountered before in a SACM domain. A characterization record can include, for example, acquired configuration, state or observed behavior of a specific target endpoint. Multiple and even conflicting instances of this information can be included in a characterization record by using timestamps and/or data origins to differentiate them. The endpoint attributes included in a characterization record can be used to re-identify a distinct target endpoint over time. Classes or profiles can be associated with a characterization record via the Classification Task in order to guide collection, evaluation or remediation tasks.</t>
  <t hangText='Target Endpoint Characterization Task:'>
  An ongoing task of continuously adding acquired endpoint attributes to a corresponding record. The TE characterization task manages the representation of encountered target endpoints in the SACM domain in the form of characterization records. For example, the output of a target endpoint discovery task or a collection task can be processed by the characterization task and added to the record. The TE characterization Task also manages these representations of target endpoints encountered in the SACM domain by splitting or merging the corresponding records as new or more refined endpoint attributes become available.</t>
  <t hangText='Target Endpoint Classification Task:'>
  The task of associating a class from an extensible list of classes with an endpoint characterization record. TE classes function as imperative and declarative guidance for collection, evaluation, remediation and security posture assessment in general.</t>
  <t hangText='Target Endpoint Discovery Task:'>
  The ongoing task of detecting previously unknown interaction of a potential target endpoint in the SACM domain. TE Discovery is not directly targeted at a specific target endpoint and therefore an un-targeted task. SACM Components conducting the discovery task as a part of their function are typically distributed and located, for example, on infrastructure components or collect from those remotely via appropriate interfaces. Examples of infrastructure components that are of interest to the discovery task include routers, switches, VM hosting or VM managing components, AAA servers, or servers handling dynamic address distribution.</t>
  <t hangText='Target Endpoint Identifier:'>
  The target endpoint discovery task and the collection tasks can result in a set of identifying endpoint attributes added to a corresponding Characterization Record. This subset of the endpoint attributes included in the record is used as a target endpoint identifier, by which a specific target endpoint can be referenced. Depending on the available identifying attributes, this reference can be ambiguous and is a “best-effort” mechanism. Every distinct set of identifying endpoint attributes can be associated with a target endpoint label that is unique in a SACM domain.</t>
  <t hangText='Target Endpoint Label:'>
  An endpoint label that identifies a specific target endpoint.</t>
  <t hangText='Target Endpoint Profile:'>
  A bundle of expected or desired component composition, configurations and states that is associated with a target endpoint.</t>
  <t>The corresponding task by which the association with a target endpoint takes places is the endpoint classification task. The task by which an endpoint profile is created is the endpoint characterization task. A type or class of target endpoints can be defined via a target endpoint profile. Examples include:  printers, smartphones, or an office PC.</t>
  <t>In respect to <xref target="RFC4949"/>, a target endpoint profile is a protection profile as defined by Common Criteria (analogous to the target endpoint being the target of evaluation).</t>
  <t hangText='SACM Task:'>
  Is a task conducted within the scope of a SACM domain by one or more SACM functions that achieves a SACM-defined outcome.</t>
  <t>A SACM task can be triggered by other operations or functions (e.g. a query from another SACM component or an unsolicited push on the data plane due to an ongoing subscription).  A task is part of a SACM process chain.  A task starts at a given point in time and ends in a deterministic state. With the exception of a collection task, a SACM task consumes SACM statements provided by other SACM components.  The output of a task is a result that can be provided (e.g. published) on the data plane.</t>
  <t>The following tasks are defined by SACM:</t>
  <t>Target Endpoint Discovery</t>
  <t>Target Endpoint Characterization</t>
  <t>Target Endpoint Classification</t>
  <t>Collection</t>
  <t>Evaluation [TBD]</t>
  <t>Information Sharing [TBD]</t>
  <t>SACM Component Discovery</t>
  <t>SACM Component Authentication [TBD]</t>
  <t>SACM Component Authorization [TBD]</t>
  <t>SACM Component Registration [TBD]</t>
  <t hangText='Timestamps :'>
  Defined in <xref target="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”.</t>
  <t>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.</t>
  <t hangText='Virtual Endpoint:'>
  An endpoint composed entirely of logical system components (see <xref target="RFC4949"/>).</t>
  <t>The most common example is a virtual machine/host running on a target endpoint. Effectively, target endpoints can be nested and at the time of this writing the most common example of target endpoint characteristics about virtual components is the EntLogicalEntry in <xref target="RFC6933"/>.</t>
  <t hangText='Vulnerability Assessment:'>
  An assessment specifically tailored to determining whether a set of endpoints is vulnerable according to the information contained in the vulnerability description information.</t>
  <t hangText='Vulnerability Description Information:'>
  Information pertaining to the existence of a flaw or flaws in software, hardware, and/or firmware, which could potentially have an adverse impact on enterprise IT functionality and/or security.</t>
  <t>Vulnerability description information should contain enough information to support vulnerability detection.</t>
  <t hangText='Vulnerability Detection Data:'>
  A type of imperative guidance extracted or derived from vulnerability description information that describes the specific mechanisms of vulnerability detection that is used by an enterprise’s vulnerability management capabilities to determine if a vulnerability is present on an endpoint.</t>
  <t hangText='Vulnerability Management Capabilities:'>
  An IT management capability tailored toward managing endpoint vulnerabilities and associated metadata on an ongoing basis by ingesting vulnerability description information and vulnerability detection data, and performing vulnerability assessments.</t>
  <t hangText='Vulnerability assessment capabilities:'>
  An assessment capability that is tailored toward determining whether a set of endpoints is vulnerable according to vulnerability description information.</t>
  <t hangText='Workflow:'>
  A workflow is a modular composition of tasks that can contain loops, conditionals, multiple starting points and multiple endpoints.</t>
  <t>The most prominent workflow in SACM is the assessment workflow.</t>
</list></t>

</section>
<section anchor="iana-considerations" title="IANA Considerations">

<t>This memo includes no request to IANA.</t>

</section>
<section anchor="security-considerations" title="Security Considerations">

<t>This memo documents terminology for security automation.  While it is about security, it does not affect security.</t>

</section>
<section anchor="acknowledgements" title="Acknowledgements">

</section>
<section anchor="change-log" title="Change Log">

<t>Changes from version 00 to version 01:</t>

<t><list style="symbols">
  <t>Added simple list of terms extracted from UC draft -05.  It is expected that comments will be received on this list of terms as to whether they should be kept in this document.  Those that are kept will be appropriately defined or cited.</t>
</list></t>

<t>Changes from version 01 to version 02:</t>

<t><list style="symbols">
  <t>Added Vulnerability, Vulnerability Management, xposure, Misconfiguration, and Software flaw.</t>
</list></t>

<t>Changes from version 02 to version 03:</t>

<t><list style="symbols">
  <t>Removed Section 2.1.  Cleaned up some editing nits; broke terms into 2 sections (predefined and newly defined terms).  Added some of the relevant terms per the proposed list discussed in the IETF 89 meeting.</t>
</list></t>

<t>Changes from version 03 to version 04:</t>

<t><list style="symbols">
  <t>TODO</t>
</list></t>

<t>Changes from version 04 to version 05:</t>

<t><list style="symbols">
  <t>TODO</t>
</list></t>

<t>Changes from version 05 to version 06:</t>

<t><list style="symbols">
  <t>Updated author information.</t>
  <t>Combined “Pre-defined Terms” with “New Terms and Definitions”.</t>
  <t>Removed “Requirements language”.</t>
  <t>Removed unused reference to use case draft; resulted in removal of normative references.</t>
  <t>Removed introductory text from Section 1 indicating that this document is intended to be temporary.</t>
  <t>Added placeholders for missing change log entries.</t>
</list></t>

<t>Changes from version 06 to version 07:</t>

<t><list style="symbols">
  <t>Added Contributors section.</t>
  <t>Updated author list.</t>
  <t>Changed title from “Terminology for Security Assessment” to “Secure Automation and Continuous Monitoring (SACM) Terminology”.</t>
  <t>Changed abbrev from “SACM-Terms” to “SACM Terminology”.</t>
  <t>Added appendix The Attic to stash terms for future updates.</t>
  <t>Added Authentication, Authorization, Data Confidentiality, Data Integrity, Data Origin, Data Provenance, SACM Component, SACM Component Discovery, Target Endpoint Discovery.</t>
  <t>Major updates to Building Block, Function, SACM Role, Target Endpoint.</t>
  <t>Minor updates to Broker, Capability, Collection Task, Evaluation Task, Posture.</t>
  <t>Relabeled Role to SACM Role, Endpoint Target to Target Endpoint, Endpoint Discovery to Endpoint Identification.</t>
  <t>Moved Asset Targeting, Client, Endpoint Identification to The Attic.</t>
  <t>Endpoint Attributes added as a TODO.</t>
  <t>Changed the structure of the Change Log.</t>
</list></t>

<t>Changes from version 07 to version 08:</t>

<t><list style="symbols">
  <t>Added Assertion, Collection Result, Collector, Excluded Endpoint, Internal Collector, Network Address, Network Interface, SACM Domain, Statement, Target Endpoint Identifier, Target Endpoint Label, Timestamp.</t>
  <t>Major updates to Attributes, Broker, Collection Task, Consumer, Controller, Control Plane, Endpoint Attributes, Expected Endpoint State, SACM Function, Provider, Proxy, Repository, SACM Role, Target Endpoint.</t>
  <t>Minor updates to Asset, Building Block, Data Origin, Data Source, Data Provenance, Endpoint, Management Plane, Posture, Posture Attribute, SACM Component, SACM Component Discovery, Target Endpoint Discovery.</t>
  <t>Relabeled Function to SACM Function.</t>
</list></t>

<t>Changes from version 08 to version 09:</t>

<t><list style="symbols">
  <t>Updated author list.</t>
  <t>Added Data Plane, Endpoint Characterization, Endpoint Classification, Guidance, Interaction Model, Software Component, Software Instance, Software Package, Statement, Target Endpoint Profile, SACM Task.</t>
  <t>Removed Building Block.</t>
  <t>Major updates to Control Plane, Endpoint Attribute, Expected Endpoint State, Information Model, Management Plane.</t>
  <t>Minor updates to Attribute, Capabilities, SACM Function, SACM Component, Collection Task.</t>
  <t>Moved Asset Characterization to The Attic.</t>
</list></t>

<t>Changes from version 09 to version 10:</t>

<t><list style="symbols">
  <t>Added Configuration Drift, Data in Motion, Data at Rest, Endpoint Management Capability, Hardware Component, Hardware Inventory, Hardware Type, SACM Interface, Target Endpoint Characterization Record, Target Endpoint Characterization Task, Target Endpoint Classification Task, Target Endpoint Discovery Task, Vulnerability Description Information, Vulnerability Detection Data, Vulnerability Management Capability, Vulnerability Assessment</t>
  <t>Added references to i2nsf definitions in Capability, SACM Component, SACM Interface, SACM Role.</t>
  <t>Added i2nsf Terminology I-D Reference.</t>
  <t>Major Updates to Endpoint, SACM Task, Target Endpoint Identifier.</t>
  <t>Minor Updates to Guidance, SACM Component Discovery, Target Endpoint Label, Target Endpoint Profile.</t>
  <t>Relabeled SACM Task</t>
  <t>Removed Target Endpoint Discovery</t>
</list></t>

<t>Changes from version 10 to version 11:</t>

<t><list style="symbols">
  <t>Added Content Element, Content Metadata, Endpoint Label, Information Element, Metadata, SACM Component Label, Workflow.</t>
  <t>Major Updates to Assessment, Capability, Collector, Endpoint Management Capabilities, Guidance, Vulnerability Assessment Capabilities, Vulnerability Detection Data, Vulnerability Assessment Capabilities.</t>
  <t>Minor updates to Collection Result, Control Plane, Data in Motion, Data at Rest, Data Origin, Network Interface, Statement, Target Endpoint Label.</t>
  <t>Relabeled Endpoint Management Capability, Vulnerability Management Capability, Vulnerability Assessment.</t>
</list></t>

<t>Changes from version 11 to version 12:</t>

<t><list style="symbols">
  <t>Added Configuration, Endpoint Characteristic, Event, SACM Content, State, Subject.</t>
  <t>Major Updates to Assertion, Data in Motion, Data Provenance, Data Source, Interaction Model.</t>
  <t>Minor Updates to Attribute, Control Plane, Data Origin, Data Provenance, Expected Endpoint State, Guidance, Target Endpoint Classification Task, Vulnerability Detection Data.</t>
</list></t>

<t>Changes from version 12 to version 13:</t>

<t><list style="symbols">
  <t>Added Virtual Component.</t>
  <t>Major Updates to Capability, Collection Task, Hardware Component, Hardware Type, Security Automation, Subject, Target Endpoint, Target Endpoint Profile.</t>
  <t>Minor Updates to Assertion, Data Plane, Endpoint Characteristics.</t>
</list></t>

<t>Changes from version 13 to version 14:</t>

<t><list style="symbols">
  <t>Handled a plethora of issues listed in GitHub.</t>
  <t>Pruned some commonly understood terms.</t>
  <t>Narrowing term labels per their definitions.</t>
  <t>In some cases, excised expositional text.</t>
  <t>Where expositional text was left intact, it has been separated from the actual definition of a term.</t>
</list></t>

<t>Changes from version 14 to version 16:</t>

<t><list style="symbols">
  <t>moved obsolete definitions into the Appendix (attic).</t>
</list></t>

</section>
<section anchor="contributors" title="Contributors">

<figure><artwork><![CDATA[
David Waltermire
National Institute of Standards and Technology
100 Bureau Drive
Gaithersburg, MD  20877
USA

Email: david.waltermire@nist.gov


Adam W. Montville
Center for Internet Security
31 Tech Valley Drive
East Greenbush, NY  12061
USA

Email: adam.w.montville@gmail.com


David Harrington
Effective Software
50 Harding Rd
Portsmouth, NH  03801
USA

Email: ietfdbh@comcast.net

Brian Ford
Lancope
3650 Brookside Parkway, Suite 500
Alpharetta, GA  30022
USA

Email: bford@lancope.com


Merike Kaeo
Double Shot Security
3518 Fremont Avenue North, Suite 363
Seattle, WA  98103
USA

Email: merike@doubleshotsecurity.com
]]></artwork></figure>

</section>


  </middle>

  <back>

    <references title='Normative References'>





<reference  anchor="RFC6933" target='https://www.rfc-editor.org/info/rfc6933'>
<front>
<title>Entity MIB (Version 4)</title>
<author initials='A.' surname='Bierman' fullname='A. Bierman'><organization /></author>
<author initials='D.' surname='Romascanu' fullname='D. Romascanu'><organization /></author>
<author initials='J.' surname='Quittek' fullname='J. Quittek'><organization /></author>
<author initials='M.' surname='Chandramouli' fullname='M. Chandramouli'><organization /></author>
<date year='2013' month='May' />
<abstract><t>This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing multiple logical and physical entities managed by a single Simple Network Management Protocol (SNMP) agent.  This document specifies version 4 of the Entity MIB.  This memo obsoletes version 3 of the Entity MIB module published as RFC 4133.</t></abstract>
</front>
<seriesInfo name='RFC' value='6933'/>
<seriesInfo name='DOI' value='10.17487/RFC6933'/>
</reference>



<reference  anchor="RFC5792" target='https://www.rfc-editor.org/info/rfc5792'>
<front>
<title>PA-TNC: A Posture Attribute (PA) Protocol Compatible with Trusted Network Connect (TNC)</title>
<author initials='P.' surname='Sangster' fullname='P. Sangster'><organization /></author>
<author initials='K.' surname='Narayan' fullname='K. Narayan'><organization /></author>
<date year='2010' month='March' />
<abstract><t>This document specifies PA-TNC, a Posture Attribute protocol identical to the Trusted Computing Group's IF-M 1.0 protocol. The document then evaluates PA-TNC against the requirements defined in the NEA Requirements specification.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='5792'/>
<seriesInfo name='DOI' value='10.17487/RFC5792'/>
</reference>




    </references>

    <references title='Informative References'>





<reference anchor="I-D.ietf-i2nsf-terminology">
<front>
<title>Interface to Network Security Functions (I2NSF) Terminology</title>

<author initials='S' surname='Hares' fullname='Susan Hares'>
    <organization />
</author>

<author initials='J' surname='Strassner' fullname='John Strassner'>
    <organization />
</author>

<author initials='D' surname='Lopez' fullname='Diego Lopez'>
    <organization />
</author>

<author initials='L' surname='Xia' fullname='Liang Xia'>
    <organization />
</author>

<author initials='H' surname='Birkholz' fullname='Henk Birkholz'>
    <organization />
</author>

<date month='July' day='2' year='2018' />

<abstract><t>This document defines a set of terms that are used for the Interface to Network Security Functions (I2NSF) effort.</t></abstract>

</front>

<seriesInfo name='Internet-Draft' value='draft-ietf-i2nsf-terminology-06' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-ietf-i2nsf-terminology-06.txt' />
</reference>



<reference anchor="I-D.ietf-sacm-vuln-scenario">
<front>
<title>SACM Vulnerability Assessment Scenario</title>

<author initials='C' surname='Coffin' fullname='Chris Coffin'>
    <organization />
</author>

<author initials='B' surname='Cheikes' fullname='Brant Cheikes'>
    <organization />
</author>

<author initials='C' surname='Schmidt' fullname='Charles Schmidt'>
    <organization />
</author>

<author initials='D' surname='Haynes' fullname='Daniel Haynes'>
    <organization />
</author>

<author initials='J' surname='Fitzgerald-McKay' fullname='Jessica Fitzgerald-McKay'>
    <organization />
</author>

<author initials='D' surname='Waltermire' fullname='David Waltermire'>
    <organization />
</author>

<date month='September' day='9' year='2016' />

<abstract><t>This document describes an automated enterprise vulnerability assessment scenario aligned with the SACM Use Cases.  The scenario assumes the existence of endpoint management capabilities and begins with an enterprise ingesting vulnerability description information. Endpoints are assessed against the vulnerability description information based on a combination of examining known endpoint characterization information and collected endpoint information.</t></abstract>

</front>

<seriesInfo name='Internet-Draft' value='draft-ietf-sacm-vuln-scenario-02' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-ietf-sacm-vuln-scenario-02.txt' />
<format type='PDF'
        target='http://www.ietf.org/internet-drafts/draft-ietf-sacm-vuln-scenario-02.pdf' />
</reference>



<reference  anchor="RFC3444" target='https://www.rfc-editor.org/info/rfc3444'>
<front>
<title>On the Difference between Information Models and Data Models</title>
<author initials='A.' surname='Pras' fullname='A. Pras'><organization /></author>
<author initials='J.' surname='Schoenwaelder' fullname='J. Schoenwaelder'><organization /></author>
<date year='2003' month='January' />
<abstract><t>There has been ongoing confusion about the differences between Information Models and Data Models for defining managed objects in network management.  This document explains the differences between these terms by analyzing how existing network management model specifications (from the IETF and other bodies such as the International Telecommunication Union (ITU) or the Distributed Management Task Force (DMTF)) fit into the universe of Information Models and Data Models. This memo documents the main results of the 8th workshop of the Network Management Research Group (NMRG) of the Internet Research Task Force (IRTF) hosted by the University of Texas at Austin.  This memo provides information for the Internet community.</t></abstract>
</front>
<seriesInfo name='RFC' value='3444'/>
<seriesInfo name='DOI' value='10.17487/RFC3444'/>
</reference>



<reference  anchor="RFC4949" target='https://www.rfc-editor.org/info/rfc4949'>
<front>
<title>Internet Security Glossary, Version 2</title>
<author initials='R.' surname='Shirey' fullname='R. Shirey'><organization /></author>
<date year='2007' month='August' />
<abstract><t>This Glossary provides definitions, abbreviations, and explanations of terminology for information system security. The 334 pages of entries offer recommendations to improve the comprehensibility of written material that is generated in the Internet Standards Process (RFC 2026). The recommendations follow the principles that such writing should (a) use the same term or definition whenever the same concept is mentioned; (b) use terms in their plainest, dictionary sense; (c) use terms that are already well-established in open publications; and (d) avoid terms that either favor a particular vendor or favor a particular technology or mechanism over other, competing techniques that already exist or could be developed.  This memo provides information for the Internet community.</t></abstract>
</front>
<seriesInfo name='FYI' value='36'/>
<seriesInfo name='RFC' value='4949'/>
<seriesInfo name='DOI' value='10.17487/RFC4949'/>
</reference>



<reference  anchor="RFC5209" target='https://www.rfc-editor.org/info/rfc5209'>
<front>
<title>Network Endpoint Assessment (NEA): Overview and Requirements</title>
<author initials='P.' surname='Sangster' fullname='P. Sangster'><organization /></author>
<author initials='H.' surname='Khosravi' fullname='H. Khosravi'><organization /></author>
<author initials='M.' surname='Mani' fullname='M. Mani'><organization /></author>
<author initials='K.' surname='Narayan' fullname='K. Narayan'><organization /></author>
<author initials='J.' surname='Tardo' fullname='J. Tardo'><organization /></author>
<date year='2008' month='June' />
<abstract><t>This document defines the problem statement, scope, and protocol requirements between the components of the NEA (Network Endpoint Assessment) reference model.  NEA provides owners of networks (e.g., an enterprise offering remote access) a mechanism to evaluate the posture of a system.  This may take place during the request for network access and/or subsequently at any time while connected to the network.  The learned posture information can then be applied to a variety of compliance-oriented decisions.  The posture information is frequently useful for detecting systems that are lacking or have out-of-date security protection mechanisms such as: anti-virus and host-based firewall software.  In order to provide context for the requirements, a reference model and terminology are introduced.  This memo provides information for the Internet community.</t></abstract>
</front>
<seriesInfo name='RFC' value='5209'/>
<seriesInfo name='DOI' value='10.17487/RFC5209'/>
</reference>



<reference  anchor="RFC6192" target='https://www.rfc-editor.org/info/rfc6192'>
<front>
<title>Protecting the Router Control Plane</title>
<author initials='D.' surname='Dugal' fullname='D. Dugal'><organization /></author>
<author initials='C.' surname='Pignataro' fullname='C. Pignataro'><organization /></author>
<author initials='R.' surname='Dunn' fullname='R. Dunn'><organization /></author>
<date year='2011' month='March' />
<abstract><t>This memo provides a method for protecting a router's control plane from undesired or malicious traffic.  In this approach, all legitimate router control plane traffic is identified.  Once legitimate traffic has been identified, a filter is deployed in the router's forwarding plane.  That filter prevents traffic not specifically identified as legitimate from reaching the router's control plane, or rate-limits such traffic to an acceptable level.</t><t>Note that the filters described in this memo are applied only to traffic that is destined for the router, and not to all traffic that is passing through the router.  This document is not an Internet  Standards Track specification; it is published for informational  purposes.</t></abstract>
</front>
<seriesInfo name='RFC' value='6192'/>
<seriesInfo name='DOI' value='10.17487/RFC6192'/>
</reference>



<reference anchor="I-D.ietf-netmod-entity">
<front>
<title>A YANG Data Model for Hardware Management</title>

<author initials='A' surname='Bierman' fullname='Andy Bierman'>
    <organization />
</author>

<author initials='M' surname='Bjorklund' fullname='Martin Bjorklund'>
    <organization />
</author>

<author initials='J' surname='Dong' fullname='Jie Dong'>
    <organization />
</author>

<author initials='D' surname='Romascanu' fullname='Dan Romascanu'>
    <organization />
</author>

<date month='January' day='22' year='2018' />

<abstract><t>This document defines a YANG data model for the management of hardware on a single server.</t></abstract>

</front>

<seriesInfo name='Internet-Draft' value='draft-ietf-netmod-entity-08' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-ietf-netmod-entity-08.txt' />
</reference>


<reference anchor="X.1252" >
  <front>
    <title>ITU-T X.1252 (04/2010)</title>
    <author >
      <organization></organization>
    </author>
    <date year="n.d."/>
  </front>
</reference>


    </references>


<section anchor="the-attic" title="The Attic">

<t>The following terms are stashed for now and will be updated later:</t>

<t><list style="hanging">
  <t hangText='Asset:'>
  Is a system resource, as defined in <xref target="RFC4949"/>, that may be composed of other assets.</t>
  <t>Examples of Assets include: Endpoints, Software, Guidance, or X.509 public key certificates. An asset is not necessarily owned by an organization.</t>
  <t hangText='Asset Management:'>
  The IT process by which assets are provisioned, updated, maintained and deprecated.</t>
  <t hangText='Asset Characterization:'>
  Asset characterization is the process of defining attributes that describe properties of an identified asset.</t>
  <t hangText='Asset Targeting:'>
  Asset targeting is the use of asset identification and categorization information to drive human-directed, automated decision making for data collection and analysis in support of endpoint posture assessment.</t>
  <t hangText='Client:'>
  An architectural component receiving services from another architectural component.</t>
  <t hangText='Endpoint Identification (TBD per list; was “Endpoint Discovery”):'>
  The process by which an endpoint can be identified.</t>
</list></t>

</section>


  </back>

<!-- ##markdown-source:
H4sIAM0rFFwAA919224kR3bgO78iQT+IHFSVyL5o1JwXUeyWRFt9QTeltmEY
i2RVkJXTVZk1eSG7ZAwwv7HA7s/Nl+y5RpyIjGRTY+/DrgFrmpWZEScizv0W
8/n8oK/6jTsrPrjl0Fb9vjgf+mZb9lVTF2W9Ki6auq/qoRm64nVTV33TVvVt
cfTh/OL1cXHl2m1VN5vmdn9QXl+37g4GgifRg1WzrMstTLFqy5t+Xrn+Zt6V
y+28Dy/NT7856HqY73+Um6aGd/t2cAfVrqV/df2Tk5MXJ08OytaVAdSD+1uZ
7mPTfkKwfmybYXfw6f6suKxh9Nr185c46cGy7M+Kqr5pDnbV2UFR9M3yrNi7
Dv7ZNW3fupvO/73fhj8PyqFfN+3ZwRy+ht9+WhTfV+2ndbP5DV7lZf3k6k/2
16YFsH5oy6FeNzeuLT5cXsGvuj2jB25bVpuzYg2jLK5llO+6ql/c+DcXK4eA
AZgOlvF+7QCWvi27zhV/fA5Pls0K4Pjqm2dPXjz/Cv+GzTkrXpbtFvZ01dMb
Q9238OOPsOdlvdf1/POi+HnwK/nnsm1d3/NPtIy3bbncOECCdte0hBQB4j/z
24vN8F1Dry2WzdbA+ez025Pijevv4XCKi6qFNwKsL56fPH8WYP1Q1n1ZXGzK
toTfWncLM50VF+cW9F8+nBuwP9AG1K4N0DfrOvqZVvDTUN67ChByuSZUq+iQ
dQnwyaJbLjr96rs1vZ6s5MnTpyfFhQMwyk3x6vOudV13X+79al48P3367T+6
ljeL4qLczj8C/rreL+ZNWS/38QNazkXVLZviw77r3dYspF6W23t48bslPk/A
f/r8+Yl8+NFA/RWCHZ8B7GHnHgP0+QK5QX9XbehQGebzVbmNfmaIHZJicdO0
nigDBQe6uLj8EJZTwkiL+8VWx/ruFn9Pl3VKp1r8WsIb++JlW905v5hXZdcD
O3Cuvh66dVjz6ZOTb06/Mkt882/pEg/qpkUGeOeQU7z/4eKbF0+fyj+f//HF
k7ODA+Qk5p3L+csFsbXqSd3dWL4GTAd/6u1LxPvuhk0975auLtuqOSvwT8BA
nuTps2fPZL5nL5690KmfnOg/vzlFKMyQsKfbZjWHnabF78v6dr6+hzf+dXH6
5Dm9CzyPGf3h5dUv8yt5UhydPPv6ycnpyfHhwcHBfD6H80BiWPYHB1frqiu2
btsUwMGHLQzeFWZpxdC5FWBD0a+deWPXNqthCU+u98ybj36XZDleMBjbarUC
HDo4+CfEGhqTuM/B26Etbhugw/uqX8PcAKNOXsC/+6aotgDDnSsaeLO8BRSg
Zw0DmltAHnh8+/LV1Q+xcCE8/l0rWhTFOUKBQyAQBoBu3QybFbD+zQ7wsQRc
XjZ15+oOBoBX79cV/AQwXW+A2It791ULC2j3OBKss2s2d25GE8M7O6Bc/GlA
aDr6deWW1crJMCBVaXdg0QvcVZTQ/NpLd1MBsPiZHHrnaLNhgG7ZVteOzx3+
uy77Yl3C3l4DYcFj+JA3q4HdahE1v9Kp8VFX1O6eZoZNuIL9BM6pH/GI90Dd
sHSQca5eOtpzGISGuIcRXVHucG1tVfaOX76G3+q66eGHleIALHwHa72plriB
vfvcI0y8bj10RA49cMTLRfGm6R0vyX3ebcq6hPOClbSFp+6mBjwrh1tEDj5l
2MBV2K4C9BHYLDjdWwLnpm22TA7mHfh72zk4KtiEq+gZ4VKAb7t1K1znZg8P
NpvmvgsPBXs74LPFBvZvxttTdgh701UCKy0dFoq7UNI2w2q74bpzfxmQCHYg
k27bcrfuMtMRWkUAAqKcg5LR4r+B650xqhjyuPoFJ/jP/2Rm8te/FgDQYQkc
GsYlqtuWgIDwNogWZk50ZM3QF+USuPkOVBGc1t0BoiICNDdFBXR4V26qFbx9
uMBZL3nxerTwDh4gYn5RKnhE+2sk+n430Dsls58LmAUwELkDD4Nna55/8LAe
VfVyM6wQnq0DvakEKV5eI6y0K/hnBzxl6RjD8W8g8NuqnhVuAWTeV1sHK9/u
uuNF8XFdbRifdS00p4WYx0aegbMr/8B/v9bpl4TqiPN3rgX8FpSH72aEPO4z
TLcBbEDJekss6V3bNDfEa25o+pc4zgeCO9mxI5wS6dbBUE73w5/dDOgSyQqF
3GZ/rOPZ5YS9sxDjeYNcA6ZFiBJ2ddm0OGRT018B5Fd6+kvA6D6gF4H+lrZY
MLHrcLYIFQn/RDwKAvbEaZolvI5QLgG7cRkwJ5BKP7SEA7DezhGiLMtdeV1t
AONdp4Tm6tWuqRAp8GhnxRo+nF+XyD9uqtbdg8pxDIRF/KVkBLGcijYJ+QkI
0BJ2A/4eyp7xQWEob0tU4wskg01V4vp3zaZa7hcgis/7Hhjv0Dta6yVwGkY4
t5GzgXWusjswY4iAHGD+bbV8mIJ0GmZlh/zJoeWAOiXzdaTjvwwVrAdPHbih
H2GOa3TzXVm1yO3Pw8iEEo7WSYRIh/JhuP4zHEo3I8BgZ4l3b4mXpfwTloPQ
mfXiN4StlwbQ16DhbWC5F3qee9q8cz3nG0Au2HgzYnkHWiUiKnPulGPQ1n1w
8N6ma4pDjyf7Q95zVvf6v/71wT0mdPpMdB24jt+Mv//tf8LO8rB4aIZwiFkN
9ZK3oRLGjlsEz5sb2OQLi7m4IFRqwTIAKVvgEnmu67b5BML5aNcgEBWg7p5X
RK8A0n4mqVfC17T9KAWXgWve0NRExDCLDObhOibuniyquKvKcEbhZwavFVFa
dp8IpwQ/Vmig3BHs1wRQ7W6bvgpynnWMeMjOTxUzFxwc0fAHyyTpNX+I5jRQ
XwQW1BKxAiiA1/ITDNSC9RX4QetgolVXHIFyhRYecsfidgBqRwJmln7vNpv5
p7q5r3EZftvTsbrjGT5vajwPltI9c1k4GKT2BaNvAJmQhZWynQo9wESQmG5z
g3qvSwEiLRKGC3iEaEI6A+pgzcSmwqCyNSvQbyvWbtfNvSiQpNPgS2ja36Cm
QqBe6Yn/CtYMgCL7HBh38UEMHiQeMXmAZ6uyqNpOV7zS7X4NatktixiL7LNk
isnXEO5JaOJXWV0EFXMgFDU6JZxLp/Q8khas2bgWOH+HGhGsBrSsfqu0zeuA
r+8q0IVjkSvU7CfI4RQyNBFgMNt71w2bPggFZZn4DAaA40OU2vLgrEx4/r0s
W7YdLHdnjC1T3AxSxJpEpcpSmAP0zxrnIMMMBvXPlLZjwK/gF2HHPBWiH3IA
mkc+7SKBVK++hnliuvbPCxI3najcMfCKjMjhSdiDIdjvd472+KYlXXi5T+E1
gooWJWyHgC5X83WzVD0PNJJb5VNlMdQdiu0KP4CR2z1+gGOIUj76CslpiVyE
KJRYGwl+RCjhs17ImfMl6D3B4STdcu1WA0gLmQK+AQ47AArBPwElYYsAr0lL
QUMBeOse7Ooadw8P0LlPGwVWzNbNXoYqgfuy4+7agcFXIZ8C/gRDshVu97df
g3UbNthsK6jR62YFMJBtixtfkfcY1VCjLal89jwKuAycQ7oXiTAxuMc7FZ3m
Gcvuzc38PUi1Fl9D3EvG2DRLki/qHEiYvTBWmanLzUO49t5tgcnPz5ewQD6s
h+eC9XsOt6puyPrtg/WYgvHQ/CT/6LRvyiVSjVdp8muS8/3w5vW7r9+8urp4
++YHRIaPry9pJd/Lac/fhtP+b10LYxF5Bhi/gNfeIJNt3YaGhLPPfUeKwqP2
Ydc6MdZVliZTBcaEjn1iSbvKsfHZNTf9PSM1akd4oC2RZcoxLadN5TryBYOd
KZ9Rse5ZaVCAhLmB9rZsG7BetsDsK9BdwthKn/x8xLdZSU+OS5wvHQompDeU
T53aczEY8M12qKslu1uAM5UsBsGe+c2Rn6lv4IvAVd6dz6/eXBT/Lr7R/yDV
v9g4dL/iHuFcrGnZ5YVJ1yWRe19+8hjbNhvHn3i9DN0C5ghgf/kRbi+t1VAA
K2+7El0ysbQm4RtUO9kklpKJc8CcWUsityOsqW+q24H1V8Gcuqnndw2gLpr7
VoczNqQRarQs/0BlLEJfrxj5ARGGGvDULXuVMOSPRjfZddP08+UeQy04ewQP
WXzEhWm3MrqgztbBvjNXvQGgQZXl/4H5q6WSoDiQ8H/NFCiSEev5A29GeaIJ
GiSotiugnGUPui0eGDCMTzDDXbVEVYu03qBfrct2lXwvagETBkhLUNkAMKTx
WB/ITA0YCJYgDuy5QLyKkZjflvVAVhFaQeLRXdIPOOE26JZH6CZ0xxG2IZzd
sEMZY19VSjECGHmu8lqk/3VZ37o8eM1yCTrLaiBpeQ06etEO9RwdTOx7AtNi
Tv4mcSp5zacoLtVO3MJYO/TkV0uyaLy2gKraxNwyIwDpT6+8weiN6iIbp3ta
FgEbH3cwj5O2hNmv2GTr2KZAlxSgCRgLDXAiD0BdXL4DzWyF0Tjhe6/PL/wv
ZMO8/OniXUESp42XOiOO1BIT2s93ZS+eHPRE9ehpQ2raNLdzxPXw5ozMZLJi
0ckF/035AsahblhDJ29v1VkFPch0QHo4GwdWA6yNuJYeCsKKZ5uh8RWODeYb
fNSRE4twI0c/uB954rja7xi72SAO+jB9Ak9yeEHzWvlojUVgKdVtTRRXI8qs
q9s14UzpXSK5sTJg82Z2w9apZCYm/b7ZCPtiHZIOJ/HuYuCHFUZ+8oPXJsml
QnYPvQUn6ZAvWoFC6ooxhS8SiEhEvGJD6kyOJTGuYKa+6gd18pX7TVOKl/jI
SppjVEPqDvSkVjha8JarU6xw26oX9q8ysEuE4KJ4RQp9YubpGMFjUybBEfMO
E01MuPqOd4HLy2Yj1NnLftjgJk+G7xIQ5wqiAW1yNnYmCJzIEvVwy3qfc08G
gaHRoeCNw6dhzxeeu/gxiZOy6554HwJCMcSaBKdfD28B6CfFOxQEjKIwY7tc
g/m37AfMDwhaMoEk5+dZ8lJGiKwdIMfUB8NGrNIqh65KEvEULBo5G1s4ATg/
0Q/JIYxh4r/+dTHy7qCXy2/nAOPUvQjLWcH5LtVv8udRcD4dew9d5J2j1yLH
HvER0ITUS8VnqesmEQoDgDRiPwur82jUqmDg/af32FCWgGdOqTmqFm4Rc5hj
JfGVdw5awYzjjveElN1Yi+xHUFPoEx17IEVZfEYuxYoVvLxLDSdI3WoBoTae
4S39D6zRJQwQf+uQ3bKeNvK8iuKmlBxgD/hGm8Fm+KqA1SLoZZ86hjpgz6IL
uM9uSU6DGiPDHPn2wy0edAZ4zsdLAoH+PTmQZxin+rxnB91773deFC/dzjEj
asixSUPNhFPIvhCVowNbtVRDSz5Cbc5yhFYAM7EtEq4r9s5quCCNK2EGRhxX
AiTs98FLi0eCQTqkjo26VTtK0OGYJ6LFUG9QJ4ER9iaArsTG3yBieUAxCEQw
XmJgIwRg8SdFhGvKKSDWhuqn4Lt33fyJN4mi662gC6yChoDVXeF3VX+IJ+x/
/GEDsrvnsKv+tm3EDvKil5a9xXAL0Ynw1rDJQ8ceQS94QL9oVpQLYbSPVTw+
5R20amkebcsWUHCDgpsUbsR1v1Q/IBtIU3YiZyLYUYc6Gld8mqxxjATslc8X
4eHEuofXHppwYjiPK1b8X8NJESK0FmEXeOiYU9DSocX7xFpbztPBlnM3CYAk
imQBXxHZeVKJVYK3Hy6LTbnHGBIJF3iJ/nxy5hdgqA2mr9l4pTO7bkEPWqI7
gHnezH/+LPs5ITe+SJRdFlegwMuQyNsXk3G2f2TZuO9juUuIf96js70fUx2b
z4FCSCvt+mn6IFx1gTrYyJdhJpezsmNbf9uI47M5K0t8IKiDzEFFOHkIreBa
eHYjUfl/kBmiP4dTFjA8QBbNaoZECMx7j/8EbgNckhwuAPhQGx6I5vdySQwZ
9CgQU7VrPR/kPICzKM50EataFDLm8CY77mhIH8AwCR3WZPYHyTNIBLYbbzRq
IGwd7nP+6N8LQnHEBvBxkmwgxrT3P0lo2uSfHBNOU2oNmDTB4xv0AYnasTiI
0zrAArSrFexxnNQqHqewO0Cp14DFOYWbgRWPlWinXo3HtCOd8VhxKyjNGLua
1puDb69hhY9ym24yBp0F67PYz0qniIWoc3PawsqrQ+i1DeqguJ3/QW2bc2jC
292+bur9lkxz+H+wbmkZpHSMNfMHmFmiBlf/pf0iHkQYksNpdYca2ZWgTJeE
La05q3FTCWWyMl8CiOUmek9y38yS0hCz5uex9xFdc5HLmF7lOB3mRqgm4D3A
aumRRa16x1hh6GSdVr75XetsSiPD5jk5ckhBY28ZqgG4rpCbI+5IfoAKZKZX
8ngitfHk7k6yNCmLBygYeSjmAqmwD8FXQPANOmc0k2o3UARAtMqZDeuzlCNH
qUQYVhqBjLJk5g9LHGP2Vp1hC5a4U0dZDlvyToWQS0SZocHzgS5LSf5CfkeE
UZKfE7O9y62ubcYZvz5jlIO2oF4sgRvOeAzWPdPV9GSXULanMPhUPrIqu8Rs
pOUnTiakU4MNNMwXD+UOM29DjJYmZS0sSzgY22ANdkmJ5vhV1Y5cgPQuFruA
8o62IixXOSfn7xnW6fkzSQcmwZKCLdWSAsAShxjH00cR9GCOiNCxyg1P/DiZ
OGckNFlGYYW/OXycEXmK6ctNWW19BCTafEm6tN5Ts6zAR0YiToAfiTiLy48W
d5Qhlfi4xT2FSqVsAiWzjqGEDdUg6ZeSF9G/hfvL8oVDJlE0JNGvxdhDPekB
mkfma2cyScgS/Ud2cvgBQxUSppGwE6oyaNuL812TsSJkA2H8SSwE9b5fs6j4
c8O+CDxQDcOmWBI78htJWzJfUPyy8u667gzm2vXNriPF8hP/i5388I+l22yK
3RqzzknbxA2124jeL8L5aF7ev6sGWGpL2jNm4qiml9+5WYQ5JKL3MPG+I0EA
M99VLcnB/OxhPwSCImSkz/xDQMUWjKd2WFLSqJ4NK18dHAX60Wakj9DqNTsV
I3DMFm6qPknrnvGJigelQ8PIU14IYovDKqqwIMbwTpcY3uXx7su9ZihWvQ0Q
mqzF3xes+FV2MJ7JD4co1GIC+0RkAsfl53X2uXXQWv0yynDNhymMFWLUMhdS
ICp2bd6D7gVMhxMA0Yi7Bb7GvjG/qDOfQQG7vuaEMHGzabLwOEhcUh4b+jRG
aYWsZfghQ5xW1CKiOtCXObuGJIhHY5+dHNLkjvyrYQpOFqF8aPWuBY4SEt37
MY34EDU9N4yxyOU8g7mKxV5TcbMgPohjgpDaa57StQTJx8OTT1F2wYRt7HPD
bq+HerUhVg37rgGJI8m3GufRedUzELC4NnTA1qEcwpxB9deJrPbJHue/vju2
G3MRKwreBiaBNxvH6G3WWNBE8+RxJEzqOE+Y4yBtlIM8M9n9Yd99zpiYPN2+
m+N2A3vSiCqz5ncvf8FQV9cRoLWRZpJQTfSFP8wp6W1WHF2JAjG1OZIGHW+x
lYUSxSN1PjMIBz5CuiL5ADG/KB+8ldcJYQY0f3IqikQuBSayamDbJpG6i85+
g+5+TWbwICkn+c1rnmnSCeFrnKX0uakxvb/w4qSLKWQZzRUcWtlU57SaxpA5
cFQ845kJGEkSzVhDHOfZoBmO+EHQOArIkZadnDPPWYEmBtx7GGdXRyUDiAQp
eA9s85eOP345HL7ZhK+6XIh/5dif7DSZ2p8j67y3sMX17z9Dv4yfUX2VQNJQ
V38ZnGi0Y/VNHkduMD+Oz/kSs5g0llj5TVTm5ItFnHk/VrGHLnJnmiqtTGyf
lhUR7ETC9xmvwqZjG19PFKjzUhFM700jChC/bA6A1Poes2LDmXhewtErs7Vq
VeCRcMnPKPUZUMmXJsbowoVZVLkRWWhkh0sB0cpXDZVSLDTX8qE+/S4GwiSO
I04zseE58hykBCDTpmI8P5mKJq8VWIvm4NXnHRsiYxnLpWF+uhGsJLpSvhEW
oGKdVR0qFGzD4qUuh0MxToHIDEOzsEiwUbLyAZaWMBHlFQ9EktE0SarxNG9N
1j0DJaKXkhtxEGEuJcZECMIF+pD8OnhryMkRpBibqWF7yRpVbSSWL11Go0hR
iqu04Ah/lLXTSb0ul+h2mIuvhUQ5+Zwk/8n72ryjiZizz2n1eRWojg9cuszv
fc2OO5N0gEl26BBn0yjsKuYScGEqEViQDzPFSwrN/RjOTDxk7HkM2eqZAlCk
Vi6OVZtH/VIiPMeHO+UrCziD8XTettYB8ZOXNRQ1TacW3josSul9gICCN4s0
O4v3LbJTQj5nM3JhiWUJutI8zutC00EDT9jJYyWFgSZwD5aKD9vfWrR4aWjF
40s4AY79mBKeWB+F1TFGJ4YA5Ux23pzBwKCWBgd/ttemSzHNUBByUYG4rjGu
oiB0FG8Rkhol+bDmGHjVOyVtSmaRDPFmx5X5XOopGtDW23yXIQNlaieQCqVo
fgS9sjNNPI1Xo3GUCjcNg5XkMVxXjn0VsDNw0rmVlaGkJqm4UeXp8t38XP0r
GcKIE5XKOJ1H7WK2/UFOVPSNS6A4Qzd5lHWbwYVx/SNCOOxW6rWd4L/K4joC
UKqumB00LVEpGdlY4mwpM02NyNO4USt+UhvosgZFDDNSgrHlppIWtYSJa7mi
rAdfNCi8mbMQOzuK2R/YYQ+APxzRHNhogMV1a+Ix3s8UdjJETwSSJMh5FdcT
pdJX3Yscsw1pqCR7VivJBQJqaEhLyLlFooPgeqNd6iyimjLr/Qseo0hkZcaf
GcM9KDDkAAYqackP47ckLDILaWYzckeLWTbq5SBLXryvXYi3w/aMM9mZk7Kb
4If3vzCQsLVgN6gPS724iJjAt4Z6hYrR9YDykiODLCI2mP00hs1WjQhiSJSo
10Saoh621w7o4+1yWXbkFka5kjX0yWqOEoV2zT1gAMhxan4Cqr2jZK+MLS0o
6rHcE/vYQeLRAYWS+kf//rf/1UjiK32EBcxd//e//W9xA+Rq0Vs2mK6HasN5
QFhh4EkxysWVApEwCsXzpmU7mZUTCaYaRCAlC+bdqEZli2XI/YOdOjRSFTY1
UuKOgBWBtMF2Mfi0zhbTHy9CBXvqU0DstO6pUis/kTN/NoSVW08GuJB9y4m7
2c/qBzaV0j+8bYl7sAgC15bBtDbnNtGeUw9O2eUA6R6GJMFU6g3g83WlxVEG
YzX8ivE5yW6hQCulCaAMX1e7zqctcToHx8ZtFNn6D+FXBMM4StFALAqExTcJ
YQ9v12w5/X9T7hShQgB6xmEIbA6FYQhD9l2KsnwWpWYIai0KK8C4yaGhTe0G
6mqm7WSi5KV7ak+kimfHwSG0l4WB7oaWJI0I+wmcqCQDoRs0y422SuqxdS/T
cHtx5C10za8YR/OP05ouyqYHTtquKKNI6CaLPjdUXKzlblRWZkGJvP3UuIy1
OINKVyO3tykZ/4tYJZzHpzEwn6WCog5trFsUE3GG37HxqqaGZSgrLq5hN9Dw
uJ1R0m23bjYrCSIDabWSBCBiS2AXRMoZq6o9sCZvsDkUMEVqIdUIiXtvFvIG
TcoxFTnFItae741m2ocU0Fw9wgh89hApTqMRy8eDe5LWdYY6Q1Ygh5q1x5Ge
Sao2KfvjuhDu8DIqMTcuqEdVAwSrRioBogSdrneSQWtN2AQTtZSc2FN4L7f3
UT7TLJ81eDNsbrClFmoMSspqg4WacHEB+IrerJFMk5ddP8sNIBlqvuvGVGJ6
qfrdOKkd+RAmdOnLwpw3+1hRssgi25KCi+hDudhiILNbgH7R4nkqXMpj9CXt
xZQtEVv9Jp2vLC5+vuR2H+ob8i6QpMYw3RTPBbWSNpvcCeetnTbF0BMKoKj8
PFiiYgXSqNplrJx6C0sGpQ7tinz92iZslLpC/aO6YbtFtQFsV6q+8ChzwQg/
Esi09dqO8MnpU1AWsFGAruTSh87IcPTgcaaBbmTi2bbuclkHCkjTbuBG2QGN
sxAfCGUMgvUIC4NptQA8DdLja7eb5pqzBEnNQTYXamclnbXfa78zBDNIpw1Y
RRuJfg5t8BpkJxI1iju8SGwAOO7OxYaW1x8kAl/yS1F6iA47o64t3OkkX3rM
S4rced7C99r7K5wTG3mSNBZVxRRfzuSMnhS//nz+xsRAp199mr7lLcHLd3ff
hKMM7/cDmFCYrHPLjg2QafwvngSzO+6e+eyKQCAerZRjvzKmaT67hojUYtZo
LNCIxr95HVD37Whs3x9zRvQtP1eT6KeRjQYnh5VOpcG1DxrTDYNloWBD/5U1
9Fm8U6JNaNpAGwsbvMX87J16ejZ7biFEBHIvwgtDd9h2deUPGkkZCPijljnR
77OoMIA3owbbTlLMJMLLrs6kvDekRODICXMTh3xmrRU+wfRxiuZIFQEBwSUO
xPCB99bNFkVT8GRbnd270+CnxG0I2zOAXXNd3XK/lMXvoZQpskD5/Ppi/vP5
j6ixDruA4+9wznnfzN+xmjKB8qgFTVVl+k5Slw/ZSzNfn5IYhReav/t63BPR
N0+Y+mquH8XNBBe5rofzMAHj/bWkyIW8i06RTj959ThbEChlmzWCo4TfB0wY
pWMRwSzTJHTQ2j/9IkSsYBLcDHuoTTgV4nCE9JS0ZQL0T1Odw7z7U1WvTBc9
4eWJKFyEFKWMcYjRKPXaT7W75BTM0M1NZvNtH+1qRXNzJga0tQca2ft2dF0v
p3kiJr/jaOOXMiXHvSkk1jB0kTsPf1VOKa5j75IY5V8jb2xvy1oC2V91NhdL
uzOecT5i1FbWp8s5Eb+qvlPJueZ+jH3ilPvGIT9zSCGvSVJytQxklI8Tp2Hk
0k8kV1C24Gu/L5X6uNMUIuBB6FvAc9oDrxOPqy879aL4OCRmGvQqo6wqKzSz
UWQ5bJN+9cUM2bA0aVAcekBlIk+ADUcy8zErktIIMk2ZwdY1xQicJLDKPj9f
+MSiVZoa+dhTkvyQGXSLZZa+vzKBgdmrJnIiBjgGwbiWFCPfzP3ENOHfGR8/
ZpI1+S9C0ngNXs1PWtHahlO5CB4jUhZXZgY8xbTgaT4eZWTlcqSlRfQa7EhX
HPpunckpHVJ7CSpTRVy8xk7fJHy49/cIioj8I4MJcE/KArULlFYJhhwU6kX0
YMF1HDvD94MdFVn4agREZD5Rq4fQharo4F/X9pyV9k6Qimh1ezMbi6aVkp4Z
FxzaasgIEu63FFK6UcJwngU6f+yblc2f5HoQE2Yb1Vpz8sOo96h3nXoh4a1F
Nbm5yC11NqA3nInQ7AcyHd+xc23NZxRDDffzqokZ+cMxn1NKaqaTAMV+sN22
eXlmU2M1rc0+dv1ycXxwQCfKxe7FqMg///ALxzrlNolruLhnIhkxlBNfSQU8
uos2N9P9CZI+cpNOpXNtAWv2PHXg2x4SAQhqNwBoBRr0TtILHXqMUkiCo0xe
IUcuD7KQjY3Do6EVJltKaXNk36h3ZgRrSEkf9fV8uGeyepXps3AMvgIu035t
1EDPt7ILZW0zShPgxgfRts9s2Zyc8MhhNO7AlPRFAyjYxS46n1+GOsztERxJ
E0jvP51xJTd1bqDcI1bZkKUcT6yPkbbUZnClNHnWpttTPkDJndHWDvHSH3CU
5aCghAHZ0ljtQ4beRcqJZ/em90c233E1OH0jwYBci+YRTIchi+EwBkraa+vf
h7qHhyOMmsWwoUGVqhzZ4mQDXAcr5cKJxNWYEw4cByKr/+FGfSPyLF5qjGCU
TqvRA6+82exMG11/ZCcVUcrRvVt9wrWxRyvE38gRm+08OoGM49XY/Npxmgdn
tupWa0DF18eN+IJwGW2PtPW2MiluUormbV5jMwXA6MuQZildpx7aPYu6Unmb
649ylrZHlJZN4duoMpZ+eknDndlMYg1U+0ylEZ/QrJn0MI+uGq6WuKs67BtQ
htK2pHgNx7n6/uUM7YuuwuQYdfVQS11Nk7NlOiqftUmYHKmGVDA/gbwV2Yyl
WOPD1u4Ue5J+9EGCShdefBY3FjIC2Hcp4z3PEbG+wm7N0Sy1dz/4vlSJz5n5
NpKZj57EQJhuZ8WvQCShWN8APoaH2vAse84c8Lqzlpl2D3VWSTq0hRYW3LaT
o724rKS1Ujal8x/oHx/1d4u3VJ3C1jn3BXXC4wKOFLT/EEKlszXfeSEcXN60
X4fCj0wqAYkodrtgfyASMtwO7a4hTsxJ6NzRHc4V/+SF8lezQ9a7pKpxPDGm
L0n7J45EmKUXhyu3bIbdRgg/yR2ILVUNl1L+kVaa8XHb7WQlN3RKxdZnaepE
KcEOWbifVtIO6BYceebrKX24wCexxkRHFrpxdkvAUwo/p5S9BFGj1rFjKrRp
zCJTZqGhHNsvb8Nay2Qck4LZupB3FushJj0jaVawGIHlkyd+T64D/ULduSbs
lvRZ3mzxa0k0uAlZO4sLK9Bozxovit1GF5Jwlnbhkr6lbMtWO+1sFiSXFQS6
XmywFkwJVGy+TPa+PsqPbPhSB4xPNRvSk0gbKdtJ80HFBSvrXgC/J4002LbY
xQDoAYxtyhZ0NUBIbT1/qFo0pqrQ3yDguk8VkAxwblcbvN5EUAF4yszwHwtN
kAHh0G6JJhkn3UctOTFAu/rzQDacdSaSsT0rOCcDXcMUmGQ079yx74ZKnn2B
YIbgcmsxq7i/V51dMlciiDQpnOxTuWANx6KyjZaXEvM4Hi5ZifdNnO92GyGh
zhd+8T/824/gKGxn5OrqU3WNrAJTyaYnlrbMp9QuQ/mp0qIKHHvZomZ9AaIz
L8ZDO62ZpdoNxsu5gIhXMCorS6Zl0KXozUOfyxtLTMCHTNnwkVlfbHgJWftI
he065L2eqqn7S8oSKsZRxjf9BW07XDHFLMhHCkrYp74bp3rAfjfDLd9JN/D6
LZ1ZHX3L9wfi7peb/W9OS81wQheFRtNG+nqpnAo4msX1Ur+zRS3JuLgw3Ft1
Si9SbYkNTYQHZW46TLIGQk+stA2+hlTlCjPqbYIF6x0g3aH8dZj0FuN6Kr7h
EeUK1z8Q5oTmLqHXTXR53JHxzIUeLMeqU2RKmRGy0gMmjnYLDXqJfZj9Xbn8
BPJdZCElHaFDQx/v+LF3nhDduxUe43E8UJrcPxoi8vXn8vjHHu24q6vmjkSJ
4DnIpitDgc854MXFJ7dPwL9E6Hz7I+TgNctY/lmydUYQji0cSsUjxW0O5NDK
AcyIvW+a21u3mgN20CNMLG5ql0xiF6JgsB+FtYTMIPrIDuRlYGY87VavsZ8Y
0pIH5gS1WA+t6pBxoJN1X5qNN9rXTp4X4W4B5viTlwpMt9aJLxMY3SLwc4Nx
W191mNzBF2XU3aRumCJRxux1XJEHE382JGt0QvFZzLhhShm57wGukISN028I
Vh/BnOwb8pJVjcSbz+hvm83YBmNWPVFXUfqaBmyNG1LV1JAmiz3nj5PIficd
qaWs1VfgKj7YbZb0pWRrBXrr2onb26cVCHFP5P8H2+rHwvs87hbGenXTf903
uzln1Wk7ptw9gbn6gNGY6rHjmgqf4WGSTKQcvzP9071n7OEkCiZs/s5fSwho
1Ef3HuZSRCQ7QXpgl1Fr4X0g8uwlWD9Xn2xkfaaQ+0pRKlNRHdPGRMaNwxgf
u6S3++UrD0K46qUzfdtlor8MJXWt248ETqWo/Ztrm3mD3KKG/86HGvYRlYxj
UTnV1wdTjmahW4FBclHhJFdWllJGiTlqVRd5WzFTWR2h9qpJqlvmQS2d/bvo
A/8xM7Nmcz1QpXAVbdRh9qSWJTWKSGLA1Py8BJXvtvCFUK23gEKsn9H1EDtz
4fh0eLwVWZyg/fPrpPQuvDWeSXgFWIl5ckvkruSqcV+4bTcsnaNHI+ydqrTw
vXEeibmF4BZn5FO5o0w9n8dG+egE4IX8hXZRCkTUzdKwJi5ZzM1lsWA+D6Cb
OtabfKGA3r0ku6X6PnrexAVDd3hYNBSEBjh60iPCNS5Swc42sdaYGH8AtqvS
7AjkoAObq56FGnhBCf8kPOU6ugbA1MomvprYsKC+EKmTJfXjAwx86O9dF3oY
PtBWmC8RttdXJ5lzjER/KuQGXxK+iVSMX+H5Mbq0pE4eKqaNOsKljmMfGWz3
fbXq138SfoLkQ0xCEBnQcydXR5M7QxUTasO25X+FbBh0R0hqDstkgVBa8AtF
rBviEDKF8YySm1dnRB9Dkpma6w7pY1E1ueaDeYSXFmFOpCaRzbi295aVgFm4
f4YpcTQgGk5ROzF0tNzW6rsv62LUNGyK1s+nDLMgT2ywSjrpVzbGnDoD1M7J
Bm6G6w0XzY17D+G7FCehXLs6xG98HPx4oY1cRiB31bai6pGGkrRDyz9atxwW
JjaHpixHV29fHSd+RqmVuACrG203sftDx1PC8UA1ixEexAUgdVzyQXFFTC0O
SWAwvjQKlHKQ9IWoGKST0kUq1AhO/f+rBRoPVmjUD5ZmRNVBoVDCVEjUVrP9
cmXE/4+FESkCpd3QTLFjuHpYDBdtZoYtMWqfVvnAfbKhnL4ftch6BCwgSLB/
Tnyzd84ontIDCI57vA+1pma8/kpWy2U0qJDz0OakPIfvgknn6f3hDnN6E2T6
TJpIZ5o+ZkqWo+vfLq3DjWqMyO1I/i8ZVU+MmiiMU1vTlQm/9WELS76Tze5C
WN/7oR7TJlfuwYivfWWwF8VbJK37qpOLvDMjRl2BwyB+5ciQQIuAc41TAlPH
pT39eaps4Q9pM45R432MaWx4FjB8Ng+s2F9xKLcFELtfyYnb5T+IJlrpEvXt
iPrIkNO7sLea5jpmyfXgbMGMrkrI0450+mUNKX41ugwi881IYXxgleYOsDTd
UNeTeCKkx1gb0rPjQFXoEp/qJK993yxq184XXd+AJt1bP6c485L8dznQGAGn
FuUDWnhgcgGZmNvGd8DRLdtYFjFjy8HwfE/sx0yeFH63bm5SlXyTytEFvv56
Qm6ayJkuvk/ahNCfhkJtjUwHxgiDsa+PvfXX9gOTxjTaNsy3JHuEOAnN+ZAX
3DZ0GJKhFkqYN74FzoPEQ3wgDl0p+eJRXb3KdA7FudidqH7BlMFbwhnFWKyT
Sy9SSK6yzW982qKRMjmGHsubcwLc9PLspbHU6MZ3k8ez9JeJkB2ZXfUkq5va
K8IJyh43G9alW8Zkme5TIu3TPaMmPmCE9dLmaOva21BVMj5QDH3SFQYqClvR
4HNoce2wcVe4qGWRQ8xHNCD1nlpqlUVdSL2pgmloNWe/obeLDl7IU7W+6fa1
fuNf+Y98qhiWSIWuZ3yjVqZ3ImeY5Igz6ujHLvu0u7UxTCuvr2fp16eTxjuU
Um6Id+4wgZApeKgxgypuiMHZq1qcMFVdFYko2KQARZp1YitHpyVM4oEiz+Xc
f0rXyqd5apoxrkiZkCPn4IXyxKo1J8j9qNRQt7eMY+cDvloqkakNOV1s53kT
4wlHrYkRDVHhFvZRgyfGnLM56LZF5PQEvueBaQfl/ZjxwjXi6Rvgh574v74u
ADClaPjLX3xoO2qcn5+HuwMk7QiLiUA5XNElQxIXygaDsjh6qQ7F1lDwg8xU
WwilN8UTQxWrgkT5Y9Vo5aqpNJqwpiTo/uXry/O6uY+dlNmO4X47Zqb17TRt
+Dbp6vBILoXEecOdV3n9P70mxqslWritntSyOLwG5Jq7G0D//hD4Pnrdq26r
8Q2vBz1y6yf1n3SZSbK4b/Uw9qCm+GWS0EdtlcfBtkktNze09MTUdGiOg9km
uyalKk3ilqsl4uySUN4aHFBf3BvTrdAib9w8uU9aBkxsM9YrdOjAluYAEWan
jbyJ8XqJm+vT7BtSmkj5aNSctoOmDd980Irkzmkpmsps2pZP9sQcNwI9K+AZ
8Uvkg1uQBtE1KDDjDTol311onEdq8pFTGD/8bHrO0HvJ+TY89HscKkl9mHGj
uz7DEOUq0/AEkc6rEMeaz+WF/iVzGtQ5fTfVXAV2mWp5o5KftNMOJxypU3mu
q9LuqyYP1qq8QP+3tz73nPOvTRJ3a6ZR5zTQO/AX0d9yNXlyakPdYeF5hUvc
Dd06c0uylCSVwYSx9y8fi5MdpWWXetU1iQ2QFpUbfRFIFjPYTC52UIgqCRlT
SwKOJUqGH9/JIUXQH9lZRj3P3C5oW4mQ83UFepqYdTi+U8xGePIlsxxoi00Y
XrL3zEV9+XRAyauQsMDqeKIc5ipqgMTiOUnMRIhY5E9prZlnqUjOvRKxqYMz
0+WXIjTeDP73q+9f/kfSMvOD3OOsz6bqs8aPzqOrwacGOI+KPSdeem87x9E7
GEW4Ck6PL4UFibsbdiUFiFLjgDklJP6oMrL9JMFInxjue64Tg0H8PaL/Ukc6
qhWxOWHMfDbljhwj8N4x0kGQOqOp0COGuZefXRxtZ+gONWSkq9U+TT5/3Oc3
c4efUOiUjaZ75XicSBE1HcHCCuNWum/7/Hjm7qZtaOcRPqxqPc0kHQYTDoGQ
TCPzoe+qUOXF5WCSL7Xny6XwJlyN6qo9Fpvv2NvKjiKsO+8aMeuDY753m41n
2HQxZ+jUgy2t9DapKGJqdSifAOPMxVLam0kDyaZKFhNZDaYee0ZBHZSkzZ/Y
VMyItL+T9Iz/Gg0Un7nYZDoTgpSn9D3qmzOb1Bi4qRK7VPqA5uqgvAdJrAI2
B9tYFxm3eCNvsMIft0jGYV/V/c+8U68wf8sT8Tcvnj6VRNpfh00dGn+ee6P/
jEOK57V1BETRZXtHhxc2SHlrx67qNBLEjaBkPtRPlsgBJN+BE+6My9amG+DD
uwhQG/WyVWzpgl6a9wwHPkubGMcJXSwhYZOdz2q92ZTkWML/Jfobd9SYqZs4
JBroPazUstW0W9C77soV2rWULYJVe3j60UUpIemSUtilnY64agizf33MthTd
mkDQAm5XU8p7kvEkJSijnRa9MrO3qnG+1BZX5/4mMeOf8v4o4KeEvmKymIaE
jzrcQq8UkFb+pFSqJeWNRFLiJ5YQTDt7q7Ju+Fdd8t3kNTX20iDsI5V8hxqd
9BYapYrHWzh1ZY4nvonLciLqwxuNgx/FMwsLUyWtHjL34giIqqRiQ4COL7a9
deyoedzhUPPwiW3nCmoqEeDK7/Gwgct0o10yHGiZXiwUMyi7QZrXm2zUf51V
PZYTfWzaT5hFKJRxL3+y0Nk2K+rpkjTjNXeL2I4Lm4bu0zSthrFGRCNiZBhw
zpSvQPEP/ZJiQehbCRq4ap8wKYa8bqu+AkP8U1Fcnr85R82D8qjZmgK9EUXa
1m2bkHxbN9osBHcNv+Lvff3K9Biak8WtkqqaLwC5MczP39yC2ok07ZaOayQU
9T2uJmuc1JWQ3LYcFOA5X6LOs3ErprKOfrzgltAgPg8OLiTpk1mVtIQ6OSFc
0L9O4ZT/gGk+mFhOxbHe549L6Azzo2F+uShWbXnTF/OT55gS08vVztLnUgL2
W8nqB7WR3G9LRzyzka5S8QwlcSbFafjPXvn+NVaM7MR1bq8ORfus0WI5VDrp
NZ3POIwpm0ysbkDairtFTuzMabQzT8zORHQ9K6aY4azA0ukBJejrpDaK2Ygv
e0FxPA3IkwiQpwTIe7wsA0D5ILzpyeIUtuFi40pc3LDjHDysAEGKqqu++xNX
68suU8L5E0QhcR0Aq7f6be3uzWbRN2TsM2Y0W1/cArqsu6MEURp3J62mcctJ
36XDRaf00HVBDbp8dfVD8e0LIBPXa21KfvFPo8U/o8VfvX35dvKDZ9EHz7/8
wfPog2/og1/w3hinPXcTjvgHND+5heThu9Z5u+AKd+CQLabDN+6ef6DtfBly
cA8X9vwO35uLgMD+q28HwJ74naEe+MogdTkDvFjjt8RuZkR+fxI3BG8wXaRS
Ui/gmsG+M07vLhq7wjRc9HJRsyrMyqbNUbQ6pZSUpSnij/vAjfOIwJDBW6Co
zELphXyk2EQeox/I/uhiTm72jOwJ2CKVZnB/pIlj+iY6pj8acqR6cXSSY5Vh
59W80SlKrv4fhCuiBY5Z0DTN4VXCoUN5ohcghwjBIT1wtmpRO41KT/LXXF+J
6ztCSXRcmLEPIwDK6+vW3QkE5BQUHKKJyC2ZfspLBp6GYYvPJAnPe7qvFju9
l91aCPGGPIMU/qJLkOTc+fPY/zKLPS0z7tJxgfxqxbo+sTn6FVsA3Lbh77eU
RiJ/YNM7V5fUOjp206R/B+fQbNqlRQC/Lv+s9zixzvq93svyPd7LMvMtFGah
qn00Jo9U1clI0nXK66wATHLL1axIblucacdFoSLy2MCOvpdCfAODX5AAA08T
sGa56DO8Nor3LQPreU1ki0ipA1Ml4QVeomMHjD+lyRVVaJyQ05sG9yjUhhwz
phUq69KIqnaq9erFNN3+MaLbbw3dnmu5dLTtfJ2k/wkLlV9pwnfYuMvRvQyz
tJPzbNzEeWbdR7NQwz1GwksTWsxGyWbBkZXHU1sb5TEtxa4LXwofml74f3Oj
nFnuqHBP0hsyP/CdzVFfkVnxzpfdU3ONWfHeNBT8vRRzzhdvpyQ45gQfqCIj
wxbCCaaXXHjKmo2bmv73sZNAsT+YjkXRnk2j8rcRKr/IaQpexjCKh35Hs2m/
/GzKHz/zFwAKwtt7YmaZJu3mN62kNj9JkfmDeP9OL1j2QbFIXYhPPo/4X8Te
B5B3dI/DGE8mMDMMbl0QI3JI8SihyBGLHaU1JIx0AlNeWEw5PYmVFVM3/LKt
bnohkwqXbARwicGNzvL0nJ8FMH7c+X+WuW7Q/IbXYM+Slj5jVJjI6HjEi8zb
HpGH9gC1yvNH+UHHr1mX3rSBFu3ilAs5HF1Qoak5BbbsiYrrsMTGDJhlWako
QuZr+AUPanXRy/lL2HiZ2BDcLwH3A0/1RPuQQDMEZAYJnObxrFUFYZ6HJPzW
w2b5yXQ4M09Yp5G74vQ0sQJMEGnmfwgXBaSAZy4cnJnXcx0aZ8XH4EXKnEXA
m6xeSdrMQ+RMPCucxRRSJh/8HvSfGCTPVrN6WcTeH2ZdkWaQU8emJZHezG5x
6Euc8L9E6IspnIscQadPpph5VsJjhAuNCKu0EFrOvL4mFyNOolNrNjbdaKta
RYrXSF3IU70Vm5lznbTuJgV4QN1Hsf+HEHfyPCJ/2OlT65iTGKLts5TZ1QcN
vgelqUjOcesif46jhT/MH8cnkpz4tPKodW35TYr8ZqfsN/up5Bs9MfkEL4du
S4pxdd3g2AvL/qMfq/6n4ZrAe9cOtTr8/PU8VPLb9U0jjkF6803ZtpLAgtcC
EMV6d2DVWkFJ71/WMmpJBYbu87Ki8PhnjSNgzjS2U8OXP1J55egZpUds3A26
hPtyyT3q1nQ5Jd5n5XYlZw/4HmvwzhB3eZVeP+12ciMjf+IpuwdZeDXX2Oq4
d4kSIJHXc3XRHJWoKx6Tl966qkB5LOD/XpZgnxUfyw3FCFpHP74pZZmX4bqL
G6Qx6qfNPsUrt1yzkkCfnJ6cgHreunJArfKOx/mxpIKr7npob0G0vSyKJyff
/vGP9OyXD+cMwSuwhjdnxQoBWdx7QL7DpKvFbXMngJ6vym3xcYH+rf6uAqqh
Xy8o8kjuJrbJAdOVPuiFp6cEafErdp3aG9heYauMH1s4quuhW4N4+DdYxJOT
b06z0IFM3i7uF1ud/Ltb/H0BSBntI1Aqet76puaPNcPBW0H08/MTImnE1vcr
+uVd0/bdtgEjDgD5qShOnn57kgekcv3N6nr9HcwMuNsvYMH8/Pu2KmusfOER
fwY22Ox4vqffwIzft03zifJP3pXtp/sSVcQBm1s8PznhDd7sgLhdjzL7x3P4
6uTkyZMsDNew3avvNjyD2YPXwBY+ueJfStfwnjQDxv0+rJv0UJ6fflv8gI5i
NMyArQ+ueANbsFaYnn7zlF784AB70R78CAC9+Pb05GkWoC1N/N2K5utgOh+b
IuDm83lxDdYnkoC3njBSFiW+sbe8dezHdNxaES8Go0JyieYMYm9v4L+YBU9m
WkjclFSaVnpCjFttmlxU8mdL/pBtUMMZWxg4lHCjLS2g+UxerDLmLhjaVgrC
Cv518RzsQcoCXGLLM9sXpVto6Nf3JqgdZk2WbYU5Qve1j/Dbu4MWsm6j4viC
gMsrn3kZ0owZaOoDh/4g5GWObktYcYWGqfLkOpxd66h4w8+UrdzmR6OsZAm9
mi6GzCHjQtooDyLpxoUVmWqwcHPC3kPivZ4GhF5/07mlB6LsbOwL5c7OvbsN
yYVJDskKmVSxHrZlPecCHOoT7rstrtyS9hD2jdL0/IWzJgOVm8WVm33HbVU0
L8UWlY+rlFAMkSv3S3e+chSVEnK1m22U8DvxHYw/5SI+uvr+JQls1AT+RLL1
cGyYHR6PulRms9m1WNWf4uLg/wBmPSwwE8oAAA==

-->

</rfc>

