Re: [pim] Progressing IGMPv3/MLDv2 RFCs, volunteer meeting

Stig Venaas <> Wed, 31 March 2021 01:55 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 52A263A1081 for <>; Tue, 30 Mar 2021 18:55:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id siKb__rmt9yj for <>; Tue, 30 Mar 2021 18:54:56 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::132]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id EBA473A107D for <>; Tue, 30 Mar 2021 18:54:55 -0700 (PDT)
Received: by with SMTP id r17so9670019ilt.0 for <>; Tue, 30 Mar 2021 18:54:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=03yl9pyu4Pdv1g9xQ/k3+3eCNIyZcozMrGZkX5MRjz8=; b=DzWxNaW6Z+O2x5ch5ZljykG3NDr5p1X4v9eYNIM1jFRl1X4XgqWato2o3enCr/R+7o AJLFUQWFK5TDjuh8SFmWxHlGJZfpilz9LooAIkgTJLMReyptKs38XkinDioTGYc6MrlL u2U4cqeQzHFGbSTFLwTWpYY5MiIdStObdbDTyKmJWagkPnPnBmf75VnPRjPngXySpk4e kekjez+P0rHTnDCoKNr5p6o9hxFpXAX/enpwv2VWV0aZMX+LWBPe+VzqMJj0Os4u7Iy0 zUpgnbfdTzFym6a3+udU5XNA3Zvp1fJv6MtM+DqPBe1Pll2WZNL6Jw+NPflV7k0NkbxY 0rug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=03yl9pyu4Pdv1g9xQ/k3+3eCNIyZcozMrGZkX5MRjz8=; b=KI+71CfyMAKKR/JM6V9g55E8eu9zz8J7EyptwHEzc21P7lqn616O4cEESqkMGYUXZA l6xIXEzd2GqcnHsDxDyysu3L6WNlvNwOHkztejyYKdcH0A2oWBuDGK2Dlx4Zv0WZpnO7 EVKeaoYo3TF5IMX8fo3H0cOFAH8KyCfEXUjvAQ6JcXNTyOCXrSB+Djj8HI9q9FyqXeTI 8W+0StBgqbpVqJQNoqxd5+4taK8PcLP/alWwjk60zewfONzOKqm5wJba+VT3KswNoUOu GVYfAYHaCNPy1z6wD9q2MZda8UMb+TIqdwLUGt1v3Qh0Au8+1qj4xrB3+7kqJN3fVeEV aIVQ==
X-Gm-Message-State: AOAM532+/q9olF2wVkZrqikZArhU6yynulkVjzirLj81hzUhoLHSInKY 86L8R92+UK27K3m+AKEfCG1bsxA2a7RImTUmxjPdBWoojyoDAg==
X-Google-Smtp-Source: ABdhPJznt8O5P9RHxWG3sPBqjZkgEKymGr3aMricAgje0Z/w/ihkDWDhJOCt075jItylC+Ed9+evCsXsL0JLDrqvrm0=
X-Received: by 2002:a92:3003:: with SMTP id x3mr845062ile.124.1617155694044; Tue, 30 Mar 2021 18:54:54 -0700 (PDT)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Stig Venaas <>
Date: Tue, 30 Mar 2021 18:54:43 -0700
Message-ID: <>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <>
Subject: Re: [pim] Progressing IGMPv3/MLDv2 RFCs, volunteer meeting
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Protocol Independent Multicast <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 31 Mar 2021 01:55:00 -0000

Hi again

I've gotten several responses which is great. It turns out that the
scheduled time is rather late in the Asian Pacific and we have
interest from there. Even though it is somewhat painful for us at the
US west coast, are people OK if we move this one hour earlier?

That would be April 7 at 14:00 UTC (7:00 PDT, 22:00 CST)

Also, if you are interested in joining, please email me if you haven't already.


On Fri, Mar 26, 2021 at 9:27 AM Stig Venaas <> wrote:
> Hi all
> As mentioned earlier, we're looking for volunteers to work on
> progressing these RFCs. We had some volunteers working on this
> earlier, that I'm hoping are still interested. I've heard from some of
> you. Also happy to get new people that may be interested.
> I'm setting up a meeting for anyone interested to join and we'll
> discuss the work to be done, see who wants to work on it and come up
> with a plan for the work.
> If you may be interested, respond to this email (I have some people I
> know already, that I'll email, but respond to this if you want to make
> sure.
> Would Wednesday April 7 at 15:00 UTC (8:00 PDT, 23:00 CST) work for
> everyone? I hope I got the time zones right. I know there is no
> perfect time. If this time is difficult for you let me know, and we
> can perhaps move it.
> I'll schedule a webex for this meeting soon and will email it
> privately to people. There have been issues in the past with bad
> people hijacking webex for other purposes, hence I would like to not
> post the info publicly where it will end up openly accessible on the
> web.
> Regards,
> Stig