%% You should probably cite rfc7967 instead of this I-D.
@techreport{tcs-coap-no-response-option-00,
    number =    {draft-tcs-coap-no-response-option-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-tcs-coap-no-response-option/00/},
    author =    {Abhijan Bhattacharyya and Soma Bandyopadhyay and Arpan Pal},
    title =     {{CoAP option for no server-response}},
    pagetotal = 8,
    year =      2013,
    month =     aug,
    day =       29,
    abstract =  {The server end-point does not respond with acknowledgment (ACK) in non-confirmable(NON)mode of CoAP. However, the server responds the client with a status code indicating "the result of the attempt to understand and satisfy the request". But there may be typical scenarios, while updating resources in NON mode, where any kind of response from the server may be considered redundant. Thus, in this case, the transaction becomes completely open-loop with no reverse path from the server to the client. This kind of exchange may be useful in constrained systems looking for maximized throughput with minimized resource consumption. This draft introduces a header option: 'No-Resp' to suppress any response from the server and discusses an exemplary but practical use case which actually motivated this proposition based on real experience.},
}