%% You should probably cite draft-helmprotocol-tttps-09 instead of this revision.
@techreport{helmprotocol-tttps-00,
    number =    {draft-helmprotocol-tttps-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-helmprotocol-tttps/00/},
    author =    {장동호},
    title =     {{The TLS TimeToken Secure Protocol (tttps://)}},
    pagetotal = 16,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {This document specifies the TLS TimeToken Secure Protocol (tttps://), an application-layer protocol extension that augments TLS 1.3 {[}RFC8446{]} with cryptographically verifiable temporal ordering. Where TLS authenticates identity ("who"), tttps:// authenticates temporal origin ("when") in a manner resistant to Byzantine manipulation. The protocol introduces Proof of Time (PoT): a multi-source NTP- synthesized, cryptographically authenticated timestamp bound to a distributed ledger anchor. PoT enables honest participants to achieve preferential execution, while Byzantine nodes are economically evicted through an adaptive state machine (the AdaptiveSwitch mechanism). Primary use cases include MEV-resistant decentralized exchange (DEX) transaction ordering, AI agent-to-agent payment sequencing, IoT mission-critical command ordering, and satellite inter-link communication timestamping. This document has Experimental status to allow deployment experience to accumulate prior to consideration for the Standards Track. The GRG Integrity Pipeline specification will be made available for independent implementation upon conclusion of pending patent proceedings (see Section 10).},
}