%% You should probably cite draft-birkholz-sacm-yang-content-01 instead of this revision.
@techreport{birkholz-sacm-yang-content-00,
    number =    {draft-birkholz-sacm-yang-content-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-birkholz-sacm-yang-content/00/},
    author =    {Henk Birkholz and Nancy Cam-Winget},
    title =     {{YANG subscribed notifications via SACM Statements}},
    pagetotal = 28,
    year =      2017,
    month =     jul,
    day =       20,
    abstract =  {This document summarizes the data model designed at the IETF 99 Hackathon and is intended to grow in to a definition of general XML SACM statements (and later JSON and CBOR, respectively) for virtually every kind of Content Element (e.g. software identifiers, assessment guidance/results, ECA Policy rules, VDD, etc.). The SACM Statement data structure is based on the Information Element (IE) definitions provided by the SACM Information Model. The initial Content Element type transferred are YANG Subscribed Notification acquired via YANG push. In combination with the Origin Metadata Annotation defined in draft-ietf-netmod-revised-datastores the data model defined in this document will ultimately be able to express collected endpoint characteristics, imperative guidance that define and orchestrate assessment instructions, and also the declarative guidance for endpoint attributes.},
}