Re: [Bier] adoption call for draft-zzhang-bier-multicast-as-a-service

"Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net> Thu, 16 June 2022 01:52 UTC

Return-Path: <zzhang@juniper.net>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A140DC14CF16; Wed, 15 Jun 2022 18:52:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.753
X-Spam-Level:
X-Spam-Status: No, score=-2.753 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.745, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net header.b=KNgK2dvD; dkim=pass (1024-bit key) header.d=juniper.net header.b=k9ol/WbG
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 M1MbhhhgPGZ0; Wed, 15 Jun 2022 18:52:34 -0700 (PDT)
Received: from mx0b-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (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 55A30C14CF0B; Wed, 15 Jun 2022 18:52:34 -0700 (PDT)
Received: from pps.filterd (m0108157.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.17.1.5/8.17.1.5) with ESMTP id 25FNqUed003423; Wed, 15 Jun 2022 18:52:33 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=PPS1017; bh=jakeuGxYqGPVQ6Rrfq1msP08fL3tEO/BnGllRWC4pYk=; b=KNgK2dvDljBaRqG8lhrW1tZ4KhtgPL/7sKiYATg0wrgCkV2fkSqGO9k53k8v3hGXGiaj 5WdV86inps0KpFfr11ak/RNZPcwgSYUmzWMpqs3JrlpD2eTSyfiiCAGdNTLrRNt/E37o U8rFm2Q4bu7b1Z6rEEnBgx4hQTJB9DnoBfeBWADCjgFNQRpfu73iAzVa/jjlU/0SYoPI bQFgW1y48Xr5eBAYLjnHWtuv6zQ7ChMH893x7F2hPOUkLwbd+cNm51wW0rrUMORSvRKI PQw+1eDTiYGkJ3R9tiLzerROeb8GzIEvi8K7RetJ7Rlk8iDsJU2+8f/jMQtAO53L7DL+ Pg==
Received: from nam11-co1-obe.outbound.protection.outlook.com (mail-co1nam11lp2171.outbound.protection.outlook.com [104.47.56.171]) by mx0a-00273201.pphosted.com (PPS) with ESMTPS id 3gqfbk9a08-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 15 Jun 2022 18:52:33 -0700
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=eOgLUhCYPf4DAzOmE2zgdU9IFtgHsoI3Y429Nx56hkf+DEFv2HYKrS+3bkOwugSxd67d4YSjAtEOUMFeMdt31eRjuWtWj8aBfNoiMMoX0oVXaYkSEm5EEsG4mVVRU1Lx3EMwXnqIuD4T8XL4ayJULAbXKnDB5hZxMK5Q2uWaPJqnZ0Nm2HhiA+/+kS4Gyv7am8p03OLMtmJqhP/riYnZLhl6qW4iZpZOrw4IB5ECzPaNwAVvFc4QQLFWUfB2ZQyBYNKUD9TBlvr7VWlwFaTyjme91GB2hNAlp92g/jEbr3pfnT1hyIiAfwkSLSyQzhlk1y+APRaubKQjLvq0b8NPaQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=jakeuGxYqGPVQ6Rrfq1msP08fL3tEO/BnGllRWC4pYk=; b=YQ0ULEyvoznDQa1lDVbllIVT3Zy1oY/jwvDYHLvPO1g0Y74jvvKmCSKuABKLL0PftS/azg03tu11lMXP9UCMhFhElHba4npQc7tcVNnXHR8RXSTY2s/67Tg0Ouw5IZAsoKtKe/3/dxdLGQHiI2JfzX2FA+3tcIY1hMMj0lSjldQTy3vFGgAYztTM2VjQ1qDx1r+rmQmXQvrAgTDv0F6cbSXoYoQlyRALouA2agRlzw1de0K+Fxk5WcW9loyh+JXfjWk2JRWUdYbfdL4C3td6N0ZGuudFSpHie5hcnTQTR8pdZHS4a71pPYEsoG6liMF+0oZkH3+gJ7unT1BsuU7MLg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=juniper.net; dmarc=pass action=none header.from=juniper.net; dkim=pass header.d=juniper.net; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=jakeuGxYqGPVQ6Rrfq1msP08fL3tEO/BnGllRWC4pYk=; b=k9ol/WbGIULKsQssceeEWKBBfqeQCO6cYCVFeiofH0yuij+SUhOvyPYpNxREtqwjKBFDG/1Iv4KpBSDGEXtua6SWuKfV70vKWh/RWbo8OhOM8riTNkku5Z0I7XI3TaUJjNADGA40HfmuKgzB1WsJhUgIc0ye0vgCjXcQdPci4Oc=
Received: from BL0PR05MB5652.namprd05.prod.outlook.com (2603:10b6:208:6a::19) by CY4PR0501MB3732.namprd05.prod.outlook.com (2603:10b6:910:8c::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5353.11; Thu, 16 Jun 2022 01:52:30 +0000
Received: from BL0PR05MB5652.namprd05.prod.outlook.com ([fe80::e97b:bb16:8b3a:b5e8]) by BL0PR05MB5652.namprd05.prod.outlook.com ([fe80::e97b:bb16:8b3a:b5e8%7]) with mapi id 15.20.5353.013; Thu, 16 Jun 2022 01:52:30 +0000
From: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
To: Aijun Wang <wangaijun@tsinghua.org.cn>
CC: "EXT-zhang.zheng@zte.com.cn" <zhang.zheng@zte.com.cn>, "bier@ietf.org" <bier@ietf.org>, "bier-chairs@ietf.org" <bier-chairs@ietf.org>
Thread-Topic: [Bier] adoption call for draft-zzhang-bier-multicast-as-a-service
Thread-Index: AQHYf6HzMhaKZN6JYkOi2UddOfDGwq1O7hcQgACxJgCAAaIJgA==
Date: Thu, 16 Jun 2022 01:52:30 +0000
Message-ID: <BL0PR05MB5652796DEA8819323E639322D4AC9@BL0PR05MB5652.namprd05.prod.outlook.com>
References: <BL0PR05MB5652F9FDC0E31D1C9EB5F95CD4AA9@BL0PR05MB5652.namprd05.prod.outlook.com> <DD80E947-CAA8-4255-AAD8-8396EDCED638@tsinghua.org.cn>
In-Reply-To: <DD80E947-CAA8-4255-AAD8-8396EDCED638@tsinghua.org.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Enabled=true; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SetDate=2022-06-16T01:52:27Z; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Method=Standard; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Name=0633b888-ae0d-4341-a75f-06e04137d755; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SiteId=bea78b3c-4cdb-4130-854a-1d193232e5f4; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_ActionId=b221f2b1-e7d4-40cf-bf05-1194a35f24d1; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_ContentBits=2
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b9e3f39c-4081-447a-7806-08da4f3adf7d
x-ms-traffictypediagnostic: CY4PR0501MB3732:EE_
x-ld-processed: bea78b3c-4cdb-4130-854a-1d193232e5f4,ExtAddr
x-microsoft-antispam-prvs: <CY4PR0501MB3732581C0EC2C4707F6219C6D4AC9@CY4PR0501MB3732.namprd05.prod.outlook.com>
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: TiEHKaoRCGMBNJGograZsUgQyVNbLAlGSWEHOVllrg4jfM5sIm9nYgeMHHarUHrhdfQTqSp1CTuC9Z8Nt7VAVdd1L24Ux5WpfYZTybWPZ9XlDRpT5gk5txzWX6xqztKNbeLdayxze7e5pJWxSDAnwTJQQO7SWWGNfvt5ogda/g+r8oEZJAvQmhQ2hRLrfAFHO9o/Mdn2+tozM/pOxzwoY5gDd33fmG7R/Uj/rFUyk23x7X0JOAbP7k8J6xgVdbi/gzGPD01UVF27gnupt9UBBfCcdUswwGOaRjjKKMyQWY04+YwIbeKgHz6vgeZsfiRzGnOr5TV7BbU+9SW0x5IJzJfBbfngdEqIvb5yOvo2yeLq+Y1rtUfaREA1oHuQ0vcxv7LmA0e/ac5S06VuKlPTmtWDFQ/K9whL3Ixp8nkKAMc7dC6Pz4lr75GBibqu+86DHspJRmroaYj6skDueXUaWZAz/fCSK0Z0veB2XqlxhquKdZixJcCEGaiTCz8nHrAGlzrilfg6KrkQCoczDaUudX9n7eyIKjhHdXBQ9Z0UBzJB2B6zEp23WVw8QzLyhcqj1OZJkMXnL7C2SnxpRDL9MYV2acj/mmccILKSW9iJlU4TD+IItqAyb69bC82Ey8lam+1RCf1iGN2GWLJCR4PWXKLtgDrlI/P6PsBUHDha50jC5chqD3VgrChWbvjj6fuRimZQlRkXHjSucH7dHbFRRRcp9pdSADlxuaWdQa6fBKM4vNKHlFnp8ddu9k2Zd097z4Yc0cODcH4z+ZTUBnN0GnOnuJP4UdEb0jZcjOOX7z/MIvsv0KSERcQejVis24E71nRKxfIa52Wj5S8BG+ZR7w==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BL0PR05MB5652.namprd05.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230016)(4636009)(366004)(6506007)(83380400001)(316002)(26005)(166002)(66946007)(186003)(53546011)(7696005)(86362001)(33656002)(9326002)(2906002)(8936002)(52536014)(5660300002)(66556008)(508600001)(55016003)(9686003)(66476007)(64756008)(4326008)(38070700005)(71200400001)(122000001)(66574015)(38100700002)(966005)(66446008)(76116006)(54906003)(6916009); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: CxwX/PL2PX2ZiI6CD/WKp2yt/8feUXhoX5GhObuyx+FDk9JkE24fVNAu5LYtH5vhEbSZqN1fNluKSnV3u6f4QWFhHDU/UIO1w8k38a9JSvx6efsaMWbmZ2uHLuuMePsfJZ2UVxvG8R4lwZNrEWmXA16PLPqQcNur2weDay6bAapW70eY/uBBwSR/154oOWQlyiizeZSMGUfwPoqb+d+D+G6bY/IR4yFHyQtRQ6CJy7dmz+eHmwHvBz5MXouAi518xP2be+7VHQ0SJDqd4CLpFsHfQ6fKjk6Gw3n6OAF3VkUkVZMKJcHSXtFu6v+p/jEd8ngGsNJ/b4XRdgvEYiXvJwvnNfz9T/Qg8PjNBsWHFlccEl75T+h/2MIFHxJt0Ev/77Eq/tOmmsnWDg/Fhv4J100hmWpKGeR6axP/dXNC3+p/RvoyVPZbdAn9sfrI7WawpTFHrgLNDKvdkRSfvPVdFsoT/JVTgo2gWHPt7TQIBd6y1Ym0SKRizRo99AUynk+7sraR5RsuyvLKv+7kYd52Lfoc0RFjTrWPI6/tjCB7R7/HHnAVMHlm0QgXNUfmpTg8YFmDeslCb2lD3AHljtW2u8graqYSfRSa+pMHnVBjaUCqQJbHPYmA64+/LpGlmJjGPhgVlU1LLnn3abi6XzqaiZfnhxx9RAJHF5ZSJLwP6ODm8jvy7za2af3W9dlmg5z0TM52jNjuccjBkN6as1RYjhA5lTvpaXPyYz+Y9o+ly+ng/PnUDUargfQHLwc3+lpCzfRFD+LDtbQG88bv4xattb3iGO8R0jRXRzRA1JO/Bb8fn/0zr6xfijjl6u+ey6PHbEgzIjRcDbes2txlglTFb0zD0SjIF5sWW60ovKtYHkgcE1tGHRNB/t393iMvMK78AedqijMpkw4L1SSUalRkICKv3lEDiCi3wFOflAt4epFmcN9PultBtbclJvoE6h1lJxoDYd0M6Oq1h5MbRgLSZHrVIv9bONeE7CbannyiYwH6VZllOydZmUidkB3eI+kwDOGDaVgySQSNU3VXjSmBr78jurPL+E4HytxXszK3uIzzYbzGWyCFg9e7GTYDxYrx+FKF0sV88+lyAUU+dnxOjZFZ1wuILgdczC16PUu1BTVGrWiqky86KWuO4xkVioPjownGAppNCpeTpZKGrHpU7+pk28ugvNJeX3lpMFMRdgGNetj8zR/VvVRcXcWj17Skj/4VnXFL8c1eMYp5C2XlhwvGVNjjQuUAAIuV7kr8FD3EuyAH21jQWdDwtTg8eJBreSekmYoIBQ/FI0D6WMuWpjcxiUXEMjcYrTzogUErA1xhgxII8QifsePdJX7RFYlB4PjD0sKrq+6K451xf6x3lApyqn7YSaI5/vZshBBkJ4gMlEeqIadJNfrjLEue5bP3+zdf3qZeM3V8/HErqetZFBxIU2IY09ZaKmOJwbKFmpN9gIuwQHVVdUBwBCuXjCV9Nt0qnSiRkyXQRaxOAIAOQE+xghvbI89YJrb4z/QiQZvBZ8UhwleyReYT1QhPx/1jUFV8ftz9BUEPqEvnz623cxcYAhthFv2P68wHJXposcWwJDvRZ9RE0F8gCW0lwu+lhND5OqB1pi5fqITHlXQTQHnmYKMt4funItwjPpvtafikDFOo5NU2CXDxo4l7yy033RrSwEjhYbvmKnivLKkWZsiZOIcZ58yCSxWNAAm/vn+HhU6v76H+lSDkmqrWpwlOVJmLl+W8/b5cF5g3pHIzbw==
Content-Type: multipart/alternative; boundary="_000_BL0PR05MB5652796DEA8819323E639322D4AC9BL0PR05MB5652namp_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BL0PR05MB5652.namprd05.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: b9e3f39c-4081-447a-7806-08da4f3adf7d
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Jun 2022 01:52:30.1960 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: /0je179XW04KDemIxe4Ufzun8q6xNJ8LRkaD/II3HFlwpOZFw+6Ciig1uniAuODTDSpJ/u5uc4duifNilDvXyA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR0501MB3732
X-Proofpoint-ORIG-GUID: hpYEcpEHY-sf6X5knoGSEpI4fIDzb7mG
X-Proofpoint-GUID: hpYEcpEHY-sf6X5knoGSEpI4fIDzb7mG
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.874,Hydra:6.0.517,FMLib:17.11.64.514 definitions=2022-06-15_17,2022-06-15_01,2022-02-23_01
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 mlxscore=0 priorityscore=1501 clxscore=1015 bulkscore=0 adultscore=0 spamscore=0 lowpriorityscore=0 mlxlogscore=999 phishscore=0 suspectscore=0 malwarescore=0 impostorscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2204290000 definitions=main-2206160005
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/9WI7XkOH7Lnka3l4_LORhxNwLGw>
Subject: Re: [Bier] adoption call for draft-zzhang-bier-multicast-as-a-service
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <bier.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bier>, <mailto:bier-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bier/>
List-Post: <mailto:bier@ietf.org>
List-Help: <mailto:bier-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bier>, <mailto:bier-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jun 2022 01:52:39 -0000

Hi Aijun,

Only BFIRs/BFERs (those need to encapsulate or decapsulate BIER headers) need to have BFR-IDs. Transit BFRs don’t need BFR-IDs.

Consider the following:

     BFER1  (customer BIER network) C-BFR1 --- P-BFR1 (provider BIER network) P-BFR2 --- C-BFR2 (customer BIER network) BFER2

P-BFR1/2 are border routers of the provider network. C-BFR1/2 are border routers of the customer network.
C-BFR1 learns BFER1’s BIER prefix and readvertises via BGP to P-BFR1 using SAFI 1/2, who re-advertises into the provider network using the BIER SAFI (or IGP). P-BFR2 learns that and then re-advertises to C-BFR2 (using SAFI 1/2), with the TEA set to itself (so that C-BFR2 will send BIER traffic to P-BFR2 – as explained in https://datatracker.ietf.org/doc/html/draft-zzhang-bier-multicast-as-a-service-04.html#section-2.1).
Now for C-BFR2 to know what BIER label to use to send to P-BFR2, P-BFR2 needs to advertise its own BIER prefix with BIER information.

C-BFR2 does not need to know about P-BFR1 or any other internal BFRs in the provider network.


That is why “when a provider edge re-advertises BIER SAFI routes to its customers, only the ones with BFR-IDs (i.e. these are customer BFERs), and the one originated by itself need to be re-advertised. The provider’s internal BFRs do not need to be advertised to the customers”.



Jeffrey



Juniper Business Use Only
From: Aijun Wang <wangaijun@tsinghua.org.cn>
Sent: Tuesday, June 14, 2022 8:31 PM
To: Jeffrey (Zhaohui) Zhang <zzhang@juniper.net>
Cc: EXT-zhang.zheng@zte.com.cn <zhang.zheng@zte.com.cn>; bier@ietf.org; bier-chairs@ietf.org
Subject: Re: [Bier] adoption call for draft-zzhang-bier-multicast-as-a-service

[External Email. Be cautious of content]

Hi, Jeffrey:
Thanks for your explanation.
Adding the corresponding part will be helpful for the reader. And regarding to the following description:


Zzh> I should add (to the draft) that, when a provider edge re-advertises BIER SAFI routes to its customers, only the ones with BFR-IDs (i.e. these are customer BFERs), and the one originated by itself need to be re-advertised. The provider’s internal BFRs do not need to be advertised to the customers.

Are the above statement contradictory?  Is there any provider’s internal BFR has no BFR-ID? It is still confused that what and how the provider edge router advertise the selected prefixes to the customer—-besides of the customer BFERs, there should be some BFRs within the provider itself?
Aijun Wang
China Telecom

On Jun 14, 2022, at 22:45, Jeffrey (Zhaohui) Zhang <zzhang=40juniper.net@dmarc.ietf.org<mailto:zzhang=40juniper.net@dmarc.ietf.org>> wrote:

Hi Aijun,

Thanks for you review and support.

Please see zzh> below.



Juniper Business Use Only
From: BIER <bier-bounces@ietf.org<mailto:bier-bounces@ietf.org>> On Behalf Of Aijun Wang
Sent: Monday, June 13, 2022 11:51 PM
To: EXT-zhang.zheng@zte.com.cn<mailto:EXT-zhang.zheng@zte.com.cn> <zhang.zheng@zte.com.cn<mailto:zhang.zheng@zte.com.cn>>
Cc: bier@ietf.org<mailto:bier@ietf.org>; bier-chairs@ietf.org<mailto:bier-chairs@ietf.org>
Subject: Re: [Bier] adoption call for draft-zzhang-bier-multicast-as-a-service

[External Email. Be cautious of content]

Hi,

I support its adoption and think it provides the solutions that the customers can use to deploy their multicast services based on BIER technology.
Can the authors make some clarification for the description in section 2.1 “BGP Procedures”: https://datatracker.ietf.org/doc/html/draft-zzhang-bier-multicast-as-a-service-04#section-2.1<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/html/draft-zzhang-bier-multicast-as-a-service-04*section-2.1__;Iw!!NEt6yMaO-gk!ERYbnBni0Qf4qGsC1Rmi0S7a798KRdXxbt7VX9MyohdNzV-D27RZZlv4jLGaBesUGibeLYz8uEFTf7K1i5xwWbAn$>


  “If a provider provides independent BAAS services to multiple

   customers, when its BFR receives BIER prefixes from a customer it

   MUST re-advetise with a new BIER SAFI.  For simplicity, all BFRs of

   the provider use the same RD that is specifically assigned for the

   customer.  When a BFR re-advertises BIER prefixes to a customer, it

   MUST re-advertise with SAFI 1 or 2.”



Why the BIER SAFI is not used when a BFR re-advertise BIER prefixes to a customer?



Zzh> Those multiple customers may have overlapping sub-domain-id and bfr-id. As mentioned below:


1.3.1<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/html/draft-zzhang-bier-multicast-as-a-service-04*section-1.3.1__;Iw!!NEt6yMaO-gk!EIyUWEvhhozndc8Qvd8nOLg5T_J07sX3D5Z_QwzfaywjNxkUbcyCS08HB7uQnWtIdW_qPbWNWBX9Tii2w-aczqGi$>.  Providing Independent BAAS To Multiple Customers

   Now consider that the ISP also provides BAAS for another CDN.  Each
   of the two CDNs has its own BIER domain, with its own BFR-ID or even
   sub-domain ID assignment that could conflict between the two CDNs.
   For example, both have BFR-ID 100 and sub-domain ID 0 assigned but
   they are totally independent of each other.  For an BFR in the ISP to
   support this, with BGP signaling it needs to advertise its own BFR
   prefix multiple times, each time with a different RD that is mapped
   to the corresponding CDN.  A new SAFI BIER (to be allocated by IANA)
   is used.





Zzh> The last two sentences explain why a new SAFI is needed for the provider to advertise its own BIER prefixes multiple times (with different RDs) for those different customers. When it receives BIER prefixes from its customers, it is regular SAF 1/2 not BIER SAFI and it needs to re-advertise via BIER SAFI with corresponding RDs (to match its own advertisements for the customers), and when it re-advertise customer BIER prefixes back to customers, it needs to go back SAFI 1/2 w/o RD – just like regular VPN case (when you re-advertise customer routes into core you use VPN-IP with RD and when you re-advertise routes learned from core to customer you use IP w/o RD).



Zzh> I should add (to the draft) that, when a provider edge re-advertises BIER SAFI routes to its customers, only the ones with BFR-IDs (i.e. these are customer BFERs), and the one originated by itself need to be re-advertised. The provider’s internal BFRs do not need to be advertised to the customers.



And for the IANA consideration part, why the OSPFv3 corresponding part is missed?

Zzh> Thanks for spotting the oversight.
Zzh> Thanks.
Zzh> Jeffrey

Aijun Wang
China Telecom

On Jun 5, 2022, at 18:19, zhang.zheng@zte.com.cn<mailto:zhang.zheng@zte.com.cn> wrote:
This is the 2-week WG adoption call  for
https://datatracker.ietf.org/doc/draft-zzhang-bier-multicast-as-a-service/<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-zzhang-bier-multicast-as-a-service/__;!!NEt6yMaO-gk!EIyUWEvhhozndc8Qvd8nOLg5T_J07sX3D5Z_QwzfaywjNxkUbcyCS08HB7uQnWtIdW_qPbWNWBX9Tii2w6mtpWkm$>
Please indicate your support or objection.
Authors, please respond to the list indicating whether you are aware of any IPR that applies to this draft.
Thanks,
Sandy (As WG secretary, on behalf of Greg/Tony)

_______________________________________________
BIER mailing list
BIER@ietf.org<mailto:BIER@ietf.org>
https://www.ietf.org/mailman/listinfo/bier<https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/bier__;!!NEt6yMaO-gk!EIyUWEvhhozndc8Qvd8nOLg5T_J07sX3D5Z_QwzfaywjNxkUbcyCS08HB7uQnWtIdW_qPbWNWBX9Tii2w35B0pXE$>
_______________________________________________
BIER mailing list
BIER@ietf.org<mailto:BIER@ietf.org>
https://www.ietf.org/mailman/listinfo/bier