%% You should probably cite draft-sgcp-state-graph-cryptographic-protocol-01 instead of this revision.
@techreport{sgcp-state-graph-cryptographic-protocol-00,
    number =    {draft-sgcp-state-graph-cryptographic-protocol-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-sgcp-state-graph-cryptographic-protocol/00/},
    author =    {sripad karthik},
    title =     {{State Graph Cryptographic Protocol (SGCP)}},
    pagetotal = 44,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {This document specifies the State Graph Cryptographic Protocol (SGCP), a communication-security framework in which a client and server establish a cryptographically protected session and maintain a synchronized state graph throughout the lifetime of the communication session. SGCP combines device identity, port context, socket context, session identity, ECDH-based shared-secret establishment, cryptographic key derivation, epochs, packet sequence numbers, authenticated state transitions, state-dependent packet transformation, replay protection, continuous context verification, controlled reauthentication, and session recovery. The central principle is that both endpoints independently derive the same cryptographic state from a common authenticated session secret and deterministic state information. The state graph defines which communication states are valid and which transitions are permitted. This document also illustrates the protocol with a worked example of a full-duplex binary media file transfer (an MP3 audio file) showing the complete packet-level exchange.},
}