%% You should probably cite draft-silverajan-core-coap-alternative-transports-11 instead of this revision.
@techreport{silverajan-core-coap-alternative-transports-08,
    number =    {draft-silverajan-core-coap-alternative-transports-08},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-silverajan-core-coap-alternative-transports/08/},
    author =    {Bill Silverajan and Teemu Savolainen},
    title =     {{CoAP Communication with Alternative Transports}},
    pagetotal = 18,
    year =      2015,
    month =     jun,
    day =       20,
    abstract =  {CoAP has been standardised as an application level REST-based protocol. A single CoAP message is typically encapsulated and transmitted using UDP or DTLS as transports. These transports are optimal solutions for CoAP use in IP-based constrained environments and nodes. However compelling motivation exists for allowing CoAP to operate with other transports and protocols. Examples are M2M communication in cellular networks using SMS, more suitable transport protocols for firewall/NAT traversal, end-to-end reliability and security such as TCP and TLS, or employing proxying and tunneling gateway techniques such as the WebSocket protocol. This draft examines the requirements for conveying CoAP messages to end points over such alternative transports. It also provides a new URI format for representing CoAP resources over alternative transports.},
}