Re: [Roll] [MBONED] core/mboned/roll: (which) multicast routing proto/implementations for rfc7390 ff05::fd ?
Alvaro Retana <aretana.ietf@gmail.com> Mon, 09 May 2022 14:55 UTC
Return-Path: <aretana.ietf@gmail.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8481FC159A30; Mon, 9 May 2022 07:55:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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_BLOCKED=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 (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 Ha2QRQeQY66n; Mon, 9 May 2022 07:55:09 -0700 (PDT)
Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) (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 97287C159A1D; Mon, 9 May 2022 07:55:09 -0700 (PDT)
Received: by mail-wr1-x436.google.com with SMTP id e24so19846421wrc.9; Mon, 09 May 2022 07:55:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=NcQn0r/zFa9aphdXJKhJyHSCqpVy2CLHNun9aThfKMI=; b=aZ9/Bec3dgsWpnhZohQ6wVnDb9aHuT13MQDjvDStebml3ZtLG3wAmMAsLuuLZIAxUJ twya1Ot//sb7wY3MsUbVFA7+jnJOHq+KKtElx30LeQ+ari6TMKRz5OGgNiCXFM0AQCH8 GcR+Fmn4pEIDzmr3QpmDUae2uxb1WRb5tqc4ybDv+M9rLrjXZ9VnkeM4M8wmbyZ7QlOM UcXLZztBcveyo2NmSfQ+JaIdsu01GZGfEk7gIGAOH4vUNQnGQ/r+fanGeWLHCdHEaQeL slARcWK6ry+FxRKQAv5m15N9PDgjuA8f1Q10kOU6YKek3A5DjV4RPhO6ypndKjVR6uZA cGwg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=NcQn0r/zFa9aphdXJKhJyHSCqpVy2CLHNun9aThfKMI=; b=E0DkR0gK2XC09SExN/PEuLTS3fwViuSK+92iLt5gRyG57ZfjGJFF1iPpEn+FedzWOD Et+lIgJ+8juyFQIoSThtrMlLW3714mIl4bBsHzAquBXNKc8Jsj9rXRYMgrW5mixPpPFx cBLERbaRPqWACptMdMwuP+UP0xius+yuM4bZmWwyEZC74/qlHdsVavphGdLM/8WRue+8 /yazBdD07JOdpUf+S0LOBG4a3tKUeGqPOgxFj6f7JdRDMRIoEYnQNbGuS2BtFQdrpeu/ h55cViuAKWaGT1dzuoGjmTveuRj9MmJezdhEHKU6n7zyAJHmr6bE3dUBd6oWEFI/sqZz uhwg==
X-Gm-Message-State: AOAM533qGDPbYityuQOgBti0EVmsvP0JSIHXjXKasGZlwduZziD8jjOF 61Zm5A9Rq5iA9wNoSaM2g6qOCBXBtWtVfTOi4cDqUptB
X-Google-Smtp-Source: ABdhPJzKzw9KLL4VR7BPLT3MeEbH/IkG1rpCDcChyBMFWnZkpbud6u7gWkrbzYJ99c5r9JkePpMwNpAmiaKUSUGyi/A=
X-Received: by 2002:a05:6000:1681:b0:20c:5aa2:ae14 with SMTP id y1-20020a056000168100b0020c5aa2ae14mr14015677wrd.443.1652108107061; Mon, 09 May 2022 07:55:07 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Mon, 9 May 2022 07:55:06 -0700
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <YmvaFvE1AiaRyawf@faui48e.informatik.uni-erlangen.de>
References: <YmvaFvE1AiaRyawf@faui48e.informatik.uni-erlangen.de>
MIME-Version: 1.0
Date: Mon, 09 May 2022 07:55:06 -0700
Message-ID: <CAMMESsyge+hYXPPK7WRzAkfTsR6qJw8WYF25aPCmLF2+xX0kgQ@mail.gmail.com>
To: mboned@ietf.org, Toerless Eckert <tte@cs.fau.de>, roll@ietf.org, manet@ietf.org, babel@ietf.org
Cc: anima@ietf.org, core@ietf.org
Content-Type: multipart/alternative; boundary="000000000000da1cd605de95643b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/M97d1ZmyacqagVwbGNAeBe1M0Nw>
Subject: Re: [Roll] [MBONED] core/mboned/roll: (which) multicast routing proto/implementations for rfc7390 ff05::fd ?
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2022 14:55:13 -0000
[Adding manet and babel.] On April 29, 2022 at 8:29:33 AM, Toerless Eckert (tte@cs.fau.de) wrote: Sorry for cross-posting, but this is one of those (set of) question(s) that likeley need it. RFC7390 (and its -bis draft) define CoAP discovery via ASM IP Multicast request/reply on ff0x::fd, with link-local (ff02::fd) for LANs and ff05::fd (Admin Scope) for L3 networks. I am wondering what insight we have about actual use of the L3 version via ff05::fd: - What multicast routing protocols do those networks use this type of resource discover ? - Specifically wireless mesh networks ? - Specifically 802.15.4 wireless mesh networks ? - How many / which known 802.15.4 implementation do or do not support rfc7731 ? Any insight welcome! Background: In anima, two drafts are planning to rely on this ASM IP multicast method, (draft-ietf-anima-constrained-{voucher,join-proxy}) and i have no good insight whether it is prudent to expect that the mayority of target deployment would be able to support this ASM IP multicast routing, or whether we would (worst case) create standard RFC that will not be adopted purely because one dependency (ASM IP Multicast routing for ff05::fd) fails to become supportable well enough in the target networks. And my concerns stems from a range of experiences in challenges with getting ASM IP multicast adopted in non-wireless-mesh networks, rfc8815 is one example (not directly applicable here), rfc8766 and draft-ietf-dnssd-advertising-proxy are actual IETF work also in response to the challenges with ASM IP multicast. But, as said, no direct experience with routed wireless mesh networks such as 802.15.4, although i seem to remember that i was previously told by folks from ROLL that MPL (rfc7731) was also not commonly supported in implementations. Cheers Toerless _______________________________________________ MBONED mailing list MBONED@ietf.org https://www.ietf.org/mailman/listinfo/mboned
- [Roll] core/mboned/roll: (which) multicast routin… Toerless Eckert
- Re: [Roll] [MBONED] core/mboned/roll: (which) mul… Alvaro Retana