![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Opened 10 years ago
Closed 10 years ago
#238 closed editorial (fixed)
Proxy terminology
| Reported by: | cabo@… | Owned by: | hartke@… |
|---|---|---|---|
| Priority: | minor | Milestone: | post-WGLC-1 |
| Component: | coap | Version: | coap-09 |
| Severity: | In WG Last Call | Keywords: | |
| Cc: |
Description
Cullen Jennings notes (msg03072e):
Section 1.2
We have two very different types of proxies - one only speaks COAP and the other type translates between CoAP and HTTP. I would prefer a different terms for the translating type. Perhaps "translator" or "translator proxy". I understand people don't want to use gateway but it is what many people would call a gateway.
-> Agree on terminology and go through the 113 occurrences of "proxy"
Change History (6)
comment:1 Changed 10 years ago by zach@…
comment:2 Changed 10 years ago by angelo@…
from core-http-mapping-04:
- Terminology
A device providing cross-protocol HTTP-CoAP mapping is called an
HTTP-CoAP cross-protocol proxy (HC proxy).
comment:3 Changed 10 years ago by zach@…
In the June 4th interim meeting we settled on "Cross Proxy".
comment:4 Changed 10 years ago by zach@…
- Owner changed from draft-ietf-core-coap@… to hartke@…
comment:5 Changed 10 years ago by cabo@…
Section 10 now (coap-10) has a single instance pf "cross-protocol proxying" (plus one in the heading).
Hence, the abbreviation is not introduced. Fine?
comment:6 Changed 10 years ago by cabo@…
- Resolution set to fixed
- Status changed from new to closed
Fixed with a significant overhaul of the proxy terminology in coap-12.
I would propose "translating proxy"