IETF Logo Mail Archive

Re: [Idr] draft-hb-idr-sr-p2mp-policy (3/10 to 3/24/2022) - Adoption call

Susan Hares <shares@ndzh.com> Thu, 10 March 2022 15:27 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FC7D3A10CF for <idr@ietfa.amsl.com>; Thu, 10 Mar 2022 07:27:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.061
X-Spam-Level:
X-Spam-Status: No, score=-4.061 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ALQK_fotRgsj for <idr@ietfa.amsl.com>; Thu, 10 Mar 2022 07:27:47 -0800 (PST)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8A353A0F74 for <idr@ietf.org>; Thu, 10 Mar 2022 07:27:46 -0800 (PST)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=50.107.120.176;
From: Susan Hares <shares@ndzh.com>
To: idr@ietf.org
Date: Thu, 10 Mar 2022 10:27:40 -0500
Message-ID: <011e01d83493$6175b310$24611930$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_011F_01D83469.78A06E60"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Adg0k0r8SPpUu5oNRbilwxi9GChogA==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/VwiMYgQWWHOouUY6n0nOofSA2XE>
Subject: Re: [Idr] draft-hb-idr-sr-p2mp-policy (3/10 to 3/24/2022) - Adoption call
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Mar 2022 15:27:51 -0000

IDR WG: 

 

If you just wish to respond to the IDR list, 

you may respond to this email on the adoption call. 

 

Cheers, Sue 

 

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Thursday, March 10, 2022 9:55 AM
To: idr@ietf.org; pim@ietf.org; bess@ietf.org
Subject: [Idr] draft-hb-idr-sr-p2mp-policy (3/10 to 3/24/2022)

 

This begins a 2 week WG adoption call for: 

draft-hb-idr-sr-p2mp-policy from (3/10 to 3/24/2022) 

 

You can obtain the draft at: 

https://datatracker.ietf.org/doc/draft-hb-idr-sr-p2mp-policy/

 

In your comments for this call please consider: 

 

1)  Does this technology support the SR P2MP features 

that distributes candidate paths which connect 

a multicast distribution tree (tree to leaves). 

 

2) Is the technology correctly specified for the 

NLRI (AFI/SAFI) and the tunnel encapsulation attribute 

additions (sections 2 and 3)? 

 

3) Does the P2MP policy operation (section 4) 

provide enough information for those implementing this 

technology and those deploying the technology? 

 

4) Do you think this multicast technology is a good

Place to start for P2MP policy advertisement via BGP? 

 

5) Do you think this SR P2MP policies should not be advertised 

via BGP? 

 

Cheers, Susan Hares

v2.23.0 | Report a Bug | By Email