Resource-Oriented Lightweight Information Exchange (ROLIE)
RFC 8322
Document | Type |
RFC - Proposed Standard
(February 2018; No errata)
Was draft-ietf-mile-rolie (mile WG)
|
|
---|---|---|---|
Authors | John Field , Stephen Banghart , David Waltermire | ||
Last updated | 2018-02-14 | ||
Replaces | draft-field-mile-rolie | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Nancy Cam-Winget | ||
Shepherd write-up | Show (last changed 2017-08-31) | ||
IESG | IESG state | RFC 8322 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Kathleen Moriarty | ||
Send notices to | mile-chairs@tools.ietf.org, mile@ietf.org, "Nancy Cam-Winget" <ncamwing@cisco.com> | ||
IANA | IANA review state | IANA OK - Actions Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) J. Field Request for Comments: 8322 Pivotal Category: Standards Track S. Banghart ISSN: 2070-1721 D. Waltermire NIST February 2018 Resource-Oriented Lightweight Information Exchange (ROLIE) Abstract 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. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8322. Field, et al. Standards Track [Page 1] RFC 8322 ROLIE February 2018 Copyright Notice Copyright (c) 2018 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction ....................................................3 2. Terminology .....................................................4 3. XML-Related Conventions .........................................5 3.1. XML Namespaces .............................................5 3.2. RELAX NG Compact Schema ....................................5 4. Background and Motivation .......................................5 5. ROLIE Requirements for the Atom Publishing Protocol .............7 5.1. AtomPub Service Documents ..................................7 5.1.1. Use of the "app:workspace" Element ..................8 5.1.2. Use of the "app:collection" Element .................8 5.1.3. Service Document Discovery ..........................9 5.2. Category Documents .........................................9 5.3. Transport Layer Security ..................................10 5.4. User Authentication and Authorization .....................10 5.5. "/" (Forward Slash) Resource URL ..........................11 5.6. HTTP Methods ..............................................11 6. ROLIE Requirements for the Atom Syndication Format .............11 6.1. Use of the "atom:feed" Element ............................11 6.1.1. Use of the "atom:category" Element .................13 6.1.2. Use of the "atom:link" Element .....................14 6.1.3. Use of the "atom:updated" Element ..................15 6.2. Use of the "atom:entry" Element ...........................16 6.2.1. Use of the "atom:content" Element ..................17 6.2.2. Use of the "atom:link" Element .....................17 6.2.3. Use of the "rolie:format" Element ..................18 6.2.4. Use of the "rolie:property" Element ................19 6.2.5. Requirements for a Standalone Entry ................20 Field, et al. Standards Track [Page 2] RFC 8322 ROLIE February 2018 7. Available Extension Points Provided by ROLIE ...................21 7.1. The Category Extension Point ..............................21Show full document text