RFC 5793: PB-TNC: A Posture Broker (PB) Protocol Compatible with Trusted Network Connect (TNC)

In plain English — editorial summary, not part of the RFC

This document specifies PB-TNC, a Posture Broker protocol identical to the Trusted Computing Group's IF-TNCCS 2.0 protocol. The document then evaluates PB-TNC against the requirements defined in the NEA Requirements specification. [STANDARDS-TRACK]

Document record

Document ID

RFC5793

Published

March 2010

Authors

R. Sahita; S. Hanna; R. Hurst; K. Narayan

Status

PROPOSED STANDARD

Stream

IETF

Area

sec

Pages

76

Also known as

—

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC5793
• Reported errata exist →

Topics

• NEA
• Network Endpoint Assessment

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 8412Software Inventory Message and Attributes (SWIMA) for PA-TNCCurrent

  July 2018

• RFC 5792PA-TNC: A Posture Attribute (PA) Protocol Compatible with Trusted Network Connect (TNC)Current

  March 2010

• RFC 5801Using Generic Security Service Application Program Interface (GSS-API) Mechanisms in Simple Authentication and Security Layer (SASL): The GS2 Mechanism FamilyUpdated

  July 2010

• RFC 5802Salted Challenge Response Authentication Mechanism (SCRAM) SASL and GSS-API MechanismsUpdated

  July 2010

• RFC 5776Use of Timed Efficient Stream Loss-Tolerant Authentication (TESLA) in the Asynchronous Layered Coding (ALC) and NACK-Oriented Reliable Multicast (NORM) ProtocolsCurrent

  April 2010

• RFC 5816ESSCertIDv2 Update for RFC 3161Current

  April 2010

• RFC 5758Internet X.509 Public Key Infrastructure: Additional Algorithms and Identifiers for DSA and ECDSACurrent

  January 2010

Also filed under

• PROPOSED STANDARD
• 2010
• IETF stream
• sec area