IETF Logo Mail Archive

Re: [Bier] WG LC on https://datatracker.ietf.org/doc/draft-ietf-bier-pim-signaling/

Eric Rosen <erosen@juniper.net> Mon, 19 November 2018 15:31 UTC

Return-Path: <erosen@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 DCF37130DD3 for <bier@ietfa.amsl.com>; Mon, 19 Nov 2018 07:31:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.172
X-Spam-Level:
X-Spam-Status: No, score=-1.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, KHOP_DYNAMIC=1.999, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no 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 XOL9MIo3ZnSn for <bier@ietfa.amsl.com>; Mon, 19 Nov 2018 07:31:38 -0800 (PST)
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 9CC6912426A for <bier@ietf.org>; Mon, 19 Nov 2018 07:31:38 -0800 (PST)
Received: from pps.filterd (m0108157.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id wAJFSnvr014524; Mon, 19 Nov 2018 07:31:38 -0800
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 : content-id : content-transfer-encoding : mime-version; s=PPS1017; bh=GP0gVmh+PMrxxa0L6qDL6qAsyIQsKr7LmEIuU8RYtjI=; b=NBUXwPty6HdyjAw9OQwFz//VoPQI31qT722A331XKy4gnzzr0BtpKYovHhUSriCCXrrB JIng8htCTg1OxpVRDdL+xgWdISnGRy0siBLWgTBrSC9aaLIoY+TvbJuQh0GgVzmm9S2+ 9D/AtrlgRDtY4SCEOas0LWDdVxA1N3nSEr9e/PPXA3aeNpyx/1qnwIIAOM7b4H0jHb6V pCZL+hbbUPKfu1t47c0fEuVA3Ut4n29rwTPSZtz4VZBu1lAUAzcuIBr02Hd2jj8LzCsi T98Womc4rsbJ79tIJrHvlRSmRKTJrw8rFQmSSsKqbUothT4PhC7QmwwN3ZuLB8xrmjJE 6g==
Received: from nam01-bn3-obe.outbound.protection.outlook.com (mail-bn3nam01lp0184.outbound.protection.outlook.com [216.32.180.184]) by mx0a-00273201.pphosted.com with ESMTP id 2nuv0crf4c-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 19 Nov 2018 07:31:38 -0800
Received: from DM5PR0501MB3864.namprd05.prod.outlook.com (10.167.108.27) by DM5PR0501MB3782.namprd05.prod.outlook.com (10.167.107.161) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1361.7; Mon, 19 Nov 2018 15:31:34 +0000
Received: from DM5PR0501MB3864.namprd05.prod.outlook.com ([fe80::240d:b16e:5c81:9acf]) by DM5PR0501MB3864.namprd05.prod.outlook.com ([fe80::240d:b16e:5c81:9acf%5]) with mapi id 15.20.1361.013; Mon, 19 Nov 2018 15:31:34 +0000
From: Eric Rosen <erosen@juniper.net>
To: "Bidgoli, Hooman (Nokia - CA/Ottawa)" <hooman.bidgoli@nokia.com>, "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
CC: Stig Venaas <stig@venaas.com>, BIER WG <bier@ietf.org>, Antoni Przygienda <prz@juniper.net>
Thread-Topic: [Bier] WG LC on https://datatracker.ietf.org/doc/draft-ietf-bier-pim-signaling/
Thread-Index: AQHUW2ERP5l+URmjxkmL7UcNp3Td9aUcXQCAgAEH0jCAAKtcgIAEn0fAgAAdzoCAABDxoIAAAqlAgDNw5ICAATFfAA==
Date: Mon, 19 Nov 2018 15:31:34 +0000
Message-ID: <2f563dc7-7da4-0634-b5f0-53d9333eeb43@juniper.net>
References: <2E5604C8-CCB0-477D-9CB7-B6F2113A52BD@juniper.net> <CAHANBtL_oe9VP1qYOWtRtoOwQca=mckA3QmyZjE3fLPEayeKhg@mail.gmail.com> <VI1PR07MB4751E8BF942AB8985CB034DF91E30@VI1PR07MB4751.eurprd07.prod.outlook.com> <SN6PR05MB5040712468F9CE470D3D10EED4FC0@SN6PR05MB5040.namprd05.prod.outlook.com> <DB7PR07MB47456ED349F01B42FDFCA5E391FF0@DB7PR07MB4745.eurprd07.prod.outlook.com> <8E8276D0-FFAF-4BC3-A2B4-8EAF2BF6E505@juniper.net> <DB7PR07MB4745405084390CBC6416DDDF91FF0@DB7PR07MB4745.eurprd07.prod.outlook.com> <DB7PR07MB4745406406F965320DD853D091FF0@DB7PR07MB4745.eurprd07.prod.outlook.com> <DB7PR07MB4745D37DD1302E25AC9E4B1991DF0@DB7PR07MB4745.eurprd07.prod.outlook.com>
In-Reply-To: <DB7PR07MB4745D37DD1302E25AC9E4B1991DF0@DB7PR07MB4745.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: BYAPR02CA0030.namprd02.prod.outlook.com (2603:10b6:a02:ee::43) To DM5PR0501MB3864.namprd05.prod.outlook.com (2603:10b6:4:7b::27)
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [66.129.241.10]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM5PR0501MB3782; 6:se5swMXUfFmljNozAOXp3KO++lUQzKU8Qny1QALq4745T7oW8KFrLJAt6rqnnatYWzlvkFn811vA6+aOkUvyX9MBvVoJkGT4vyHZdjcUriETJwphPKqRcJdWWzNPoNXLtWf+5QrISQTcjNpED227YMEJ4bvDAoGJ57LMuOz6LZvNIkvfVBc+FKfDC0+5pBbPVcGJPv1gJ6AxUfAYhhJHizD3Tk6lf2Nmzm1ybvr7ttxefIkpY2CrLpdYeFCsIJaRJMyaV4WhRjuOpzV/hL/fLhxhjoKaBoRz+tylL9zn4fKAU19CE1rampf3B/n//FhziW+Od8DImqKdSuxGMv0VQWVlCquIMNQmLde1me3cQXaadOItptagg9ZyDdF+fHMxg+EKeEg0yaRNm2FZpI5wRoQsOLl4zPdw0s+9H5x95OuQud1/ikdRLzsdcfKbn6fXBRXmzx9V4uILZrdYXaHYEA==; 5:L1BWys2DH/j4u6pzOyZicPPm5HefOn8hsMuRy62SCKG2OAz2FApq1D6xGOvGFvqTNKFEFISHAD9hKOa5fn69L2rYnyivXdYDv6L2bfuwCJ0LtS77njxKFewVWC0WUN52gt414oF9zlhVcqRPcA+HGGXgzk33IxDngIbjgh6ZOD8=; 7:parHe1BhvZhRp4GN5CurBwAq2UZaVFGEKTV2mzq5ogcPI6su8J1+3Y/yXg1TLNFS2JqxzmNWR4cAhCnw3FXvNe9rtBE8zbv3ycMkOlKKC+42FehRilf4HOMlNWK2wm5PDaLn6f17PErEJUAujdrBSg==
x-ms-office365-filtering-correlation-id: 3ebfa1e1-800e-484c-b86e-08d64e34167a
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390098)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(4618075)(2017052603328)(7153060)(7193020); SRVR:DM5PR0501MB3782;
x-ms-traffictypediagnostic: DM5PR0501MB3782:
x-microsoft-antispam-prvs: <DM5PR0501MB37827161D8BCFCC62FBC37B2D4D80@DM5PR0501MB3782.namprd05.prod.outlook.com>
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(3002001)(10201501046)(93006095)(93001095)(3231415)(944501410)(52105112)(6055026)(148016)(149066)(150057)(6041310)(20161123564045)(20161123562045)(20161123560045)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(201708071742011)(7699051)(76991095); SRVR:DM5PR0501MB3782; BCL:0; PCL:0; RULEID:; SRVR:DM5PR0501MB3782;
x-forefront-prvs: 08617F610C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(396003)(366004)(39860400002)(346002)(376002)(199004)(189003)(110136005)(31686004)(1941001)(93886005)(14454004)(8936002)(97736004)(36756003)(68736007)(105586002)(476003)(316002)(25786009)(53936002)(6246003)(256004)(4326008)(107886003)(478600001)(54906003)(6116002)(3846002)(5660300001)(2906002)(86362001)(2900100001)(6486002)(6512007)(52116002)(6436002)(229853002)(81156014)(81166006)(6636002)(106356001)(8676002)(66066001)(99286004)(76176011)(71200400001)(71190400001)(11346002)(305945005)(2616005)(446003)(6506007)(26005)(386003)(486006)(53546011)(102836004)(31696002)(7736002)(186003); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR0501MB3782; H:DM5PR0501MB3864.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: Vpupf+0RT/t1Im0NrXMwSGcLYwWXUcmvn49oIR9EvxuIYeYhvWWv155TgLAzXd2cMVaCTJK/17B8sILr3h8Wv6hltbqiOsZFFolrJCCrEc0xj5IkSTwKxe63ZpA5QMueByQ3MXzaHX7rHytPbkU9MZZ3FCatxkJNJaxGfbP1l3eCESNGP8IhRtWviTcf1bpaVsNFEpJoPqFaPgasDu7KGHv+/zACh3WbQLSVmCZtniPWFjU/9Idz668mkqpxtnY05ObkHnGgF6yrAwBWKEzRIBLG3J+Pv3jV8eoY0wDld/VVapA8LlvKyWIekmTdppvzVeOYRN0CJkD9uWpPICJv7XbLORgfpnl5UDfOLXA3KYg=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <612FA507C1F59246BD996EFD5D096171@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 3ebfa1e1-800e-484c-b86e-08d64e34167a
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Nov 2018 15:31:34.7955 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR0501MB3782
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-11-19_06:, , 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=901 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1811190143
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/O6ckAP0j_oXyvqTMqC68ON4q9g4>
Subject: Re: [Bier] WG LC on https://datatracker.ietf.org/doc/draft-ietf-bier-pim-signaling/
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: Mon, 19 Nov 2018 15:31:40 -0000

On 11/18/2018 4:53 PM, Bidgoli, Hooman (Nokia - CA/Ottawa) wrote:
> Jeffery/Stig
>
> Going back to the comments in the IETF for an optional TLV to identify the IBBR in the PIM join.
>
> 1.	Jeffrey forwarded RFC 5384, I am not sure how the TLVs in this RFC will help to identify the IBBR in the PIM signaling packet?

RFC 5384 is about how to add attributes to PIM Joins.  I think the 
suggestion is that a new Join attribute (identifying the IBBR) needs to 
be defined.

> 2.	Thinking more about this, If the implementation on EBBR dictates that the PIM message needs to have an optional TLV that identifies the IBBR, why can't the EBBR add that TLV to the PIM signaling packet before it sends it to the PIM task. All the info are available in the BIER header and before the signaling packet is send to the PIM task on EBBR the EBBR can add this information as an optional TLV. I

Stig is obviously concerned about an implementation in which (a) the 
ability to pass information about the packet from hardware to software 
is limited, and (b) the ability to modify the packet before passing it 
to the control plane processor is minimal or non-existent.  And if these 
abilities exist, it might involve difficult-to-incorporate microcode 
changes.  These issues aren't that mysterious.

v2.23.0 | Report a Bug | By Email