IETF Logo Mail Archive

Re: [Bier] Comment on draft-hj-bier-mldp-signaling-00

"Bidgoli, Hooman (Nokia - CA/Ottawa)" <hooman.bidgoli@nokia.com> Sun, 15 July 2018 22:31 UTC

Return-Path: <hooman.bidgoli@nokia.com>
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 8D7BF130E96 for <bier@ietfa.amsl.com>; Sun, 15 Jul 2018 15:31:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.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 Q-oFB_ZTsamT for <bier@ietfa.amsl.com>; Sun, 15 Jul 2018 15:31:05 -0700 (PDT)
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-vi1eur04on0716.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe0e::716]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E0B3130E89 for <bier@ietf.org>; Sun, 15 Jul 2018 15:31:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com; s=selector1-nokia-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=U05y0QpaoqQWMsADIrTjTQlI8HcT5BWyaZRY0a2pJR8=; b=pdF8ktfXqgCrjFy5wQMNC477H/6O6khg9CDeL6F4iXlGekjjhI97yYuDtq/L/sImlUN0ZBrATOa17yDWdcqyhUuKAtf6tMTiuwwQtLUVv0LlAeJalFUJEEYB2KbOqWx0TvcizgxTLiRxnhXs8ieu98dt5AGkStLQb7sygoPnKsA=
Received: from VI1PR0701MB2351.eurprd07.prod.outlook.com (10.168.137.146) by VI1PR0701MB2767.eurprd07.prod.outlook.com (10.173.81.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.973.14; Sun, 15 Jul 2018 22:31:01 +0000
Received: from VI1PR0701MB2351.eurprd07.prod.outlook.com ([fe80::7c4e:57c0:1814:30db]) by VI1PR0701MB2351.eurprd07.prod.outlook.com ([fe80::7c4e:57c0:1814:30db%5]) with mapi id 15.20.0973.013; Sun, 15 Jul 2018 22:31:01 +0000
From: "Bidgoli, Hooman (Nokia - CA/Ottawa)" <hooman.bidgoli@nokia.com>
To: Eric C Rosen <erosen@juniper.net>, BIER WG <bier@ietf.org>
Thread-Topic: [Bier] Comment on draft-hj-bier-mldp-signaling-00
Thread-Index: AQHUGJK7ydY9zk8PIU+Ih2ZAjGnDvKSQ1M1A
Date: Sun, 15 Jul 2018 22:31:01 +0000
Message-ID: <VI1PR0701MB2351BB0170B30DDA7D8DA824915E0@VI1PR0701MB2351.eurprd07.prod.outlook.com>
References: <1808952e-97a3-f1a1-36f1-ab4271d01e02@juniper.net>
In-Reply-To: <1808952e-97a3-f1a1-36f1-ab4271d01e02@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=hooman.bidgoli@nokia.com;
x-originating-ip: [173.32.187.177]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VI1PR0701MB2767; 6:QrPuaFBkWE7DRnTFW1zHt5cG7H7N7X15RqSHS/P3UdrtVob5Zq/Ywlg+r4VYT6gGUi8Zw59my01so7otooslOpczjzXvZJ5ojkiu61nsXdt7Dwsi4y8rU5nkXhzId3x5uOlL3+Z3uF7Ld/o74ycTBuCM/5ou2ZTROzWuqXLdsP9fAGmwJCa6UMvUfwTtiBDqkpkWjO+lgKUUp4J28Ovp4MYfAxinFCql41N2C1z+ODntraFts4CmncbtwYDqmlF2tt/+19ir8YHOoaibQyEuzNqwRTKAMegds9v2Mxaos5nmNzkfovDgAI+2hIyDnqfflThxg91Pg8Ma2ETxEJNBf4fm3FSXP/uJ092vprSZKrUt7BUC6Ooj8XWdO0qG9P4GELf5KKMkvxDkg6Lj0asfQvT0gYoVAxsyb2bvvkZfuWqvAgKgzqbpdIJe7/lCd0QI1PyisSbAz33UTHKqFG+6og==; 5:2vBjZTQbjJrZdcCjsLPE4IAB71WYVntTfQhaAn/OsMkJpVU7goN1t8hSz8xWMfjHDygSc8sh7531IQiXlyQaw+J8zS7kXWnqVgcy0ac0FI8cooRIgwkZ2RxHFGiWhymvDKz+AgNFwcMvgrULVs/2Bpy7/u2u3TtmNFgiM4xeEA4=; 7:lywiXaPjROdbVQXk337fDByC2hemWmv7XFmwUfWyDMJYNfn2iBdB8GEjUyjUG5xVLb7kSeoQdQDBVFLrQ5JWwxN2z7g5V8R9huaKzeNnAvwMmbVggO2RWcFnXCpkP1c7b42njubpf09w32E+Cbua34j1U5vOYD5+uW/OMnezg7aAFTM1h30pUXW/TxnWzN6GioG6BpI7poCABkWSMN9aagzgxJt/b03L/kCKQrNWdWBkIFlonHH4OJARVCl+GL/F
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 310bac9a-2a4f-40e4-9725-08d5eaa2a50a
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989117)(5600053)(711020)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(48565401081)(2017052603328)(7193020); SRVR:VI1PR0701MB2767;
x-ms-traffictypediagnostic: VI1PR0701MB2767:
x-microsoft-antispam-prvs: <VI1PR0701MB2767197B84EA5CDC8030453E915E0@VI1PR0701MB2767.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(788757137089)(21532816269658);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(3231311)(11241501184)(806099)(944501410)(52105095)(93006095)(93001095)(3002001)(10201501046)(6055026)(149027)(150027)(6041310)(20161123562045)(20161123564045)(20161123560045)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011)(7699016); SRVR:VI1PR0701MB2767; BCL:0; PCL:0; RULEID:; SRVR:VI1PR0701MB2767;
x-forefront-prvs: 07349BFAD2
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(979002)(39860400002)(396003)(136003)(346002)(376002)(366004)(199004)(13464003)(189003)(256004)(106356001)(26005)(7696005)(102836004)(76176011)(53546011)(478600001)(186003)(99286004)(6506007)(9686003)(476003)(11346002)(486006)(446003)(68736007)(229853002)(55016002)(6246003)(6306002)(6436002)(97736004)(86362001)(74316002)(14454004)(3846002)(6116002)(2906002)(25786009)(33656002)(105586002)(966005)(53936002)(5250100002)(7736002)(5660300001)(110136005)(81156014)(316002)(8676002)(81166006)(2900100001)(66066001)(1941001)(305945005)(8936002)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR0701MB2767; H:VI1PR0701MB2351.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: nokia.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: XO3SG6SHqTNPw0UYxeR7PI6reU1LmjeaEEP9kNiPaJU3FzL1OYgvcgJYev8ZV2dFZkxwylSFXCx4Y3rh638uXPdXfahKAmX5lwtGx0tvef8SZbOsX9tLnL2HxX8z9evqPe5Cod7PRVpeTFwRjEYa2FDUp3KtpR0rGLsD0uUNLZWLS9mwiDj7Ipyn29WZ2C+F1EATEbabTVa41DSOBD0nEOLen05pg7877pTxywOVxJv6EvVKW1wPSyaMm7VTVCgeWCyuyoKzYYSo3XVGAEt90q3nSF/OHMucyw0l0OFVvthJqQbKxTGWYbyX5jdCPbAC8iQV2o8MugtsHEpxyo1LeVfPL9WTCH67aNwWn3pVc9wX+RIJci/yozS97z6ABMbBw6l4VrhoYsV5KsplzfRV+g==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 310bac9a-2a4f-40e4-9725-08d5eaa2a50a
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Jul 2018 22:31:01.6498 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0701MB2767
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/Epa5uy8a-6Rflygt786amtNO0Ys>
Subject: Re: [Bier] Comment on draft-hj-bier-mldp-signaling-00
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.27
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: Sun, 15 Jul 2018 22:31:09 -0000

