IETF Logo Mail Archive

Re: [Bier] The offline talk about BIERin6 and BIER-ipv6-requirements drafts

"Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net> Mon, 29 July 2019 13:25 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 8FA7E1200E7; Mon, 29 Jul 2019 06:25:51 -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, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, 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 FIPlvMaz1x7S; Mon, 29 Jul 2019 06:25:49 -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 8F091120124; Mon, 29 Jul 2019 06:25:46 -0700 (PDT)
Received: from pps.filterd (m0108159.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x6TDJRjl020258; Mon, 29 Jul 2019 06:25: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=HZZX22aQroxwexbpNkrKlqNaZWvT4MJOX7OzxhLWEMc=; b=T+ibgNKalxeNFsGq9TwJKshiLvsYr81wtp0fA5R14MhvV4X05y+7v4UKulY7E7DatxyB EDJ04NvYkQ4OHnsF5cVQ25WYnFjMLfQZFKDIF9egMxXoQ8Jrn42GMru7o3IIqioiOumX STEviy4Fg44V+uM0jsYFoMnl5EABGyG7txrVaA7Sja8laa475u+VXkKG0xwlSz3PFI2X WExJU7hHfjfbcaF9GkWa3fOWVau17mD3wtzzzi4EJr9i5wtQPQoGez00+aXAWl/nQb/E 92xzEkfaqMG4/5oQoRdKfqrb0npukZvlpNfUD0It55Cl4ixXPnVG7Q8d24Rx/g+fu5hG cQ==
Received: from nam05-by2-obe.outbound.protection.outlook.com (mail-by2nam05lp2053.outbound.protection.outlook.com [104.47.50.53]) by mx0a-00273201.pphosted.com with ESMTP id 2u1x930cen-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 29 Jul 2019 06:25:32 -0700
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=IInKk0QZvJfJBcC9wqGurUjZ06bfMIjwwoCPmQFRfpIX5ztQq83BaQu4I24TnyeDYB9+Yzi4M5U6KFC7umnL06u9p2AzGFBKrEhLaQwsaEcuBFC/ackJ93WhXhD7myHPYLgfulUwQeVvk6Ejl4FgyHEcJSPs8TdQOnGv0XndSm+SuC4axO1I7O5hcqFN6pFYOYfzXKGFETUiu1zLvSw2CQbveJKV3C59UyXD1JJXPVxbH2BEiwzZXdm1W2a7Arn8M9R010/igDYPsuprtCKFSPE6lFw6i4Vas6yx6t/wvK5JCVqSfa1C4czB/cNRauhocCoke9Z5ntIepmAfcAXvXQ==
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-SenderADCheck; bh=HZZX22aQroxwexbpNkrKlqNaZWvT4MJOX7OzxhLWEMc=; b=SVVDwFqcPTNtGnaf0qOc2IiPtvvCLCdWvB2MP/Sq/PuSyKaU0IvMDooN7vF61eQOM12dW1ioDcfdDp+igZKwUVI6QNbXSqXQZQfXsWCtR5ErpqIKqGnTUJOq6oHq3rMnSEN6zyQ/G7GfMqm/mkYew7FPWIfz+ZGClEumXGEhOLuYOW9UJ0CM8LCzjRd0cyoGDTwthdn3ywFQIkbEkWG2oUzROWqqO5bIWwn7qQwOYdiWRL1bOnjNf8Z+tsPsRoQU/4h/LedKX/1Vu9P0wEDXbu+Mx5C4p5m9QWfsnmnI1aYgDBu7NyMOASgxi3G5+Zm/YAjOYM+sROFm6UpKmROWfA==
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
Received: from DM5PR05MB3548.namprd05.prod.outlook.com (10.174.242.153) by DM5PR05MB2923.namprd05.prod.outlook.com (10.168.176.135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2136.10; Mon, 29 Jul 2019 13:25:31 +0000
Received: from DM5PR05MB3548.namprd05.prod.outlook.com ([fe80::18d2:ef12:6593:9e2a]) by DM5PR05MB3548.namprd05.prod.outlook.com ([fe80::18d2:ef12:6593:9e2a%7]) with mapi id 15.20.2136.010; Mon, 29 Jul 2019 13:25:31 +0000
From: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
To: Xiejingrong <xiejingrong@huawei.com>, BIER WG <bier@ietf.org>
CC: "draft-ietf-bier-ipv6-requirements@ietf.org" <draft-ietf-bier-ipv6-requirements@ietf.org>, "draft-zhang-bier-bierin6@ietf.org" <draft-zhang-bier-bierin6@ietf.org>
Thread-Topic: The offline talk about BIERin6 and BIER-ipv6-requirements drafts
Thread-Index: AdVEbDdfSasS0zeXTT+PUAHUwHtauQBpKyAA
Content-Class:
Date: Mon, 29 Jul 2019 13:25:30 +0000
Message-ID: <DM5PR05MB35486224332EB2DDD02E87B3D4DD0@DM5PR05MB3548.namprd05.prod.outlook.com>
References: <16253F7987E4F346823E305D08F9115AAB90D974@nkgeml514-mbs.china.huawei.com>
In-Reply-To: <16253F7987E4F346823E305D08F9115AAB90D974@nkgeml514-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
dlp-product: dlpe-windows
dlp-version: 11.2.0.14
dlp-reaction: no-action
msip_labels: MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Enabled=True; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SiteId=bea78b3c-4cdb-4130-854a-1d193232e5f4; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Owner=zzhang@juniper.net; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SetDate=2019-07-29T13:25:32.4601080Z; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Name=Juniper Business Use Only; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Application=Microsoft Azure Information Protection; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_ActionId=df53777c-e2ee-4503-938d-5a1a86099de0; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Extended_MSFT_Method=Automatic
x-originating-ip: [98.217.112.215]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 527b7678-8193-4d1d-56f2-08d714283a94
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(4618075)(2017052603328)(7193020); SRVR:DM5PR05MB2923;
x-ms-traffictypediagnostic: DM5PR05MB2923:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <DM5PR05MB2923FFF662D5630179B9F05ED4DD0@DM5PR05MB2923.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7219;
x-forefront-prvs: 01136D2D90
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(346002)(136003)(366004)(39860400002)(396003)(376002)(199004)(189003)(54906003)(229853002)(74316002)(7696005)(9686003)(54896002)(6306002)(68736007)(71190400001)(71200400001)(7736002)(110136005)(316002)(9326002)(102836004)(81166006)(66066001)(81156014)(6506007)(53546011)(14454004)(6436002)(76176011)(33656002)(478600001)(5660300002)(8676002)(790700001)(2906002)(8936002)(52536014)(186003)(25786009)(486006)(256004)(66476007)(64756008)(76116006)(66446008)(86362001)(66556008)(66946007)(6246003)(4326008)(476003)(446003)(53936002)(11346002)(55016002)(99286004)(3846002)(26005)(6116002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR05MB2923; H:DM5PR05MB3548.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-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 1w6v6FynSDAhnO5nwsjsqnoObvP3KGOukTJZZouhSCTQctRMA7PtoOxOIzps7I6dg99QpDIQNjq3HZnUOUJndghiLCZIXCIqGbMuBkHiEmjdSN1ObjYW6mWuRLE1kznmIKIn0IPo7cEUIm3i+7v6jyQI46hpO0J6un5Hk7ZsubXuKxPSySjrCIIp6tDVUbKQJFScHI6qF5JDCCMCY+Wtr7HjWitERDzopAjpHYBRWPA3xj/uMvTM5+hILhekaK4ypDoI8kkSRSwZ35M5yLCQMONe4x0t6frbt+85kZ9fC1OPiG9FLgJ3HzYyfX4FD1gFaq6rH+/K7xIBEYEYzHEKnvkf/2aIWY/GsH5vJ4tOEVvjhMHpcKklnlTCuvoiT4Wjbtps0G6Cjkq2fcYKvIJMYfUUFJxCTQexVubIT2Ff0Qw=
Content-Type: multipart/alternative; boundary="_000_DM5PR05MB35486224332EB2DDD02E87B3D4DD0DM5PR05MB3548namp_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 527b7678-8193-4d1d-56f2-08d714283a94
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Jul 2019 13:25:30.9612 (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: zzhang@juniper.net
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR05MB2923
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-07-29_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=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1907290155
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/RvqN-oNLYcQYIlFXP9HCfeVIOAg>
Subject: Re: [Bier] The offline talk about BIERin6 and BIER-ipv6-requirements drafts
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, 29 Jul 2019 13:25:52 -0000

Hi Jingrong,

We emphasized several times it is not layer-4, just like you would not consider IPinIP/IPinWhatever as layer-4.

Jeffrey



Juniper Business Use Only
From: BIER <bier-bounces@ietf.org> On Behalf Of Xiejingrong
Sent: Saturday, July 27, 2019 7:24 AM
To: BIER WG <bier@ietf.org>
Cc: draft-ietf-bier-ipv6-requirements@ietf.org; draft-zhang-bier-bierin6@ietf.org
Subject: [Bier] The offline talk about BIERin6 and BIER-ipv6-requirements drafts

Thanks Jeffrey and Sandy for the patient talk offline about the BIERin6 and BIER-ipv6-requirements yesterday.
I summarized the talk afterwards, and have the following points.

(1) BIERin6 is a Layer-4 solution, which has its special advantages and disadvantages in different scenarios, comparing to Layer-3 solution (the solution using IPv6 Extension Header).

(2) The <bier-ipv6-requirements> can be more inclusive to include Layer-3, Layer-4, and Layer-5 solution, so that many of the interests, Layer-3/4/5, in the WG can be all considered.

What's your opinion ?

Thanks
Jingrong

v2.23.0 | Report a Bug | By Email