IETF Logo Mail Archive

Re: [Bier] BIER WG adoption of https://datatracker.ietf.org/doc/draft-zzhang-bier-php/

"Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net> Wed, 10 October 2018 19: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 2099612785F for <bier@ietfa.amsl.com>; Wed, 10 Oct 2018 12:52:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 9TlH4rZAgLoz for <bier@ietfa.amsl.com>; Wed, 10 Oct 2018 12:52:35 -0700 (PDT)
Received: from mx0a-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 2CF6D1277D2 for <bier@ietf.org>; Wed, 10 Oct 2018 12:52:35 -0700 (PDT)
Received: from pps.filterd (m0108156.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w9AJmoWX028212; Wed, 10 Oct 2018 12: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=KKjuc+cX8js3IjdxClmnpP/6Gpjg+ccqXc6I4CdthRs=; b=Sg1M7lu4Ar5t3dKi2khScvd4/cmDKSKN2BsRdlX8vQ1xDJ5a9mM1j7p4FKcANp+0nplv 0CSe07OkoOUA3izSsjFq5HnV/QuBqAFsf8BwufIj+XF4LQFebNp8jSZmi6V5OnPkdMyf mQXaFIJYAcSaIsUmr+0YIz3+SnmkHMTG9n7ZXYUGKRN+TqU6a9WeLwFRAuE4KCu99CMX d9EjksQzaR6LLy1EwKVMBiNjutKzHW4RpVErEuOUK7Yb4L5uG6Q6h5K/D4aztV9iUw5L D+3ZaFoZmMks//q0g+cscW0xg+D6mEP6EbNBzuhKqAZmJQ2xcq9lFVEzftmZPhX0oOFX 3Q==
Received: from nam05-dm3-obe.outbound.protection.outlook.com (mail-dm3nam05lp0111.outbound.protection.outlook.com [216.32.181.111]) by mx0a-00273201.pphosted.com with ESMTP id 2n1e93satu-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 10 Oct 2018 12:52:33 -0700
Received: from CY1PR05MB2300.namprd05.prod.outlook.com (10.166.192.146) by CY1PR05MB1962.namprd05.prod.outlook.com (10.162.216.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1228.16; Wed, 10 Oct 2018 19:52:31 +0000
Received: from CY1PR05MB2300.namprd05.prod.outlook.com ([fe80::4c5e:bc16:d273:b7fb]) by CY1PR05MB2300.namprd05.prod.outlook.com ([fe80::4c5e:bc16:d273:b7fb%4]) with mapi id 15.20.1228.020; Wed, 10 Oct 2018 19:52:30 +0000
From: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
To: IJsbrand Wijnands <ice@cisco.com>
CC: Antoni Przygienda <prz@juniper.net>, "bier@ietf.org" <bier@ietf.org>
Thread-Topic: [Bier] BIER WG adoption of https://datatracker.ietf.org/doc/draft-zzhang-bier-php/
Thread-Index: AQHUW2F/wIVUmx7F/EG+cm87AG1LeaUYfgUAgAAMtQCAABUkgIAAExkAgAA6feA=
Date: Wed, 10 Oct 2018 19:52:30 +0000
Message-ID: <CY1PR05MB23005F944881AEE61392959ED4E00@CY1PR05MB2300.namprd05.prod.outlook.com>
References: <497C28F0-AF6B-48B5-A979-165C82AF27E1@juniper.net> <95A70C7D-6E74-473A-BF52-750BBE5BC994@cisco.com> <CY1PR05MB2300D2A2021E7F4FF48AFF65D4E00@CY1PR05MB2300.namprd05.prod.outlook.com> <FB5031E7-93E8-496B-AB32-F16B3A0C9EB7@cisco.com> <6093F946-F9C0-4298-83B3-1948AB918D30@cisco.com>
In-Reply-To: <6093F946-F9C0-4298-83B3-1948AB918D30@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
dlp-product: dlpe-windows
dlp-version: 11.0.400.15
dlp-reaction: no-action
x-originating-ip: [66.129.241.14]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY1PR05MB1962; 6:cwUPiKWxAP42dMVISsodbY1rwOeJuNl/G/z0Ty+QJBphfTOaK/uj6LwfFaxpE4syilwYomwUYyQIjTkkEeJXZaIwkE0gXWnVF0YYRZL/PpxnOaaJmyaxVud3og8kianxL00ioN5HGctVwzqvlYd46VApdNqJ2/j1v65KPsqOCySYCXA66UMuIsWEgzFmUCR2JOdaGlw6Oc+PsuG9HFeES5rOj16lb+K7a2q6w34r86sk6mFrva29K+KMpsk3fDa+AQHnM6S+nEO9h0qG2VGT4VmuYDcY0UVcZh4Lre4vYJzWymr1mSlO/DFlNmm3unGPJOXpkjD9cgRPD1MwDo+VQZ579UPWBR9QBKKDMFSJTxPt2gWk+pE8rr1OAd7SvktvHg6lQEE9s+6xpUbKJMvnCX51trYzECusr1XcKXoPWfQZ5Bk1wCetslFLaCo67DQjILdENdbISYGttj9ccq3+zQ==; 5:btTBwopp2gMvuji/2+ZuqrHu1uwJHQsTBUxxlg3Cwvrcj3xfwd4+dyJ/6GrTuUyYk18x8CBKQMTf1v/GyrXmVhVpuaoAW5w3Z9RQiznin2Uj7W4ZTVqtq+bYNCCZhu96YROVzDuSM503OlekjHkoMT/JqYc8rLyleOqvqyHnxSM=; 7:x5eX6HDeXWgAzw8440mwPVPypWjKVibaQMYNbJ048CSf8zl02ZcfeMeBfuHXyhqe0a3Vt80f9fZ1H6AUbcBroqLi+K20qWxpR2t66XiqlrLsiXxco2ZGl8fab6r0IYBdzbKLC+7wlmfTisJKkuTEVAqm0LtSfcQ4E8+VBXisGyxj0qvs9VuenibTABZZPeFxXcxHdidWojhjnQYQ1sRCvnis1fA05Jp5BaYJ40Ig7+2nUGiFBCG83Cja+CwodoPt
x-ms-exchange-antispam-srfa-diagnostics: SOS;SOR;
x-forefront-antispam-report: SFV:SKI; SCL:-1; SFV:NSPM; SFS:(10019020)(346002)(136003)(366004)(39860400002)(376002)(396003)(199004)(189003)(13464003)(97736004)(6916009)(2900100001)(68736007)(25786009)(66066001)(6246003)(4744004)(3846002)(6116002)(4326008)(6506007)(8936002)(105586002)(7696005)(256004)(14444005)(54906003)(93886005)(76176011)(99286004)(106356001)(8676002)(316002)(5660300001)(74316002)(476003)(5250100002)(11346002)(102836004)(86362001)(33656002)(26005)(81156014)(81166006)(486006)(2906002)(186003)(966005)(71200400001)(9686003)(478600001)(14454004)(71190400001)(446003)(7736002)(229853002)(6436002)(55016002)(6306002)(305945005)(53936002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR05MB1962; H:CY1PR05MB2300.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
x-ms-office365-filtering-correlation-id: c9b8bd75-c314-4ff2-17b1-08d62ee9e9a4
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(4618075)(2017052603328)(7153060)(7193020); SRVR:CY1PR05MB1962;
x-ms-traffictypediagnostic: CY1PR05MB1962:
x-microsoft-antispam-prvs: <CY1PR05MB196265DA5FEEADF2CCA3D39DD4E00@CY1PR05MB1962.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(120809045254105)(21748063052155)(28532068793085)(95692535739014)(138986009662008);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3231355)(944501410)(4982022)(52105095)(3002001)(10201501046)(93006095)(93001095)(6055026)(149066)(150057)(6041310)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123558120)(20161123562045)(201708071742011)(7699051); SRVR:CY1PR05MB1962; BCL:0; PCL:0; RULEID:; SRVR:CY1PR05MB1962;
x-forefront-prvs: 08213D42D3
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 6cyi5M97iudOgNZtWSOSlSnGpoa/cw+jQvCWrZzGwriDn7narAdi9AO+wx1FcFbYLEUaqsiUbq+GuALycVef1Pj5aCU1banj5EtGO+qjEXrxY7QVHToJc0P1n1kc0aCz+92y68dWPnRST6/rbgYNlKxgzmGOHmHP3GP+McQybhPw088m7oaJX5LP2Zc6fZ0dTnIpWmJ4zE4zOYZ2Wa9VwhiU5ksF1pEkaLbTQa5mnu57QLNGEWJmPRI24z82Ozwb2cVv6vxNMJpFLv3n5JseqxrFIhYjTwGwMFmJz82INiNgZNGGw9Jet+p0rWlQcFtE+2XLKcxb/9cBTjpthr3jXQ86kz6S13EhWtKwwwQZDwU=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_CY1PR05MB23005F944881AEE61392959ED4E00CY1PR05MB2300namp_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: c9b8bd75-c314-4ff2-17b1-08d62ee9e9a4
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Oct 2018 19:52:30.0825 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR05MB1962
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-10-10_12:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1810100184
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/mmQh-E5RqK5Mw-z5bUkqxmxMvA0>
Subject: Re: [Bier] BIER WG adoption of https://datatracker.ietf.org/doc/draft-zzhang-bier-php/
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 10 Oct 2018 19:52:38 -0000

Hi Ice,

I think we're on the same page - I said the following earlier:

> More importantly, I would expect MVPN/GTM/EVPN kind of deployment is the more appropriate scenario, where there will be a VPN/BD label used, which can associate the packets with a virtual RPF interface. If we're just transitioning an existing PIM deployment to using BIER, then there is no explicit set of edge routers (the premise of PHP is really that some edge routers, like VPN/EVPN PEs, cannot be upgraded to support BIER forwarding) - we can just run PIM if a router does not support BIER yet.

Notice the red text above – I am assuming you’re talking about BGP based overlay signaling.

Jeffrey

> -----Original Message-----
> From: IJsbrand Wijnands <ice@cisco.com>
> Sent: Wednesday, October 10, 2018 12:18 PM
> To: Jeffrey (Zhaohui) Zhang <zzhang@juniper.net>
> Cc: Antoni Przygienda <prz@juniper.net>; bier@ietf.org
> Subject: Re: [Bier] BIER WG adoption of https://datatracker.ietf.org/doc/draft-
> zzhang-bier-php/
>
> Jeffrey,
>
> >> The egress RPF would either disable the RPF check or specify any "core
> interfaces" to be expected incoming interface. This is similar to using P2MP
> tunnels to send multicast traffic w/o signaling (a deployment scenario that has
> been supported by certain vendors already).
>
> Thinking a bit more about this.. Disabling the RPF check I don’t like too much.
> Considering that modifications to the control-plane are allowed, it would be a
> good deployment practise to *always* advertise a downstream label, also for
> the global table scenario, maybe even make it mandatory for this solution...
> That way at least you can map the incoming interface to the BIER Virtual
> interface, which I think is good enough. Or, define BIER_IPV4_EXPLICIT_NULL
> and BIER_IPV6_EXPLICIT_NULL if we can get it. Something to consider..
>
> Thx,
>
> Ice.

v2.23.0 | Report a Bug | By Email