Re: [Bier] BIER WG, Call For Agenda, Montreal IETF 105

"Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net> Fri, 12 July 2019 20:53 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 7657A1201DC; Fri, 12 Jul 2019 13:53:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, URIBL_BLOCKED=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 I2eiD_bMHzP0; Fri, 12 Jul 2019 13:53:17 -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 A0232120167; Fri, 12 Jul 2019 13:53:17 -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 x6CKn2U6022673; Fri, 12 Jul 2019 13:53:13 -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=8I0x8yyNiUUK3AptZeODB24b2ss5E6R0jTWWCcnvT1U=; b=WqLIsetDtTyyanusBgKNFRYUPu0oQZCbqQvP0+5KuDYR4W29fXI5AW0V03okWqjEPDR+ wsYvmymZ2CFJsIAPZqa1oSEObqOLtDG8PhlPj+xk13b6Np4NbYxIrj4h8AeLHjOQCUZQ KUj+1eQUxx8XLWhs0K0Is0KTGdVGLX+S8PL24k7/qdPwwRtEej5dl6Zv1StgTnqrU2LB xZ7j33ENbnZYJUwBqIfO79+wHdmkl6wVRC1QUbdXaRQOFbQDi+CCrGFj6LxhrIhnbSuJ pfJtfdSE6NACHdJcKQFWfEqbUf63aPR0IeLNguV1O0c+nkpjBUJTY8IRsJlh+Vo7mg0x jg==
Received: from nam02-bl2-obe.outbound.protection.outlook.com (mail-bl2nam02lp2050.outbound.protection.outlook.com [104.47.38.50]) by mx0a-00273201.pphosted.com with ESMTP id 2tq1a3g0xc-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 12 Jul 2019 13:53:13 -0700
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=gzvDlUOHxqch3URi2Q2rXP6NZgijhmi6u27ibpllwVjOpthgo8wQM5HCYn+YZ+ex3mHUxU0wX8wcYMxVKtYMJTRdtxrZq4o5mM2OywKnqF2Y/ahQT0cr38xYPJllUo+lBhurTTOF6DWortgkFg0L6dKNILmvAc2on6SkUGdnviO7WYn9KFrfnyNu/+3BEZpnHdYS0sST8ZRJUwhIWW8Lq9oNK7+sgZO42Wlo5znKDHp7EzVvAb5NvNJzey5rLKkz0RnXuBOWgIjzrmKLRHd+X1gNqfAdFQ2MmzeTbpWZ03dkVFDtk6kYv7E5L+cIs82y3Jlpwn8I6vobimcvn4HsOw==
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=8I0x8yyNiUUK3AptZeODB24b2ss5E6R0jTWWCcnvT1U=; b=oZF2QL7OV3KNvEeQYczzQ+5B1xriM53SfHoC9TCLMl6J3MMF3l3LfMr3DDyD0NiVx6u49yBjmufPQV5FOgnXleH/ECbAnyrWT38INAgRpfgIa3FKm/Ds9et/ZVpUo1WlOgLz8KGHObUhMHdJLLvNEhrDYwtYrudJFDPssct2j543D4dSG9TyUjSPXDLiWoP1P9H1DcXu9DhBB9/tRDFgJ7PbB8Lx5yriwcDpO15S/3NH3564e5LpMukZiKfZVM39Zwcz7eUhQhA0BFn+lxzlQr9/1ZV+wAgorTuGtldOBKQFejDTBoPXQuNHOBkpJtOdam61yD7kYAk8eh1ORgBHYQ==
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 DM5PR05MB3417.namprd05.prod.outlook.com (10.174.240.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2094.6; Fri, 12 Jul 2019 20:53:10 +0000
Received: from DM5PR05MB3548.namprd05.prod.outlook.com ([fe80::c890:e1c9:8d87:8d5f]) by DM5PR05MB3548.namprd05.prod.outlook.com ([fe80::c890:e1c9:8d87:8d5f%6]) with mapi id 15.20.2073.008; Fri, 12 Jul 2019 20:53:10 +0000
From: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
To: Xiejingrong <xiejingrong@huawei.com>, "gjshep@gmail.com" <gjshep@gmail.com>, BIER WG <bier@ietf.org>
CC: "'draft-xie-bier-ipv6-mvpn@ietf.org'" <draft-xie-bier-ipv6-mvpn@ietf.org>, "draft-xie-bier-ipv6-isis-extension@ietf.org" <draft-xie-bier-ipv6-isis-extension@ietf.org>, "draft-geng-bier-ipv6-inter-domain@ietf.org" <draft-geng-bier-ipv6-inter-domain@ietf.org>, "draft-xie-bier-ipv6-encapsulation@ietf.org" <draft-xie-bier-ipv6-encapsulation@ietf.org>
Thread-Topic: [Bier] BIER WG, Call For Agenda, Montreal IETF 105
Thread-Index: AQHVNcSZBwZEncl0nUyrr4r1gwptmqbBgBoAgAXukNA=
Content-Class:
Date: Fri, 12 Jul 2019 20:53:10 +0000
Message-ID: <DM5PR05MB3548731B6AE229EA12451E21D4F20@DM5PR05MB3548.namprd05.prod.outlook.com>
References: <CABFReBo=+68gyhsFwYktcc1Mr7zkax2MiYFCTSC5osod48x3Jw@mail.gmail.com> <16253F7987E4F346823E305D08F9115AAB8DC2D1@nkgeml514-mbx.china.huawei.com>
In-Reply-To: <16253F7987E4F346823E305D08F9115AAB8DC2D1@nkgeml514-mbx.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-12T20:53:07.0290746Z; 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=fc0f7f6e-6a0b-43d3-9a3d-fc2d9329e5a5; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Extended_MSFT_Method=Automatic
x-originating-ip: [66.129.241.14]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 25174e72-59d0-46bf-9a9b-08d7070af2fe
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600148)(711020)(4605104)(1401327)(4618075)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:DM5PR05MB3417;
x-ms-traffictypediagnostic: DM5PR05MB3417:
x-microsoft-antispam-prvs: <DM5PR05MB341741DA398C3BDD74C88C49D4F20@DM5PR05MB3417.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 00963989E5
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(136003)(366004)(376002)(396003)(346002)(39860400002)(25584004)(199004)(189003)(966005)(99286004)(53946003)(55016002)(6306002)(52536014)(6436002)(8936002)(6246003)(66066001)(86362001)(4326008)(33656002)(54906003)(110136005)(316002)(71200400001)(3846002)(229853002)(5660300002)(53936002)(71190400001)(2906002)(2501003)(6116002)(9686003)(81166006)(81156014)(25786009)(8676002)(14454004)(66446008)(66556008)(7736002)(66946007)(64756008)(305945005)(256004)(30864003)(76116006)(14444005)(68736007)(478600001)(7696005)(102836004)(186003)(446003)(6506007)(26005)(561944003)(66476007)(76176011)(486006)(11346002)(476003)(74316002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR05MB3417; 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: dTMU5lQXiDjNIkFSwDalgwnJ1uS9JYk73lCoJhHKLfsb7R49abyNonvThHQADDmmoB0tj0KkmlOV7FB3camXifGgVFDe6Vx2keMe35wqDAR87IsZcPrvoOClIeH2qLmKsEaRXe11jL+YhNcEAHJZyDSAFDpG51cqgC/E5oA1eJR4PxZ7C7RK6AvCJ3wm5QjDdzt6eUpG1pfB/YKGAl6Y++LqMyEj3ywbl+C7YRPcLdj4IrvflISiZEhZmXxZhLEaEK91dCYyYox7PJuZq/4e7tPVF3Hdb+6E0SVPJJLuSDbPofLPvxTfZpBklsMWJ/Vw1R/5icwAL+GyfifEL4ncrGhLM2N9QLHFNfICSUXBe/NzFEnXydGhUVa+hE24iJEG0DQk+O7B8tE7ZOEfETvRErEgFWK8R33JgMbU2bSi1bs=
Content-Type: multipart/alternative; boundary="_000_DM5PR05MB3548731B6AE229EA12451E21D4F20DM5PR05MB3548namp_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 25174e72-59d0-46bf-9a9b-08d7070af2fe
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Jul 2019 20:53:10.3014 (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: DM5PR05MB3417
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-07-12_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-1810050000 definitions=main-1907120213
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/5UdrqwIZ5kmevb0-72biWUbKxgo>
Subject: Re: [Bier] BIER WG, Call For Agenda, Montreal IETF 105
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: Fri, 12 Jul 2019 20:53:22 -0000

Hi Jingrong, Liang,

I have some questions and comments on two of the drafts.

draft-xie-bier-ipv6-encapsulation-02

-       Use of BIER multicast address FF0X::AB37 does not seem right to me. For example, on a LAN you can’t multicast BIER packets to multiple downstream BFRs – individual copies (with different BitString) must be unicast to those downstream BFRs.
-       Assuming that we agree that a unicast DA address must be used. What’s the rational of “Source Address field in the IPv6 header MUST be a routable IPv6 unicast address of the BFIR in any case”? Since the IPv6 header is only the outer encapsulation to get a packet from BFR1 to BFR2, why would you want to put the BFIR’s address in the outer encapsulation? If you could make both SA/DA of the IPv6 header to be the original SA/DA of the payload it may make some sense, but obviously you can’t do that.
-       With the above, I don’t see a real difference between this proposal and draft-zhang-bier-bierin6-03 – it’s just whether the BIER header is in the destination option or in the “payload” part of the IPv6 packet. Can you explain the pros and cons of two?

draft-geng-bier-ipv6-inter-domain-00

-       Can you elaborate the following?
   Note: Use of the IPv6 address configured on PE1 to identify an MVPN
   instance can eliminate the need for BFR-id configuration on PE1x,
   which otherwise has to be configured from the space of a sub-domain.
-       For the “peering multicast”, how many BIER sub-domain do you have?
-       What’s the real difference between “hierarchical multicast” and “peering multicast”, once you take away the color and MVPN aspects that I believe are orthogonal here?
-       What’s the significance of “inter-domain” here, that requires this new draft?
-       What’s the uniqueness of IPv6 here?

Thanks!
Jeffrey

From: BIER <bier-bounces@ietf.org> On Behalf Of Xiejingrong
Sent: Monday, July 8, 2019 9:30 PM
To: gjshep@gmail.com; BIER WG <bier@ietf.org>
Cc: 'draft-xie-bier-ipv6-mvpn@ietf.org' <draft-xie-bier-ipv6-mvpn@ietf.org>; draft-xie-bier-ipv6-isis-extension@ietf.org; draft-geng-bier-ipv6-inter-domain@ietf.org; draft-xie-bier-ipv6-encapsulation@ietf.org
Subject: Re: [Bier] BIER WG, Call For Agenda, Montreal IETF 105

We’d like to request 35-40 minutes for the presentation of the following BIERv6 drafts.  I will be the speaker (may have some adjustment before the session).

BIERv6 Encapsulation  //  draft-xie-bier-ipv6-encapsulation-02, 15min
BIERv6 via IS-IS  //  draft-xie-bier-ipv6-isis-extension-00  10min
MVPN using BIERv6  //  draft-xie-bier-ipv6-mvpn-01            5min
Inter-domain Multicast Deployment using BIERv6  //  draft-geng-bier-ipv6-inter-domain-00  10min

Thanks
Jingrong on behalf of the authors

From: BIER [mailto:bier-bounces@ietf.org] On Behalf Of Greg Shepherd
Sent: Tuesday, July 09, 2019 3:37 AM
To: BIER WG <bier@ietf.org<mailto:bier@ietf.org>>
Subject: [Bier] BIER WG, Call For Agenda, Montreal IETF 105

Please send agenda items with title, draft, speaker name, and requested time to this thread.

Thanks,
Shep
(chairs)

Juniper Business Use Only