%% You should probably cite draft-silverajan-core-coap-alternative-transports-11 instead of this revision.
@techreport{silverajan-core-coap-alternative-transports-02,
    number =    {draft-silverajan-core-coap-alternative-transports-02},
    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/02/},
    author =    {Bill Silverajan and Teemu Savolainen},
    title =     {{CoAP Communication with Alternative Transports}},
    pagetotal = 14,
    year =      2013,
    month =     jul,
    day =       15,
    abstract =  {CoAP is being standardised as an application level REST-based protocol. A single CoAP message is typically encapsulated and transmitted using UDP. This draft examines the requirements and possible solutions for conveying CoAP packets to end points over alternative transports to UDP. UDP remains the optimal solution for CoAP use in IP-based constrained environments and nodes. However 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 provide compelling motivation for understanding how CoAP can operate in various other environments.},
}