RFC 8412: Software Inventory Message and Attributes (SWIMA) for PA-TNC
In plain English — editorial summary, not part of the RFC
This document extends "PA-TNC: A Posture Attribute (PA) Protocol Compatible with Trusted Network Connect (TNC)" (RFC 5792) by providing specific attributes and message exchanges to allow endpoints to report their installed software inventory information to a NEA Server, as defined in "Network Endpoint Assessment (NEA): Overview and Requirements" (RFC 5209).
Document record
- Document ID
- RFC8412
- Published
- July 2018
- Authors
- C. Schmidt; D. Haynes; C. Coffin; D. Waltermire; J. Fitzgerald-McKay
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 101
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6876A Posture Transport Protocol over TLS (PT-TLS)Current
February 2013
- RFC 5793PB-TNC: A Posture Broker (PB) Protocol Compatible with Trusted Network Connect (TNC)Current
March 2010
- RFC 8411IANA Registration for the Cryptographic Algorithm Object Identifier RangeCurrent
August 2018
- RFC 8410Algorithm Identifiers for Ed25519, Ed448, X25519, and X448 for Use in the Internet X.509 Public Key InfrastructureUpdated
August 2018
- RFC 8414OAuth 2.0 Authorization Server MetadataCurrent
June 2018
- RFC 8417Security Event Token (SET)Current
July 2018
- RFC 8418Use of the Elliptic Curve Diffie-Hellman Key Agreement Algorithm with X25519 and X448 in the Cryptographic Message Syntax (CMS)Current
August 2018
- RFC 8419Use of Edwards-Curve Digital Signature Algorithm (EdDSA) Signatures in the Cryptographic Message Syntax (CMS)Current
August 2018
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?