@techreport{goland-http-reliability-00,
    number =    {draft-goland-http-reliability-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-goland-http-reliability/00/},
    author =    {Yaron Y. Goland},
    title =     {{SOA-Reliability (SOA-Rity) for HTTP}},
    pagetotal = 14,
    year =      2005,
    month =     nov,
    day =       8,
    abstract =  {SOAR-ity is intended to allow for "reliable" (this term is almost always a misnomer) messaging over HTTP. It achieves this goal by introducing two new request headers, Message-ID which provides a unique ID for a message and MsgCreate which contains the date and time on which the first instance of the message with the associated Message-ID was sent. The purpose of the Message-ID/MsgCreate pair is to allow any HTTP request (e.g. any HTTP method can be used) to be repeated multiple times with a guarantee that the message will be processed no more than one time. In essence it makes any HTTP method call idempotent.},
}