%% You should probably cite draft-wang-jep-receipt-profile-01 instead of this revision.
@techreport{wang-jep-receipt-profile-00,
    number =    {draft-wang-jep-receipt-profile-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-wang-jep-receipt-profile/00/},
    author =    {yuqiang wang},
    title =     {{JEP Receipt Profile: Verifiable Behavior and Evidence Receipts}},
    pagetotal = 28,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {This document defines JEP Receipt Profile 1 (JEP-RP-1), a minimal receipt and evidence profile for the Judgment Event Protocol (JEP) {[}JEP{]}. JEP-RP-1 binds a JEP event to one digest-addressed receipt record through a critical JEP extension. It defines a small behavior-record format, portable receipt manifests and bundles, and independent receipt-validation checks. JEP remains authoritative for event verbs, Event Identity, Event Hash, signature processing, references, extension processing, validation modes, and acceptance semantics. Receipt records are technical evidence about observable behavior and related artifacts. JEP-RP-1 does not assign legal liability, prove subjective intent, establish authorization validity, determine causality or factual truth, define governance outcomes, or establish regulatory compliance.},
}