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

Susan Hares <shares@ndzh.com> Fri, 25 March 2022 11:17 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 7A82C3A1044 for <idr@ietfa.amsl.com>; Fri, 25 Mar 2022 04:17:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.04
X-Spam-Level: *
X-Spam-Status: No, score=1.04 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 xBs28Kwo-gIz for <idr@ietfa.amsl.com>; Fri, 25 Mar 2022 04:17:05 -0700 (PDT)
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 C2DBF3A1028 for <idr@ietf.org>; Fri, 25 Mar 2022 04:17:04 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=50.107.114.225;
From: Susan Hares <shares@ndzh.com>
To: "'Jeffrey (Zhaohui) Zhang'" <zzhang=40juniper.net@dmarc.ietf.org>, idr@ietf.org
References: <011e01d83493$6175b310$24611930$@ndzh.com> <BL0PR05MB56524EE412C4938C8083E3BED41A9@BL0PR05MB5652.namprd05.prod.outlook.com>
In-Reply-To: <BL0PR05MB56524EE412C4938C8083E3BED41A9@BL0PR05MB5652.namprd05.prod.outlook.com>
Date: Fri, 25 Mar 2022 07:16:45 -0400
Message-ID: <020301d84039$d498d910$7dca8b30$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0204_01D84018.4D88BFB0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGp/yvwH9nW5W2IuizwYX5ak4V6dQKcEeR0rReH02A=
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/eWGQor0vXwJ6zb5mzG6idQKcn5w>
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: Fri, 25 Mar 2022 11:17:10 -0000

Jeffrey: 

 

If this is process question, then 

a) this call was given 2 weeks ago to IDR and BESS.  

b)I check with BESS chairs and they agreed to adoption call with BESS
copied. 

 

If you are concerned about specific technical issues, please provide
detailed comments today as the 2 week adoption call closed yesterday. 

 

Sue 

 

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Jeffrey (Zhaohui) Zhang
Sent: Friday, March 25, 2022 6:30 AM
To: Susan Hares; idr@ietf.org
Subject: Re: [Idr] draft-hb-idr-sr-p2mp-policy (3/10 to 3/24/2022) -
Adoption call

 

I am sorry for responding late. I somehow missed this.

 

I think we should discuss the relationship with
daft-ietf-bess-bgp-multicast-controller further before adopting this.

 

Thanks.
Jeffrey

 

 

Juniper Business Use Only

From: Idr <idr-bounces@ietf.org> On Behalf Of Susan Hares
Sent: Thursday, March 10, 2022 10:28 AM
To: idr@ietf.org
Subject: Re: [Idr] draft-hb-idr-sr-p2mp-policy (3/10 to 3/24/2022) -
Adoption call

 

[External Email. Be cautious of content]

 

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/
<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-hb-idr-sr
-p2mp-policy/__;!!NEt6yMaO-gk!TfiPI1NfecN3db3pj6WZ8paxUr4s6OvmVZ91mapddPFeCk
FZJodxFk8aTGCpYg34$> 

 

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