IETF Logo Mail Archive

Re: [6lo] [pim] Heads-up on draft-ietf-6lo-multicast-registration

Alvaro Retana <aretana.ietf@gmail.com> Tue, 31 May 2022 15:22 UTC

Return-Path: <aretana.ietf@gmail.com>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64BD9C15C0AE; Tue, 31 May 2022 08:22:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level:
X-Spam-Status: No, score=-2.103 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 XgiJBzOMX4Zk; Tue, 31 May 2022 08:22:15 -0700 (PDT)
Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (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 B5776C15AE21; Tue, 31 May 2022 08:22:15 -0700 (PDT)
Received: by mail-wm1-x332.google.com with SMTP id r129so2936300wmr.3; Tue, 31 May 2022 08:22:15 -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=/VNKnD8g706H2g828nMmCGDGsxZf7jOkesaZEeAmQ/s=; b=B9FOM3906HMarGmbXHfjBpQ586RddXlAolHUHyUtTWjH6jOS5WUtOLSWFSmDzSPoAI f3Z5kRrspMajtDB686nV5bpduzQYgMyX0ChFbbaRzqDbdY1MJekM2g1eXsq+HaARFw6h ic2/ik6TmWCtsjoMFglkD4SJyX+FEbcSIyFaYT9qXBmbWnvherJFLi/q1hgo+83sW5+A KkeBLKUeevoF7TMS7JsFYN4tCIbGQtgRIYMPyOu6317ztbcNeG/1sY0rZQ3pSGwuAhU/ FiP6W1JBS3vVoWZehuFpIYjT6I/62YnfjwuFMvbRowcS7Fo9JT26r6mPEP8iGNUAR0ki vZaQ==
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=/VNKnD8g706H2g828nMmCGDGsxZf7jOkesaZEeAmQ/s=; b=qHlnb2LD8VX26lTVAOIdK0+9p+tFRG4UYP4mYHRnv5yUNQvj79Ns2XnmWI1TDhJJqg 3e7P1WZMu363HPE1KenLvH/HLk72Yono8pJWnfcq2/7/i1ie+isVLp26LdOrrItj6zyF mUw1MLlOOlWWasy/0Ihuy4zPhf6EZIX1+kB/DkaaNpvw+VIBcFIzhCfKUaiVUgSwBVp+ pfyjkISpIuE6TgY9/rnMjvljREY4++k10C4+hwH2qhLVGjFGMAPy5vYwFpz6b6Ckz09P EObh5axfk2TYY+wKfB6hiUwRIiUvIw6KWAdnNcRy95zobPGZwsSWRbu7l7t6lWEUXM/2 pbPg==
X-Gm-Message-State: AOAM532v/pn5Hl6nv+uMVEdQDQu9PRfoDOv8eGe6sGX0KwXPIHSbdm5p FiZ+eRHX+to8V/3WiPkuN9OnWk4B+PXf0oye7ap6PlMR
X-Google-Smtp-Source: ABdhPJwrYgeYQginpWnL9Ktke+AsQskQ9OVp5NY2Me/SCO3oP94J17c7/C25zFUcmxcpLBAl5etpc4FXKaljlmIZ5g0=
X-Received: by 2002:a05:600c:a41:b0:39c:1512:98bd with SMTP id c1-20020a05600c0a4100b0039c151298bdmr7452317wmq.88.1654010533645; Tue, 31 May 2022 08:22:13 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Tue, 31 May 2022 08:22:12 -0700
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <CO1PR11MB48819EB0A157BC439FC211D0D8939@CO1PR11MB4881.namprd11.prod.outlook.com>
References: <CO1PR11MB48819EB0A157BC439FC211D0D8939@CO1PR11MB4881.namprd11.prod.outlook.com>
MIME-Version: 1.0
Date: Tue, 31 May 2022 08:22:12 -0700
Message-ID: <CAMMESszkZArBwbefqYz82PTat3vC8TRBFxmLZ64vmjwscFUDXA@mail.gmail.com>
To: "pim@ietf.org" <pim@ietf.org>
Cc: "ROLL WG (roll@ietf.org)" <roll@ietf.org>, "6lo@ietf.org" <6lo@ietf.org>, Pascal Thubert <pthubert@cisco.com>
Content-Type: multipart/alternative; boundary="00000000000050169f05e0505674"
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/SlcEgp6BcK1JGGVxU3RitOa1UhU>
Subject: Re: [6lo] [pim] Heads-up on draft-ietf-6lo-multicast-registration
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 May 2022 15:22:16 -0000

Hi!

Refreshing this message for the pim WG.  I haven’t seen any replies or
opinions. :-(

Please take a look:
https://datatracker.ietf.org/doc/draft-ietf-6lo-multicast-registration/


Thanks!

Alvaro.



On November 10, 2021 at 10:49:15 AM, Pascal Thubert (pthubert) (
pthubert=40cisco.com@dmarc.ietf.org) wrote:

Dear all:

With draft-ietf-6lo-multicast-registration, 6lo is extending the IPv6
stateful address autoconfiguration (RFC 8505/8928) to express that the node
is accepting traffic for an anycast address and to subscribe to multicast
addresses.

The model is a proactive push from the device, compared to MLD reports that
pulls from the router. There are a number for reasons for doing this that
way in energy conscious networks, where multicast and broadcasts are mostly
prohibited, and devices sleep most of their time. Also the incremental code
on constrained devices that operate IPv6 ND as per RFC 8505 is very
minimal.

The proactive model allows the router to inject the MAC and IP information
in a network overlay routing or a proxy function in a fashion that is more
reliable and economical than the classical snooping of MLD and ND. This is
why it is used in RFC 8929 for proxy ND, and proposed for use in RIFT and
now eVPN as the IGP-agnostic UNI between the host and the router.

Since we are extending the registration from unicast to anycast and
multicast, Erik and Alvaro suggested that we raise the topic on this list
as well.

I would certainly be happy to help folks are interesting in drafting how
subscriptions learned from this new work can be injected in PIM as well.

Keep safe;

Pascal

_______________________________________________
pim mailing list
pim@ietf.org
https://www.ietf.org/mailman/listinfo/pim

v2.23.0 | Report a Bug | By Email