Proxy Operations for CoAP Group Communication
draft-tiloca-core-groupcomm-proxy-03
|
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Authors |
|
Marco Tiloca
,
Esko Dijk
|
|
Last updated |
|
2021-02-22
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
htmlized (tools)
htmlized
bibtex
|
Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
CoRE Working Group M. Tiloca
Internet-Draft RISE AB
Intended status: Standards Track E. Dijk
Expires: August 26, 2021 IoTconsultancy.nl
February 22, 2021
Proxy Operations for CoAP Group Communication
draft-tiloca-core-groupcomm-proxy-03
Abstract
This document specifies the operations performed by a forward-proxy
or reverse-proxy, when using the Constrained Application Protocol
(CoAP) in group communication scenarios. Such CoAP proxy processes a
single request, sent by a CoAP client over unicast, and distributes
the request over IP multicast to a group of CoAP servers. It then
collects the individual responses from these CoAP servers and sends
these responses to the CoAP client such that the client is able to
distinguish the responses and their origin servers through addressing
information.
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 https://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 August 26, 2021.
Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
Tiloca & Dijk Expires August 26, 2021 [Page 1]
Internet-Draft Proxy Operations for Group Communication February 2021
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
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
2. The Multicast-Signaling Option . . . . . . . . . . . . . . . 4
3. The Response-Forwarding Option . . . . . . . . . . . . . . . 5
3.1. Encoding of Server Address . . . . . . . . . . . . . . . 7
3.2. Default Values of the Server Port Number . . . . . . . . 8
4. Requirements and Objectives . . . . . . . . . . . . . . . . . 8
5. Protocol Description . . . . . . . . . . . . . . . . . . . . 10
5.1. Request Sending at the Client . . . . . . . . . . . . . . 10
5.1.1. Request Sending . . . . . . . . . . . . . . . . . . . 10
5.1.2. Supporting Observe . . . . . . . . . . . . . . . . . 11
5.2. Request Processing at the Proxy . . . . . . . . . . . . . 11
5.2.1. Request Processing . . . . . . . . . . . . . . . . . 12
5.2.2. Supporting Observe . . . . . . . . . . . . . . . . . 13
5.3. Request and Response Processing at the Server . . . . . . 13
5.3.1. Request and Response Processing . . . . . . . . . . . 13
5.3.2. Supporting Observe . . . . . . . . . . . . . . . . . 13
5.4. Response Processing at the Proxy . . . . . . . . . . . . 13
5.4.1. Response Processing . . . . . . . . . . . . . . . . . 13
5.4.2. Supporting Observe . . . . . . . . . . . . . . . . . 14
5.5. Response Processing at the Client . . . . . . . . . . . . 15
5.5.1. Response Processing . . . . . . . . . . . . . . . . . 15
5.5.2. Supporting Observe . . . . . . . . . . . . . . . . . 16
5.6. Example . . . . . . . . . . . . . . . . . . . . . . . . . 16
6. Reverse-Proxies . . . . . . . . . . . . . . . . . . . . . . . 18
6.1. Processing on the Client Side . . . . . . . . . . . . . . 19
6.2. Processing on the Proxy Side . . . . . . . . . . . . . . 19
7. Chain of Proxies . . . . . . . . . . . . . . . . . . . . . . 19
7.1. Request Processing at the Proxy . . . . . . . . . . . . . 20
7.1.1. Supporting Observe . . . . . . . . . . . . . . . . . 21
7.2. Response Processing at the Proxy . . . . . . . . . . . . 22
7.2.1. Supporting Observe . . . . . . . . . . . . . . . . . 22
Show full document text