Re: [dtn] Revival of the IMC multicast scheme
Scott Burleigh <sburleig.sb@gmail.com> Tue, 13 December 2022 22:52 UTC
Return-Path: <sburleig.sb@gmail.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 47B03C14CE26 for <dtn@ietfa.amsl.com>; Tue, 13 Dec 2022 14:52:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.094
X-Spam-Level:
X-Spam-Status: No, score=-7.094 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jhfGbYpHAuJk for <dtn@ietfa.amsl.com>; Tue, 13 Dec 2022 14:52:35 -0800 (PST)
Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0956CC14CE23 for <dtn@ietf.org>; Tue, 13 Dec 2022 14:52:35 -0800 (PST)
Received: by mail-lf1-x131.google.com with SMTP id bp15so7448819lfb.13 for <dtn@ietf.org>; Tue, 13 Dec 2022 14:52:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=WbxB21epLJ7TVtQMkKo6fSp4r+WYekfOZhOorXFrfyQ=; b=Pr0UO2Xwl5Amk4qOx+k64sMz/7XL3vg9CKjsQlx+csvCvGo3Uaw5niviheusaTh0PW 6g9V8WAT1IFvihbGD0hsvb70VxYCu3eu7Sbd+VQCkJ+ApMZhZjzJeXlqXd4INqn055R5 RwK9em17BBG5G1APaw6+q681V7JGsM9bu8NzsSCc8LxatnAsOP2Mc24Nbz1L2ln/+TE7 YRhqSG2D70aV8r2yP16hdUYIVwfR5OF/XuW4V4KC8fNha68qSrQj/2jnp0Nzc/aaIRx5 1VRMIkUpxy1D3IXegfMaiiVvw5vUVZn6F2l2okOj6aM0YUZ8fHeOdVrrexqjL0dQiKld K7fw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=WbxB21epLJ7TVtQMkKo6fSp4r+WYekfOZhOorXFrfyQ=; b=wldlCk32Snzw4UxbcxBPh3zZ4Dlvr/r9fnxeZdnwfbkuuF3RKV+Z/I4AVVxsGerzi2 JpcayWwOSmubWlazrDDHAUVMI9060mxDFpgrOZe7vkl71RsO8Lqn44KQ7Vs3WbWdwljh lqPfMiUsHbxE43biGO9MHnkcYeBfV86cO7UV+Aw5aRmorF9y+Bwh8IxJ7F78or3eu0Mu /UOSb2e9zdH9yftdyobwDyF9+D/+TONXYmIVv1A44s1cMx/w1cJqMV0VIbx0GP9hvPNa 6wSnmuu3VJ3sRJtylz3FPeck9jwR+WxBlzhC0T2TCNflmgddgwXFJqr6qpJfNXEj82YZ wbrQ==
X-Gm-Message-State: ANoB5pk5gfeiWwcziL2BPWJqlNjn9mSjIOVyzRxTrfCDQZF40ubz8cwW 7jsGUGu8dG6bsB0skS/QLeGjnsE+TjhMT2COiB8LtReP
X-Google-Smtp-Source: AA0mqf5ZuA5AppBu7c04Ez30ESf/4umhepcdl96HitbzsHI51O12OhclNHdV/9Irsb7HSaGpViRI5uZaHfrR/GRn8jo=
X-Received: by 2002:a05:6512:b24:b0:4b6:f206:a9eb with SMTP id w36-20020a0565120b2400b004b6f206a9ebmr563287lfu.450.1670971952653; Tue, 13 Dec 2022 14:52:32 -0800 (PST)
MIME-Version: 1.0
References: <ddacbba4f8cc4126ac98983b70dcbed8@jhuapl.edu>
In-Reply-To: <ddacbba4f8cc4126ac98983b70dcbed8@jhuapl.edu>
From: Scott Burleigh <sburleig.sb@gmail.com>
Date: Tue, 13 Dec 2022 12:52:22 -1000
Message-ID: <CA++2eb0E88Tq+y=ZftbffHnQEkLBi7tsL6BP0Aze7AP+CVxO7w@mail.gmail.com>
To: "Sipos, Brian J." <Brian.Sipos@jhuapl.edu>
Cc: dtn@ietf.org
Content-Type: multipart/alternative; boundary="000000000000aae98505efbd791e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/CUhs36WXyyzza50lmzTtS9qKELo>
Subject: Re: [dtn] Revival of the IMC multicast scheme
X-BeenThere: dtn@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 13 Dec 2022 22:52:37 -0000
Thanks, Brian, I am very much interested in that. I haven't been pushing multicast for a while, as it seemed like the WG had plenty of other fish to fry, but I believe it is critically important. Let's start on a draft. On Tue, Dec 13, 2022, 12:39 PM Sipos, Brian J. <Brian.Sipos@jhuapl.edu> wrote: > Scott, > > Would you be interested in reviving the IMC endpoint draft [1] and > updating the membership petitions for BPv7 and potentially multiple groups? > > If so, I would be happy to review and contribute to the document. I have > some feedback about group registration and comments/questions about service > identification. I also have some questions about how an ION-based network > would bootstrap a multicast tree currently. > > Thanks, > > Brian S. > > > > [1] https://datatracker.ietf.org/doc/html/draft-burleigh-dtnrg-imc-00 > > >
- [dtn] Revival of the IMC multicast scheme Sipos, Brian J.
- Re: [dtn] Revival of the IMC multicast scheme Olivier De jonckere
- Re: [dtn] Revival of the IMC multicast scheme Scott Burleigh
- Re: [dtn] Revival of the IMC multicast scheme sburleig.sb
- Re: [dtn] Revival of the IMC multicast scheme Olivier De jonckere