Hi Eric

Thanks for feedback, we did look at that RFC. 
Couple of thoughts:
1.	This RFC is non-segmented mLDP, we felt segmentation (terminating LDP signaling at BFIR/BFER) and stitching between BIER and MLDP will provide better scaling. i.e the draft is suggesting single label presenting the P2MP LSP in bier domain and stitching vs the rfc will mean  a unique label presenting each BFIR and it is non-segmented. 
2.	There is still the issue of pushing P2MP MPLS over BIER and finding the BFERs. i.e. BFIR still needs to track the BFERs as per this draft.
3.	We are not trying to connect the 2 LDP domains from signaling point of view, we are just trying to signal the FEC and stitch, just like draft-ietf-bier-pim-signaling we are open how to signal through BIER domain. 

The biggest thing we are trying to accomplish is to stitch 2 P2MP LSP in 2 disconnected LDP domains over BIER domain without any (software/HW) impact to the LDP domain and as always we are open to suggestion...

Regards

Hooman
  

-----Original Message-----
From: BIER [mailto:bier-bounces@ietf.org] On Behalf Of Eric C Rosen
Sent: Tuesday, July 10, 2018 5:12 PM
To: BIER WG <bier@ietf.org>
Subject: [Bier] Comment on draft-hj-bier-mldp-signaling-00

I note that the problem described in draft-hj-bier-mldp-signaling is essentially the same problem that is solved by RFC 7060 ("Using mLDP on Targeted LDP Sessions").  Section 6 of that RFC discusses the use of multicast tunneling to transport packets from an ingress LDP edge node to a set of egress LDP edge nodes, and applying it to BIER is straightforward.

RFC 7060 does require targeted LDP sessions between edge nodes. 
Draft-hj-bier-mldp-signaling proposes to replace those LDP sessions either by using an SDN controller, or by encapsulating an mLDP packet in a BIER packet (analogous to what is done with PIM in draft-ietf-bier-pim-signaling).  There are a couple of issues with the "encapsulate mLDP packets in BIER" option:

- There is no such thing as an "mLDP packet".  You'd need to extract mLDP messages from the TCP stream, and you need to say exactly which messages need to be forwarded and which don't.

- If you are trying to connect two LDP sessions by sending mLDP messages in datagrams, you will have a big problem if one of those datagrams gets lost.  Or if one of the edge nodes reboots.

Eliminating the TCP-based LDP signaling protocol by inventing a new datagram-based LDP signaling protocol is probably not a simplification.

_______________________________________________
BIER mailing list
BIER@ietf.org
https://www.ietf.org/mailman/listinfo/bier

v2.23.0 | Report a Bug | By Email