RFC 8322: Resource-Oriented Lightweight Information Exchange (ROLIE)
In plain English — editorial summary, not part of the RFC
This document defines a resource-oriented approach for security automation information publication, discovery, and sharing. Using this approach, producers may publish, share, and exchange representations of software descriptors, security incidents, attack indicators, software vulnerabilities, configuration checklists, and other security automation information as web-addressable resources. Furthermore, consumers and other stakeholders may access and search this security information as needed, establishing a rapid and on-demand information exchange network for restricted internal use or public access repositories. This specification extends the Atom Publishing Protocol and Atom Syndication Format to transport and share security automation resource representations.
Document record
- Document ID
- RFC8322
- Published
- February 2018
- Authors
- J. Field; S. Banghart; D. Waltermire
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 43
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5989A SIP Event Package for Subscribing to Changes to an HTTP ResourceCurrent
October 2010
- RFC 4685Atom Threading ExtensionsCurrent
September 2006
- RFC 8600Using Extensible Messaging and Presence Protocol (XMPP) for Security Information ExchangeCurrent
June 2019
- RFC 7970The Incident Object Description Exchange Format Version 2Current
November 2016
- RFC 7632Endpoint Security Posture Assessment: Enterprise Use CasesCurrent
September 2015
- RFC 6819OAuth 2.0 Threat Model and Security ConsiderationsUpdated
January 2013
- RFC 8323CoAP (Constrained Application Protocol) over TCP, TLS, and WebSocketsUpdated
February 2018
- RFC 8040RESTCONF ProtocolUpdated
January 2017
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?