<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.thomson-nea-problem-statement" target="https://datatracker.ietf.org/doc/html/draft-thomson-nea-problem-statement-03">
   <front>
      <title>Network Endpoint Assessment (NEA) Problem Statement</title>
      <author initials="S." surname="Thomson" fullname="Dr. Susan Thomson">
         <organization>Cisco Systems</organization>
      </author>
      <date month="June" day="28" year="2006" />
      <abstract>
	 <t>   Network Endpoint Assessment (NEA) architectures have been implemented
   in the industry, e.g.  [TNC, NAP, NAC], to assess the software or
   hardware configuration of endpoint devices for the purposes of
   monitoring compliance of endpoints to an organization&#x27;s policy for
   access to the network, and optionally restricting or denying access
   until the endpoint has been updated to satisfy the requirements.
   While these architectures share common components and interfaces to
   support network endpoint assessment, these components are not
   interoperable because not all required protocols are standards.

   This document describes the problem these architectures are intending
   to address, defines common terminology and concepts, and identifies
   interfaces that are candidates for standardization.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-thomson-nea-problem-statement-03" />
   
</reference>
