[dtn] Bundle multicasting

Alexandre Waeles <alexandre.waeles@netcourrier.com> Sat, 07 November 2020 14:07 UTC

Return-Path: <alexandre.waeles@netcourrier.com>
X-Original-To: dtn@ietfa.amsl.com
Delivered-To: dtn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CCE73A0B2D for <dtn@ietfa.amsl.com>; Sat, 7 Nov 2020 06:07:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.195
X-Spam-Level:
X-Spam-Status: No, score=-0.195 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netcourrier.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wfujU5y1hzLS for <dtn@ietfa.amsl.com>; Sat, 7 Nov 2020 06:07:14 -0800 (PST)
Received: from msg-1.mailo.com (msg-1.mailo.com [213.182.54.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 630963A0AE2 for <dtn@ietf.org>; Sat, 7 Nov 2020 06:07:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=netcourrier.com; s=mailo; t=1604758029; bh=IWfsHIErGYEpuTVjuvCznE+K9lvKzcVbVwkEDb2PsVs=; h=X-EA-Auth:To:From:Subject:Message-ID:Date:MIME-Version: Content-Type; b=Ycu4FXMKILw++TW+WVNk+mPezO19CbJ86PyAyilxPm4DztSQCt2tTBTN7ITBNtVkP hdHwgpBczDNwjU39rFnpE1GD0S8lpTOFcJLOGxJzogrCh082xtnnMj/RJ4YYaDnv+n okfafhWDaL5iLw9YOY4Pluw5Ejjnu5AJu1JjS86k=
Received: by b-6.in.mailobj.net [192.168.90.16] with ESMTP via ip-206.mailobj.net [213.182.55.206] Sat, 7 Nov 2020 15:07:08 +0100 (CET)
X-EA-Auth: S0RAqB/HStLGB6405wVrcgKaxM1NaLe8EUoK/45P/+Mi7qLFWD3BON8tZXwJ6kDQP1eds55ZDB9nNfvYO5+/kMQ65jsA0cunqspIggs1dLl+0z51M94V3w==
To: dtn@ietf.org
From: Alexandre Waeles <alexandre.waeles@netcourrier.com>
Message-ID: <8db295a4-f6d0-a8be-b32c-20bb4c913e05@netcourrier.com>
Date: Sat, 07 Nov 2020 15:07:04 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------728594CE60B25AEDCE4D1D7E"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/X658B9TGXCxaHwg2LhqjoiWXEYs>
Subject: [dtn] Bundle multicasting
X-BeenThere: dtn@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Delay Tolerant Networking \(DTN\) discussion list at the IETF." <dtn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dtn>, <mailto:dtn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dtn/>
List-Post: <mailto:dtn@ietf.org>
List-Help: <mailto:dtn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dtn>, <mailto:dtn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Nov 2020 14:07:17 -0000

Hi,

I'm wondering about how a bundle could be sent to multiple nodes and to 
make sure that every node received the bundle.

I guess it could be made through announcing another "multicast" endpoint 
ID at many different nodes. But I'm not sure on how that could be 
handled in a routing protocol like PRoPHET, would it rather be some 
anycast ?

Thanks,

Alexandre Waeles

-- 
Signature

*Alexandre Waeles* (HE2B: #54023)

Academic contact: awaeles@etu.he2b.be <mailto:awaeles@etu.he2b.be>
Personal contact: alexandre.waeles@netcourrier.com 
<mailto:alexandre.waeles@netcourrier.com>
Personal phone: +32 495 75 49 94 <tel:+32495754994>

Rue Bois des Fosses 42
1350 Enines
Belgium

This message as well as all its attachements are /strictly confidential/ 
and /sent to the attention of its recipients only/ if not stated otherwise.

If this message was sent to you in error, please delete it and notify 
the sender immediately!

*Sharing or copying the content of this message is forbidden!*

------------------------------------------------------------------------

Ce message ainsi que toutes ses pièces-jointes sont /strictement 
confidentiels/ et /envoyées à l'attention de ses destinataires 
uniquement/ si ce n'est pas précisé autrement.

Si ce message vous a été envoyé par erreur, veuillez le supprimer et 
notifier l'expéditeur immédiatement !

*Il est interdit de diffuser ou reproduire le contenu de ce message !*