Internet DRAFT - draft-bormann-core-cross-reverse-convention
draft-bormann-core-cross-reverse-convention
CoRE Working Group C. Bormann
Internet-Draft Universitaet Bremen TZI
Intended status: Standards Track December 06, 2012
Expires: June 9, 2013
A convention for URIs operating a HTTP-CoAP reverse proxy
draft-bormann-core-cross-reverse-convention-00
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.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 9, 2013.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
Bormann Expires June 9, 2013 [Page 1]
Internet-Draft CoAP reverse cross-proxy convention December 2012
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Convention . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
5. Security Considerations . . . . . . . . . . . . . . . . . . . 7
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.1. Normative References . . . . . . . . . . . . . . . . . . . 9
7.2. Informative References . . . . . . . . . . . . . . . . . . 9
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 10
Bormann Expires June 9, 2013 [Page 2]
Internet-Draft CoAP reverse cross-proxy convention December 2012
1. Introduction
(see abstract for now)
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119, BCP 14
[RFC2119] and indicate requirement levels for compliant CoAP
implementations.
In this document, the term "byte" is used in its now customary sense
as a synonym for "octet".
Where bit arithmetic is explained, this document uses the notation
familiar from the programming language C, except that the operator
"**" stands for exponentiation.
Bormann Expires June 9, 2013 [Page 3]
Internet-Draft CoAP reverse cross-proxy convention December 2012
2. Convention
(This is a placeholder document. This section will provide a
convention.)
Bormann Expires June 9, 2013 [Page 4]
Internet-Draft CoAP reverse cross-proxy convention December 2012
3. Examples
In his original contribution, Cullen Jennings proposed translating
http://www.proxy.com/.wellknown/core-translate/1.2.3.4_4567/foo/
bar?a=3
to
coap://1.2.3.4:4567/foo/bar?a=3
Bormann Expires June 9, 2013 [Page 5]
Internet-Draft CoAP reverse cross-proxy convention December 2012
4. IANA Considerations
(none foreseen.)
Bormann Expires June 9, 2013 [Page 6]
Internet-Draft CoAP reverse cross-proxy convention December 2012
5. Security Considerations
TBD.
Bormann Expires June 9, 2013 [Page 7]
Internet-Draft CoAP reverse cross-proxy convention December 2012
6. Acknowledgements
The original point that this document might be needed was brought up
by Cullen Jennings.
Bormann Expires June 9, 2013 [Page 8]
Internet-Draft CoAP reverse cross-proxy convention December 2012
7. References
7.1. Normative References
[I-D.ietf-core-coap]
Shelby, Z., Hartke, K., Bormann, C., and B. Frank,
"Constrained Application Protocol (CoAP)",
draft-ietf-core-coap-12 (work in progress), October 2012.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
7.2. Informative References
[REST] Fielding, R., "Architectural Styles and the Design of
Network-based Software Architectures", Ph.D. Dissertation,
University of California, Irvine, 2000, <http://
www.ics.uci.edu/~fielding/pubs/dissertation/
fielding_dissertation.pdf>.
Bormann Expires June 9, 2013 [Page 9]
Internet-Draft CoAP reverse cross-proxy convention December 2012
Author's Address
Carsten Bormann
Universitaet Bremen TZI
Postfach 330440
Bremen D-28359
Germany
Phone: +49-421-218-63921
Email: cabo@tzi.org
Bormann Expires June 9, 2013 [Page 10]
