Re: [pim] Status of advancing 3376/3810 to full standard

Alvaro Retana <aretana.ietf@gmail.com> Tue, 12 July 2022 12:54 UTC

Return-Path: <aretana.ietf@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01E50C14CF03 for <pim@ietfa.amsl.com>; Tue, 12 Jul 2022 05:54:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.104
X-Spam-Level:
X-Spam-Status: No, score=-7.104 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, 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 IjMKQ_0FoL9K for <pim@ietfa.amsl.com>; Tue, 12 Jul 2022 05:54:22 -0700 (PDT)
Received: from mail-lf1-x12c.google.com (mail-lf1-x12c.google.com [IPv6:2a00:1450:4864:20::12c]) (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 142A6C14CEFC for <pim@ietf.org>; Tue, 12 Jul 2022 05:54:22 -0700 (PDT)
Received: by mail-lf1-x12c.google.com with SMTP id e28so10188530lfj.4 for <pim@ietf.org>; Tue, 12 Jul 2022 05:54:21 -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; bh=MJ8+lxvyXGXfobpRQkh6EgQIpJOM2k5GS/g8CJcSW4g=; b=HvPceFHpV28vk1DBSDmATQWT4u37frAsX4Qa1q9vw0HfbmNsfmSuc6uTFclD3HwU/a BG8E7o1gEJSP6xDqO5FvGtzGGDUz4da7yEeCXJXEHo5Le9ztgib364m6+oE/LQRoibYk XfUJE/PINrJobToOYSth0+ek97Ps+wVMe8tEc3MVxSDM4oFKqQPLVVCq3XrSqgUooVcr 4wyDvnaWxjWgdTa6lnS4e5cgcTUF4B+878q6KMlV3bpKoTyFfEQ3EVqJ/XV2s3KUh/Fv clkyUPYcHOJOKMRxak/TXsFLDGE84BmKiLLI15wWH495GEkAcdRqKrMAd0SoWhIkgPc4 tuXA==
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; bh=MJ8+lxvyXGXfobpRQkh6EgQIpJOM2k5GS/g8CJcSW4g=; b=u4WjY2nF3KTgA612WLCEPvFigsYVkc/6kq2ePB60okHCqocglSSykkA339AU+B0nCE 0nV4pQnc5QTsdoKv/bznzzPIWb5OF4t+TEwIQl0fAOYO3pPxr4QgPmZtnvep26aySWJW uOFExpyo1vt/fGKr09R3daC7bDvFDiTcpbQbyjsjBy77fUWXznZc0YgNJ+pFioM10n7d CCh6Kdig2+opzk1ncgBGCSVCxSV3P7eLi/UAUF98e7NZpKKmbb1QNZfl8yHIR09y9JSv vICdxq0oJV+vChNItxwZs95z6nTWwVPZpz31zgj/2ro1NqKcdfp/4Wbf9Uackxw93Kle k6MQ==
X-Gm-Message-State: AJIora9iTw6s0kTg5y4Sz7hcC9HEHcn8/YoZz2WbcqsH+LsNv35r+7pS yXOci52Xdfhwtan/9Z0Woo4R3SIKEw5iOJOy3HHfEWOL
X-Google-Smtp-Source: AGRyM1tXKZAAWzr6Wi52Ziw9zkd68AD8bvBBJUVII2oqBIMBryu9IZfC6nl+D5HMLlPZhsZeZ6Sl73uEK+Tq2TO5up8=
X-Received: by 2002:a05:6512:3a88:b0:481:4bb:3246 with SMTP id q8-20020a0565123a8800b0048104bb3246mr15524406lfu.292.1657630460009; Tue, 12 Jul 2022 05:54:20 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Tue, 12 Jul 2022 12:54:19 +0000
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <35534782-2a1d-0585-08ae-d69475b921be@innovationslab.net>
References: <35534782-2a1d-0585-08ae-d69475b921be@innovationslab.net>
MIME-Version: 1.0
Date: Tue, 12 Jul 2022 12:54:19 +0000
Message-ID: <CAMMESszdF+u1r78G9y+KgWyaKMLi-ip5B7W99jCuF20EepzXhA@mail.gmail.com>
To: Brian Haberman <brian@innovationslab.net>, "pim@ietf.org" <pim@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000bce11b05e39b2a6d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/o491G4c9StRhyh6XuMfVJjEb8AU>
Subject: Re: [pim] Status of advancing 3376/3810 to full standard
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2022 12:54:23 -0000

Brian:

Hi!

This would add extra scope to the bis documents, which may be interpreted
as a significant change from the base specs.  However, given that rfc4604
was published over 15 years ago (updating both base specs), I think it can
be argued that this was part of the specs all along (i.e. it is not a
significant change).

All this is to say that we’ll want to provide strong justification — in the
Shepherd write-up, at least.

Thanks!

Alvaro.

On July 8, 2022 at 12:05:46 PM, Brian Haberman (brian@innovationslab.net)
wrote:

Hi all,
I just posted revisions to 3376bis and 3810bis, both now at -03.
In our issue tracker, there is one remaining work item that we
identified, the potential incorporation of SSM specific operation into
the base specifications...

RFC 4604 updates both 3376 and 3810. I believe the right next step
is to move the requisite text from 4604 to 3376bis and 3810bis. After
that, the two bis drafts can mark 4604 Obsolete or we can make a request
to move 4604 to Historic.

Any thoughts/concerns with the above plan?

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