[core] I-D Action: draft-ietf-core-multicast-notifications-proxy-01.txt

internet-drafts@ietf.org Wed, 22 April 2026 16:42 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: core@ietf.org
Delivered-To: core@mail2.ietf.org
Received: from [10.244.6.0] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 20BC8E0F73CC; Wed, 22 Apr 2026 09:42:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1776876132; bh=nDfrEhkIhIWRc+k3pJCrlvaulYrQZvtKJGBjZwB6Oeg=; h=From:To:Cc:Subject:Reply-To:Date; b=TTXTTW3AQSZTZKGFxeghQ83norG3IC5tZgxcHnWHmXa4PizrIAf8LL26x/5UeTyiC E4UPd2lGkTa8sls8gyl0VgwbVPJw3/nPY0liS0SFeZ+7a2favcuTkjoZFzHl08FejG EK1r9qcn1j3NCYurV+VI3uV8X1phGDcwenEXFyLc=
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.62.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <177687613205.1083380.12118643279124897175@dt-datatracker-b45949c58-5szpr>
Date: Wed, 22 Apr 2026 09:42:12 -0700
Message-ID-Hash: QXLKDZ6MRRSF4PQP6HQLSGUNJFKAEN6U
X-Message-ID-Hash: QXLKDZ6MRRSF4PQP6HQLSGUNJFKAEN6U
X-MailFrom: internet-drafts@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-core.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: core@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: core@ietf.org
Subject: [core] I-D Action: draft-ietf-core-multicast-notifications-proxy-01.txt
List-Id: "Constrained RESTful Environments (CoRE) Working Group list" <core.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/ItBJzuZTsPYkwb8lck64lRGUS74>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Owner: <mailto:core-owner@ietf.org>
List-Post: <mailto:core@ietf.org>
List-Subscribe: <mailto:core-join@ietf.org>
List-Unsubscribe: <mailto:core-leave@ietf.org>

Internet-Draft draft-ietf-core-multicast-notifications-proxy-01.txt is now
available. It is a work item of the Constrained RESTful Environments (CORE) WG
of the IETF.

   Title:   Using Proxies for Observe Notifications as CoAP Multicast Responses
   Authors: Marco Tiloca
            Rikard Höglund
            Christian Amsüss
            Francesca Palombini
   Name:    draft-ietf-core-multicast-notifications-proxy-01.txt
   Pages:   39
   Dates:   2026-04-22

Abstract:

   The Constrained Application Protocol (CoAP) allows clients to
   "observe" resources at a server and to receive notifications as
   unicast responses upon changes of the resource state.  Instead of
   sending a distinct unicast notification to each different client, a
   server can alternatively send a single notification as a response
   message over multicast, to all the clients observing the same target
   resource.  When doing so, the security protocol Group Object Security
   for Constrained RESTful Environments (Group OSCORE) can be used to
   protect multicast notifications end-to-end between the server and the
   observer clients.  This document describes how multicast
   notifications can be used in network setups that leverage a proxy,
   e.g., in order to accommodate clients that are not able to directly
   listen to multicast traffic.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-core-multicast-notifications-proxy/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-core-multicast-notifications-proxy-01.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-core-multicast-notifications-proxy-01

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts