References from draft-haynes-sacm-ecp-mapping
These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.
Document | Title | Status | Type | Downref |
---|---|---|---|---|
BCP 72 |
References Referenced by |
informatively references | ||
draft-fitzgeraldmckay-sacm-endpointcompliance |
Endpoint Compliance Standard
References Referenced by |
informatively references | ||
draft-narten-iana-considerations-rfc2434bis |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | informatively references | |
RFC 2434 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | Possible Reference | |
RFC 3552 |
Guidelines for Writing RFC Text on Security Considerations
References Referenced by |
Best Current Practice | informatively references | |
RFC 5209 |
Network Endpoint Assessment (NEA): Overview and Requirements
References Referenced by |
Informational | informatively references | |
RFC 5792 |
PA-TNC: A Posture Attribute (PA) Protocol Compatible with Trusted Network Connect (TNC)
References Referenced by |
Proposed Standard | informatively references | |
RFC 5793 |
PB-TNC: A Posture Broker (PB) Protocol Compatible with Trusted Network Connect (TNC)
References Referenced by |
Proposed Standard | informatively references | |
RFC 6876 |
A Posture Transport Protocol over TLS (PT-TLS)
References Referenced by |
Proposed Standard | informatively references | |
RFC 7171 |
PT-EAP: Posture Transport (PT) Protocol for Extensible Authentication Protocol (EAP) Tunnel Methods
References Referenced by |
Proposed Standard | informatively references | |
RFC 7632 |
Endpoint Security Posture Assessment: Enterprise Use Cases
References Referenced by |
Informational | informatively references |