%% You should probably cite draft-silverajan-core-coap-alternative-transports-11 instead of this revision.
@techreport{silverajan-core-coap-alternative-transports-04,
    number =    {draft-silverajan-core-coap-alternative-transports-04},
    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/04/},
    author =    {Bill Silverajan and Teemu Savolainen},
    title =     {{CoAP Communication with Alternative Transports}},
    pagetotal = 17,
    year =      2014,
    month =     feb,
    day =       14,
    abstract =  {CoAP is being 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 understanding how CoAP can operate with other transports, such as the need for M2M communication using non-IP networks, improved transport level end-to- end reliability and security, NAT and firewall traversal issues, and mechanisms possibly incurring a lower overhead to CoAP/HTTP translation gateways. This draft examines the requirements for conveying CoAP packets to end points over such alternative transports. It also provides URI solutions for representing CoAP resources over alternative transports.},
}