Re: [pim] [spring] wglc: draft-ietf-pim-sr-p2mp-policy

Greg Mirsky <gregimirsky@gmail.com> Sat, 27 April 2024 22:15 UTC

Return-Path: <gregimirsky@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 BB865C14F5EA; Sat, 27 Apr 2024 15:15:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 U-j32cglwmqc; Sat, 27 Apr 2024 15:15:46 -0700 (PDT)
Received: from mail-yw1-x1130.google.com (mail-yw1-x1130.google.com [IPv6:2607:f8b0:4864:20::1130]) (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 E626CC14E515; Sat, 27 Apr 2024 15:15:46 -0700 (PDT)
Received: by mail-yw1-x1130.google.com with SMTP id 00721157ae682-61ab31d63edso27071477b3.1; Sat, 27 Apr 2024 15:15:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1714256146; x=1714860946; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=AuWw4fGRV1dgQWuD1qC5ffsYLkSdc4NcLXNl5QmmdjE=; b=WZsSLa7jPN00rRziqHGx6tHgChPzUZiSd7EnqD3n0JC77duvn8hOFrapHzZg9vM3oy K2coaagTRNoGB087btrklfovRj5hYahaFnrRoFBxqEDl2iSzSpp4L69x7rmy/PeEE5y0 cW5BuVI7NZtGIW63Ojb+D2sUbnXLsO1qIikaetZPUcAFs3C0YQTywsKVy7tFWs7Avrxq tGMCD3Lyw/Cntq0ZS6A/r5OniuwvxoN64da89uRC5veYj3Pq8aIdRDmp3b7/0BipIVwc vBhAaHWBbemwiqMcD+Hjql291rp5Bk1xiTWZXP4l145t7AGhnI8NfAKA9Z6thGYHYFTO HQWA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714256146; x=1714860946; 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=AuWw4fGRV1dgQWuD1qC5ffsYLkSdc4NcLXNl5QmmdjE=; b=Sy2KkF8+biNfREKI0STyEP+Xo6UTl7633E0scWjVnD0LlUTFks7oe3a/5tjgLVdn2X XM6GhtKGfT4Ldevsl7fpXdkfybREnPHN44w6bqT8ek3Zib5ngRQHg8VtGYD4+v7G9B28 M/bZ4mQIO02ecLndXMrvMgNyAGKYnKONitruxJ8KIj2IfZlsPHKCvpcg7UM3nBLyuRpv vKdZ5oVRb0e7Xs8NJb3vn5BsncJyXd84MPCLnK5uZOW7ZHTdTEOy4Nucl8Weyc4yWLh8 iBCxDvDnKXC5tfuszm9Tr5t6R5tbRQ+SQ7pRvBSCuiSoo4MFREFvM8CiP7VwMkiSzC7U W+dA==
X-Forwarded-Encrypted: i=1; AJvYcCUI5R+Yu2rWSKgKA4aIwVeMw959Y3ME0OKO2HKVNnzBehKJOgYBUtMDWxl8zhe1BfzanKdc8BENCC77dqAHuWlcu8kzBq/nKpbX4d34xw==
X-Gm-Message-State: AOJu0YxBxv3HIg9tZvVdaZ3BuycXoTjO14MzykpAEGYhSSrpAVhuV/jZ 1zy3wRt7hM3Xz9Oy78iDDxXCFusKvik6qU8MR5kxpXomQeeeEXUhQH8u3hSgjLWUO6Xszry+De9 3E+pO8Enj69GzsJBlQtGochKIcrFwcg==
X-Google-Smtp-Source: AGHT+IHwS2ig/PLf5ykoBxWTVJ2G/NFRzLGDo6McMgIJ7Jupyy8Ln0Sl6CNFtMdR/AFkRIYQxT7TR/ahji93YRaE/Zs=
X-Received: by 2002:a0d:f943:0:b0:618:90cc:bc4a with SMTP id j64-20020a0df943000000b0061890ccbc4amr2004739ywf.26.1714256145738; Sat, 27 Apr 2024 15:15:45 -0700 (PDT)
MIME-Version: 1.0
References: <BN6PR1301MB2065E3EA8A3CD21A6046FBE3F4122@BN6PR1301MB2065.namprd13.prod.outlook.com> <CA+RyBmXJ_akH-H23Jg7To-1vmEZDaSKeGiE7oYCcRw2zQARcAw@mail.gmail.com> <CABjMoXY9dp3saGz5wP=nqeQU0mHdnTnrvtZMGBtS-2kNaM0Dfw@mail.gmail.com>
In-Reply-To: <CABjMoXY9dp3saGz5wP=nqeQU0mHdnTnrvtZMGBtS-2kNaM0Dfw@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Sat, 27 Apr 2024 15:15:34 -0700
Message-ID: <CA+RyBmU0be79CM88BHC-7e0STJrDPQhn_gFLodeLDML2uH_c+A@mail.gmail.com>
To: Rishabh Parekh <rishabhp@gmail.com>
Cc: Michael McBride <michael.mcbride@futurewei.com>, "pim@ietf.org" <pim@ietf.org>, "spring@ietf.org" <spring@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009ef7cc06171b5c4a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/DH4mNz3SyX7Jf8RvpZd0d9TnQuA>
Subject: Re: [pim] [spring] wglc: draft-ietf-pim-sr-p2mp-policy
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: Sat, 27 Apr 2024 22:15:51 -0000

Hi Rishabh,
thank you for pointing that out to me. The Appendix in RFC 9524 is helpful
by demonstrating how the ubiquitous ping operation works in the presence of
the Replication segment. I think that it would be also helpful to extend
that example by demonstrating the operation of a traceroute, particularly
when DDMAP TLV is included in the echo request message, with a replication
node as a transit node.

Regards,
Greg

On Sat, Apr 27, 2024 at 8:40 AM Rishabh Parekh <rishabhp@gmail.com> wrote:

> Greg,
> Some OAM considerations were added to the parent Replication Segment
> document, now RFC 9524, in section 2.2.2 and Appendix A.2.1 during the WGLC
> in SPRING.
>
> -Rishabh
>
> On Mon, Apr 22, 2024 at 12:25 AM Greg Mirsky <gregimirsky@gmail.com>
> wrote:
>
>> Dear Authors,
>> thank you for a well-written document that is a pleasure to read. I
>> believe that it is ready to progress. However, I have one general
>> observation to make. Although IETF documents are required to include an
>> analysis of the existing and any new security threats, and requested IANA
>> actions, there's no formal requirement to have a text that considers how
>> the defined mechanisms affect existing OAM tools, point to any existing
>> gaps that have been identified and need further work. As a suggestion, it
>> seems that because p2mp SR policies are different from well-known p2p use
>> cases, perhaps this document needs some additional text that points to the
>> OAM-related aspects, specific to p2mp SR policies, e.g., echo request/reply
>> (a.k.a. ping and traceroute), BFD, performance monitoring. WDYT?
>>
>> Regards,
>> Greg
>>
>> On Mon, Apr 22, 2024 at 4:37 AM Michael McBride <
>> michael.mcbride@futurewei.com> wrote:
>>
>>> Hello good people,
>>>
>>>
>>>
>>> Today begins a two week wglc for
>>> https://datatracker.ietf.org/doc/html/draft-ietf-pim-sr-p2mp-policy-08.
>>> The related (normative) replication segment draft has now been published as
>>> a standards track RFC. The poll in the Brisbane pim room was 3 in favor and
>>> 0 against. Please respond with your opinions on the advancement of this
>>> draft.
>>>
>>>
>>>
>>> Thanks,
>>>
>>> mike
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> spring mailing list
>>> spring@ietf.org
>>> https://www.ietf.org/mailman/listinfo/spring
>>>
>> _______________________________________________
>> pim mailing list
>> pim@ietf.org
>> https://www.ietf.org/mailman/listinfo/pim
>>
>