IETF Logo Mail Archive

Re: [babel] About BIER in Babel

Antoni Przygienda <prz@juniper.net> Tue, 28 March 2017 23:31 UTC

Return-Path: <prz@juniper.net>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 964A2127871 for <babel@ietfa.amsl.com>; Tue, 28 Mar 2017 16:31:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level:
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=junipernetworks.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 5_hA7eY0nZ17 for <babel@ietfa.amsl.com>; Tue, 28 Mar 2017 16:31:34 -0700 (PDT)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0129.outbound.protection.outlook.com [104.47.38.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53AB0129456 for <babel@ietf.org>; Tue, 28 Mar 2017 16:31:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junipernetworks.onmicrosoft.com; s=selector1-juniper-net; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=PapmmoEc1Kv8hAmh9RCqVSEwLeV4WfRpFPlg66P3jUw=; b=OjjBHaP7OCKWmuNVPu4IiqF8CSFv8ZVSjTWTpqExlppKPWIUJsdYSEiMEHsSVWp2oKrsiENCw2AX+dD6muWGhkcWkjbvgZaGa+H01AsR5anqd/At9jeF2YehP+LJ9tPEnm3k0D3oPczpUPuKftXc2N3oJfFCZfT9yFPhz6BgC0M=
Received: from DM2PR0501MB1438.namprd05.prod.outlook.com (10.161.224.148) by DM2PR0501MB1437.namprd05.prod.outlook.com (10.161.224.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1005.2; Tue, 28 Mar 2017 23:31:30 +0000
Received: from DM2PR0501MB1438.namprd05.prod.outlook.com ([10.161.224.148]) by DM2PR0501MB1438.namprd05.prod.outlook.com ([10.161.224.148]) with mapi id 15.01.1005.009; Tue, 28 Mar 2017 23:31:30 +0000
From: Antoni Przygienda <prz@juniper.net>
To: Zhang Z <zzhang_ietf@hotmail.com>
CC: Juliusz Chroboczek <jch@irif.fr>, "zhang.zheng@zte.com.cn" <zhang.zheng@zte.com.cn>, "pierre.pfister@darou.fr" <pierre.pfister@darou.fr>, Greg Shepherd <gjshep@gmail.com>, "babel@ietf.org" <babel@ietf.org>
Thread-Topic: [babel] About BIER in Babel
Thread-Index: AQHSqASE+FBqZZhPnk6jNtau8gv99KGq4UBygAAFjoA=
Date: Tue, 28 Mar 2017 23:31:29 +0000
Message-ID: <2F23101F-3169-468C-B200-1AA69E5820EC@juniper.net>
References: <87shlxyvqe.wl-jch@irif.fr> <PS1PR03MB15625DDBBDF79080DB3E811A8E320@PS1PR03MB1562.apcprd03.prod.outlook.com>
In-Reply-To: <PS1PR03MB15625DDBBDF79080DB3E811A8E320@PS1PR03MB1562.apcprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
authentication-results: hotmail.com; dkim=none (message not signed) header.d=none;hotmail.com; dmarc=none action=none header.from=juniper.net;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [66.129.239.12]
x-microsoft-exchange-diagnostics: 1; DM2PR0501MB1437; 7:ThFAuDYNVAs8m2lDfnJOS+sYDTUzsiN9N35goLfLUmzW1xj52Hgobk1YKRDGCiAYawbwalq2DXBUSPwv4CjmRx39Hh2Db0Vlo8qboBYzVHKNixb3U/6tt8yjTgzXHwuF6fW9t+n9FSrqZ0982Rt/MabsijP+XO7A60HdkxuNxKHGAJMdMogd/V2LWK9XDf3Q3JIJq46UQPgH2y9kJSyyNFr+q1LWLaDWLXud07/C6ZUtnF3a35CirDz/LOmi/qMY/SF+wSkZijKQf/p6NST1KvnG9aC78DjbpogSjhTaPAIzbFXHQ5mHsF/w9DFN0wBoZek4KclGYHoEZID7/ukjVA==
x-ms-office365-filtering-correlation-id: 8a295ea4-5d6b-449b-d673-08d476328fe9
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423067)(201703031133073)(201702281549067); SRVR:DM2PR0501MB1437;
x-microsoft-antispam-prvs: <DM2PR0501MB1437D367DED1F15D17C92F0AAC320@DM2PR0501MB1437.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(194151415913766);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(102415395)(6040442)(601004)(2401047)(5005006)(8121501046)(10201501046)(93006033)(93001033)(3002001)(6055026)(6041248)(201703131423067)(201703031522067)(201702281528067)(201703011903067)(201703061421067)(20161123564025)(20161123560025)(20161123558025)(20161123562025)(20161123555025)(6072148); SRVR:DM2PR0501MB1437; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0501MB1437;
x-forefront-prvs: 0260457E99
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39400400002)(39410400002)(39850400002)(39450400003)(39860400002)(39840400002)(377454003)(24454002)(110136004)(83716003)(189998001)(36756003)(38730400002)(6246003)(39060400002)(54896002)(86362001)(6306002)(4326008)(6512007)(54906002)(236005)(99286003)(606005)(53936002)(76176999)(6436002)(6506006)(6486002)(50986999)(99936001)(54356999)(33656002)(82746002)(77096006)(8676002)(81166006)(6916009)(66066001)(7736002)(2950100002)(2906002)(7906003)(8936002)(3846002)(25786009)(122556002)(3660700001)(229853002)(2900100001)(102836003)(6116002)(3280700002)(5660300001)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR0501MB1437; H:DM2PR0501MB1438.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; boundary="Apple-Mail=_8D44A7E9-8DE7-44F6-9059-4C90FA23621D"; protocol="application/pkcs7-signature"; micalg="sha1"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Mar 2017 23:31:29.8609 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0501MB1437
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/Rs50vPN5t75IP3VwQOOnq-hWq0I>
Subject: Re: [babel] About BIER in Babel
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Mar 2017 23:31:37 -0000

