Network Endpoint Assessment (NEA) Problem Statement
draft-thomson-nea-problem-statement-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dr. Susan Thomson | ||
| Last updated | 2006-06-28 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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'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.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)