A convention for URIs operating a HTTP-CoAP reverse proxy
draft-bormann-core-cross-reverse-convention-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Carsten Bormann | ||
| Last updated | 2013-06-08 (latest revision 2012-12-05) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-bormann-core-cross-reverse-convention-00.txt
Abstract
CoAP is a RESTful transfer protocol for constrained nodes and networks. In many applications, CoAP will be used via cross-protocol proxies from HTTP clients. HTTP client libraries may make it hard to operate an HTTP-CoAP forward proxy by not providing a way to put a CoAP URI on the HTTP Request-Line; reverse-proxying may therefore lead to wider applicability of a proxy. This specification will define a convention for URIs operating such a HTTP-CoAP reverse proxy. The current version of this specification is a placeholder only. It is meant to pick up http://trac.tools.ietf.org/wg/core/trac/ticket/259 and provide a home for its considerations. It might be merged with other documents later.
Authors
Carsten Bormann (cabo@tzi.org)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)