idnits 2.17.1 draft-bormann-core-cross-reverse-convention-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (December 06, 2012) is 4157 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'I-D.ietf-core-coap' is defined on line 122, but no explicit reference was found in the text == Unused Reference: 'RFC2616' is defined on line 130, but no explicit reference was found in the text == Unused Reference: 'REST' is defined on line 136, but no explicit reference was found in the text == Outdated reference: A later version (-18) exists of draft-ietf-core-coap-12 ** Obsolete normative reference: RFC 2616 (Obsoleted by RFC 7230, RFC 7231, RFC 7232, RFC 7233, RFC 7234, RFC 7235) Summary: 1 error (**), 0 flaws (~~), 6 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 CoRE Working Group C. Bormann 3 Internet-Draft Universitaet Bremen TZI 4 Intended status: Standards Track December 06, 2012 5 Expires: June 9, 2013 7 A convention for URIs operating a HTTP-CoAP reverse proxy 8 draft-bormann-core-cross-reverse-convention-00 10 Abstract 12 CoAP is a RESTful transfer protocol for constrained nodes and 13 networks. In many applications, CoAP will be used via cross-protocol 14 proxies from HTTP clients. HTTP client libraries may make it hard to 15 operate an HTTP-CoAP forward proxy by not providing a way to put a 16 CoAP URI on the HTTP Request-Line; reverse-proxying may therefore 17 lead to wider applicability of a proxy. This specification will 18 define a convention for URIs operating such a HTTP-CoAP reverse 19 proxy. 21 The current version of this specification is a placeholder only. It 22 is meant to pick up 23 http://trac.tools.ietf.org/wg/core/trac/ticket/259 and provide a home 24 for its considerations. It might be merged with other documents 25 later. 27 Status of this Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at http://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on June 9, 2013. 44 Copyright Notice 46 Copyright (c) 2012 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (http://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 2. Convention . . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 64 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 65 5. Security Considerations . . . . . . . . . . . . . . . . . . . 7 66 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8 67 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 68 7.1. Normative References . . . . . . . . . . . . . . . . . . . 9 69 7.2. Informative References . . . . . . . . . . . . . . . . . . 9 70 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 10 72 1. Introduction 74 (see abstract for now) 76 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 77 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 78 document are to be interpreted as described in RFC 2119, BCP 14 79 [RFC2119] and indicate requirement levels for compliant CoAP 80 implementations. 82 In this document, the term "byte" is used in its now customary sense 83 as a synonym for "octet". 85 Where bit arithmetic is explained, this document uses the notation 86 familiar from the programming language C, except that the operator 87 "**" stands for exponentiation. 89 2. Convention 91 (This is a placeholder document. This section will provide a 92 convention.) 94 3. Examples 96 In his original contribution, Cullen Jennings proposed translating 98 http://www.proxy.com/.wellknown/core-translate/1.2.3.4_4567/foo/ 99 bar?a=3 101 to 103 coap://1.2.3.4:4567/foo/bar?a=3 105 4. IANA Considerations 107 (none foreseen.) 109 5. Security Considerations 111 TBD. 113 6. Acknowledgements 115 The original point that this document might be needed was brought up 116 by Cullen Jennings. 118 7. References 120 7.1. Normative References 122 [I-D.ietf-core-coap] 123 Shelby, Z., Hartke, K., Bormann, C., and B. Frank, 124 "Constrained Application Protocol (CoAP)", 125 draft-ietf-core-coap-12 (work in progress), October 2012. 127 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 128 Requirement Levels", BCP 14, RFC 2119, March 1997. 130 [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., 131 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext 132 Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. 134 7.2. Informative References 136 [REST] Fielding, R., "Architectural Styles and the Design of 137 Network-based Software Architectures", Ph.D. Dissertation, 138 University of California, Irvine, 2000, . 142 Author's Address 144 Carsten Bormann 145 Universitaet Bremen TZI 146 Postfach 330440 147 Bremen D-28359 148 Germany 150 Phone: +49-421-218-63921 151 Email: cabo@tzi.org