Re: [Pce] Fw: New Version Notification for draft-li-pce-based-bier-00.txt

"lihn6@foxmail.com" <lihn6@foxmail.com> Tue, 06 July 2021 03:24 UTC

Return-Path: <lihn6@foxmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C71E83A19B4 for <pce@ietfa.amsl.com>; Mon, 5 Jul 2021 20:24:36 -0700 (PDT)
X-Quarantine-ID: <xQ6NONRqHFFr>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "Message-ID"
X-Spam-Flag: NO
X-Spam-Score: 1.099
X-Spam-Level: *
X-Spam-Status: No, score=1.099 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HELO_DYNAMIC_IPADDR=1.951, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RDNS_DYNAMIC=0.982, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=foxmail.com
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 xQ6NONRqHFFr for <pce@ietfa.amsl.com>; Mon, 5 Jul 2021 20:24:31 -0700 (PDT)
Received: from out162-62-57-252.mail.qq.com (out162-62-57-252.mail.qq.com [162.62.57.252]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3D7C3A19B2 for <pce@ietf.org>; Mon, 5 Jul 2021 20:24:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foxmail.com; s=s201512; t=1625541865; bh=ZajwtIj6aYfWs+zJtt5gW6im8wd4atusda9LwN98O50=; h=Date:From:To:Subject:References; b=jyXPTv3QmThrHTLH2xbioIcY4SeBQO4VP57g8YKgeOhELj6DWUAO3jim8hAE+zNdw u5yu44QcGlHqAZaABFIEIV9m+Olzmh89dOU1CPsgx2iYevUKYR8r8hQOC+UrolD8l1 7viqNYfDMbUyA82vI3Ur/ZU23+X7/s4daOR0N4Kw=
Received: from DESKTOP-KS7TSLH ([219.142.69.77]) by newxmesmtplogicsvrsza8.qq.com (NewEsmtp) with SMTP id 6182A83C; Tue, 06 Jul 2021 11:24:24 +0800
X-QQ-mid: xmsmtpt1625541864t6ef6cz8g
Message-ID: <tencent_3024551DBBE191E41B73B0321CD8CC614507@qq.com>
X-QQ-XMAILINFO: OEGFU1zX0f4fmtTCPqV8/qL+BwvnvVQZ080lG4tadRxzpw9AbVfD/Y7/zfDlyp mpuxisoa1cWfRkNsJkCHVVmEGd5Cse4unkl11YVhN2TkA1VaUGBMyPhipzBKiA9pOyZeIF9wq64y xqIMPxc2BtIocPT3Tur7F2JR6xgW5i5I9CA6bHTGD+2sQzH79VpvJlTMCHy5Iz2hVx16PNZaM37o EfXWn61JrlI/4iSPPDITdWeczxivVQEsqQGw+sIAY4UDGIA4cSeGqCgVZzQuKNTPHEpABEiSTYVS lYqOxJYjRYSFbR8gq5ktFpR3ZQRp+8Jve77/4lyBR8nixiL3seXRjbDngJ1913xz8IOpjsnbQkix qDW4yTYW3k1RdZwTNYi2VusDMVD3kN+pOGwl1nRNyZnmiHvInqkUOiEn0vyQ+0AHxl8aYuFksqJw e8UPqP5aRYAOsY3OD2iEqKdOXpiTax+o7UsDKIRmPjMxv138zpYz3THFJi3fW5WmxGLguW9GW7qO MiX784kerbgr0FToIKZxftSntUsu6SpV2hfKi/MHex9niJLN+HuHOyw3nvnqhPb1WprDJ1G7ooYg iqppSRRsLMgLgI3IQfj7uOvKdxsFJEgZ37RENfmyAjqFRoIVyJqWpEIgA9tTXvPELH3icf5WS5bq BqNHnGKGG64qk3iOZQKw3KHUHQZG5kN8sXeuHXL3QtpiuuepWjsoaV6NsInKVY+n5wK3OvMzqE// pAzkmwSt0zAA9lTYwi7uy4AF6suUi6MkP9IEhr9qWgLwxBW22OtBjfhd0/InTI7M3+jbaCrtxgPD yG1H7kBgZnF1Q2PpddRaJG/wN+8va4W4tHpCVKZMO2CcT/+C26SAwBRMxGMyMAUMVoZMkjX8m3FY 93k9daHinz
Date: Tue, 6 Jul 2021 11:24:24 +0800
From: "lihn6@foxmail.com" <lihn6@foxmail.com>
To: =?UTF-8?B?QmlkZ29saSwgSG9vbWFuIChOb2tpYSAtIENBL090dGF3YSk=?= <hooman.bidgoli@nokia.com>, =?UTF-8?B?InBjZSI=?= <pce@ietf.org>
References: <2021063010324155895834@foxmail.com>, <DM6PR08MB397820AD37AC4810D3BACF3991019@DM6PR08MB3978.namprd08.prod.outlook.com>
X-Priority: 3
X-GUID: B0515BE3-EEE1-4BFF-BF98-1034C84A75ED
X-Has-Attach: no
X-Mailer: Foxmail 7.2.20.273[cn]
Mime-Version: 1.0
Message-ID: <2021070611242373724628@foxmail.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart026846657326_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/DyOQtuEKDzSm6J_1Uz_THqksG-s>
Subject: Re: [Pce] Fw: New Version Notification for draft-li-pce-based-bier-00.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jul 2021 03:24:37 -0000

Hi, Hooman:

Sorry for the late reply. Thanks for your comments. 
On the issues you have mentioned, our thoughts are as follows:

1. Looking at this draft, is the objective to signal join/leaves of a Source specific Multicast (SSM) only and not ASM?
We were mainly considering SSM for controllable multicast. ASM was not considered in depth at this time. ASM can be extended in this draft in the future.

2. In addition it seems like this only will work for multicast in base routing and not mvpn i.e. I don’t see a route target or is the RD used for VRF identification, can you please verify this?
VPN is taken into consideration. RD is available in MSR object and MRI object, while it is not added in FI object. This is an error, we will add RD to FI object in next update.

3. In addition just to understand why would you want to move the overlay from BGP to PCE?
First, we want to reduce the impact of BGP updates on multicast signaling by decoupling multicast signaling from BGP.
Secondly, SDN is increasingly widely used in network deployment, and the use of PCE can well fit the SDN architecture.
Finally, we will also consider BIER-TE processing, path calculation will inevitably use PCE in BIER-TE. 



Best Regards

Huanan Li
China Telecom
 
From: Bidgoli, Hooman (Nokia - CA/Ottawa)
Date: 2021-07-01 01:03
To: lihn6@foxmail.com; \pce\""
Subject: RE: [Pce] Fw: New Version Notification for draft-li-pce-based-bier-00.txt
Hi All
 
Looking at this draft, is the objective to signal join/leaves of a Source specific Multicast (SSM) only and not ASM? 
 
In addition it seems like this only will work for multicast in base routing and not mvpn i.e. I don’t see a route target or is the RD used for VRF identification, can you please verify this?
 
In addition just to understand why would you want to move the overlay from BGP to PCE? 
 
Thanks
Hooman
 
From: Pce <pce-bounces@ietf.org> On Behalf Of lihn6@foxmail.com
Sent: Tuesday, June 29, 2021 10:33 PM
To: "pce" <pce@ietf.org>
Subject: [Pce] Fw: New Version Notification for draft-li-pce-based-bier-00.txt
 
Hi PCE experts,
 
At present,  the signaling of multicast is mainly distributed processing via BGP messages, and there is no centralized processing solution.
We submit a draft of unified management of BIER multicast signaling by controller via PCEP messages, which can combine the characteristics of BIER and improve the efficiency of interaction, as follows:
Registration of a multicast source to controller(PCE).
Report of joining/leaving message to controller(PCE).
Controller(PCE) sends BitStrings indicating the forwarding of packets in BIER network.
    
Any comments are welcome. 
 


Best Regards.
 
Huanan Li
China Telecom
 
From: internet-drafts
Date: 2021-06-29 14:07
To: Aijun Wang; Huaimo Chen; Huaimo Chen; Huanan Li; Ran Chen
Subject: New Version Notification for draft-li-pce-based-bier-00.txt
 
A new version of I-D, draft-li-pce-based-bier-00.txt
has been successfully submitted by Huanan Li and posted to the
IETF repository.
 
Name: draft-li-pce-based-bier
Revision: 00
Title: PCE based BIER Procedures and Protocol Extensions
Document date: 2021-06-29
Group: Individual Submission
Pages: 18
URL:            https://www.ietf.org/archive/id/draft-li-pce-based-bier-00.txt
Status:         https://datatracker.ietf.org/doc/draft-li-pce-based-bier/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-li-pce-based-bier
 
 
Abstract:
   This document describes extensions to Path Computation Element (PCE)
   communication Protocol (PCEP) for supporting the PCE based Bit Index
   Explicit Replication (BIER) deployment.
 
                                                                                  
 
 
The IETF Secretariat