> On Mar 28, 2017, at 6:14 PM, Zhang Z <zzhang_ietf@hotmail.com> wrote:
> 
>  Hi Juliusz and all,
> At first I must apology about the misunderstanding caused by the two drafts. One is “draft-zhang-bier-babel-extensions-00”, it was presented in Seoul meeting; it is the BIER Routing underlay technology. The other one is “draft-zhang-pim-babel-ext-02”, it was presented in this meeting. It is multicast flow overlay technology. The two drafts focus on different aspect of BIER technology. And the two drafts are independent though we can use them together. The man who is not familiar with BIER will be confused about it. The first draft “draft-zhang-bier-babel-extensions-00” had been discussed in BIER working group and many people thought that it is worth implemented. The second draft “draft-zhang-pim-babel-ext-02” is just an idea for multicast flow overlay. And the implementation that we discussed today is “draft-zhang-bier-babel-extensions-00”.
> I suggest strongly that the draft “draft-ietf-bier-architecture-05” should be read first. You will know the meaning of Routing underlay/ BIER layer/ Multicast Flow Overlay. The three layers are focus on different aspect of BIER technology. Routing underlay is used to transfer BFR-id corresponding information. There are OSPF/ ISIS/ BGP BIER extension in BIER working group. You can find them through the link “https://tools.ietf.org/wg/bier/ <https://tools.ietf.org/wg/bier/>”. In fact, the draft “draft-zhang-bier-babel-extensions-00” also belongs to Routing underlay layer. And this draft is worth implemented first.

+ 10E3

> The draft “draft-zhang-pim-babel-ext-02” belongs to Multicast Flow Overlay. This layer is used to transfer particular multicast flow information. And there is also a draft “draft-pfister-bier-mld-03” that is used to solve it. And the “draft-pfister-bier-mld-03” is the function that we call MLD in abbreviation.
> So, you will see that we can use “draft-zhang-bier-babel-extensions-00” and “draft-pfister-bier-mld-03” together to solve the Routing Underlay and Multicast Flow Overlay. It is Babel + MLD solution. And many people include me think that it is a good way to achieve the multicast deployment.
> The way that I said use one protocol to solve multicast problem is that we use “draft-zhang-bier-babel-extensions-00” and “draft-zhang-pim-babel-ext-02” at the same time. In this situation we only use one protocol Babel to solve Routing underlay and Multicast flow overlay. This function is just an idea. And it means nothing if there is no situation that we can only use one protocol to deploy multicast.

overlays will be plentiful and they will be a continuum between simplicity and scale … 

> In a word, we should consider the implementation of “draft-zhang-bier-babel-extensions-00”. The BIER forwarding plane software had also been implemented by ZTE, and I think Cisco does it also. So at first it should be considered that how to merge Babel protocol and BIER forwarding software together. And then implement “draft-zhang-bier-babel-extensions-00”.

There is an interesting ongoing discussion about Linux kernel software implementation to some extent/socket APIs … 

— tony

v2.23.0 | Report a Bug | By Email