Re: [Bier] I-D Action: draft-ietf-bier-te-isis-01.txt

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Thu, 04 August 2022 04:20 UTC

Return-Path: <ginsberg@cisco.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 16E29C14F735 for <bier@ietfa.amsl.com>; Wed, 3 Aug 2022 21:20:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.596
X-Spam-Level:
X-Spam-Status: No, score=-14.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_NONE=0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=mjhg2/6n; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=O9o40k3X
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4hJKIbWCZDNr for <bier@ietfa.amsl.com>; Wed, 3 Aug 2022 21:20:19 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A60AC14F607 for <bier@ietf.org>; Wed, 3 Aug 2022 21:20:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=107724; q=dns/txt; s=iport; t=1659586819; x=1660796419; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=S9l0PMSj2B9wtvQfgdBMVQv9pLAm0WlR2Ib6NqvAaFo=; b=mjhg2/6n8EiK5eC3Rz+LWR3p2P/G/YXfc/FjH0bFwqQH2Tals1J6gJT0 6MUJatKfifEZrb0H3He5nlQJXlM5vd5tOZOzisQwaEu8HxzW9Dd75bQZD eZ4PTkBcXGuqUJxFaKj/O+6zslyyBoUA8sM8stkfGy7du66AMm1PXL5Dz k=;
X-IPAS-Result: A0BMAADPR+ti/4kNJK1QChwBAQEBAQEHAQESAQEEBAEBgXsHAQELAYEgMVIHeAJaOkWEToNMA4RQX4ULgwIDm02BLBSBEQNPBQMIAQEBDQEBLAEKCwQBAYIpgl0CFoRgAiU0CQ4BAgQBAQEBAwIDAQEBAQEBAwEBBQEBAQIBBwSBCROFaA2GQgEBAQECAQEBEAgBCAoTAQEsCwEEBwQCAQYCEQMBAQEeAwEGAwICAiULFAkIAgQBDQUIGoJWBAKCDlcDDSUDAQ+NaY85AYE/AoofeoExgQGCCAEBBgQEgU1BgwIDFYI4AwaBPQGDG4RMAQGDCYQzJxyBSUSBFAFDgWaBAT6CYgEBAgEXgREBBwQHAQccFQkGB4MpN4IugRyHHA0jgwiBLIp6BzcDRR5CAwtNBQgJFxIQEAIEERoLBgMWPwkCBA4DQAgNAxEEAw8YCRIIEAQGAzEMJQsDBQ8MAQYDBgUDAQMbAxQDBSQHAxwPIw0NBBgHHQMDBSUDAgIbBwICAwIGFQYCAhg2OQgECAQrIw8FAgcvBQQQHwIeBAUGEQgCFgIGBAQEBBYCEAgCCCcXBxMzGQEFWRAJIRYGDhoKBgUGEwMgRyYFRQ8oMzU8IgkfGwqBEioJIhUDBAQDAgYTAwMiAhAuMQMVBikTEi0JKnUJAgMiaQUDAwQoLgMJHgQcBwkmLDABlSeCC4ERCRFPDActECYEGxQkFAMvCQwCCRUKEz8HVAs6kg0Pg1SKEESDRZtlgTEKg1GLJJUUFYN2jESYLZZ+II0YlGqFDAIEAgQFAg4BAQaBYTwNXHBwFRohgmhRGQ+OIAwWg1CFFIVKdQIBOAIDAwEKAQEDCYZHhXeBa10BAQ
IronPort-PHdr: A9a23:8WN6MBxvgQpb5GTXCzPZngc9DxPP8534PQ8Qv5wgjb8GMqGu5I/rM 0GX4/JxxETIUoPW57Mh6aLWvqnsVHZG7cOHt3YPI5BJXgUO3MMRmQFoCcWZCEr9efjtaSFyH MlLWFJ/uX+hNk0AE8flbFqUqXq3vlYv
IronPort-Data: A9a23:7uNcvqmRkg7/42g9yAt8Atbo5gy8J0RdPkR7XQ2eYbSJt1+Wr1Gzt xJNXTqDP/7fM2Ome4x+YNnn90gFvZSDmNdjQApppSs0F1tH+JHPbTi7wugcHM8zwunrFh8PA xA2M4GYRCwMZiaA4E3ratANlFEkvYmQXL3wFeXYDS54QA5gWU8JhAlq8wIDqtYAbeORXkXc4 rsen+WFYAX/g24saTpOg06+gEoHUMra6WtwUmMWPZinjHeG/1EJAZQWI72GLneQauG4ycbjG o4vZJnglo/o109F5uGNy94XQWVWKlLmBjViv1INM0SUbreukQRpukozHKJ0hU66EFxllfgpo DlGncTYpQvEosQglcxFOyS0HR2SMoUXoLveB2KbtvawlUb/TnDJybZLVl45aNhwFuZfWQmi9 NQRLDQLKxuEne/znPSwS/JngYIoK8yD0IE34y47i2qHS699B8mYHM0m5vcAtNs0rs9PG+3Ua tAWQTFudx/HJRZIPz/7Dbpvxbfy2iGkL2AwRFS9lfY4s3KPizxNjJfsatjNYOWDX+FvgRPNz o7B1yGjav0AD/SUyTeDtGilgMfdgS69U4UXUra+ntZggVCJ7m0eFBNQUkG0ydG5l0e/XtUZI EwZ/AIgsLQv7kG0Q9i7VBq9yFaYohM0UMEWHeQnrg2AooLb4gCCDGUeQWsdMNcnr8QxAzct0 3eFmtrzDnpuvaGbD3WH+d+8pDi/NH1JdWQDfiQDCwAC5vHvpYgphVTOQ8ptVqmvgbXdCzH5x T/Mvigzgbo7n9IGka68+BbMhVqRSoPhRwox4EDcWXioq18/b4++bIvu4l/ehRpdELukopC6l CBss6CjAComVPlhSATlrD0xIYyU
IronPort-HdrOrdr: A9a23:zhKZz6xHdSdYsrZCywkqKrPxkuskLtp133Aq2lEZdPULSKKlfp GV88jziyWZtN9IYgBdpTiBUJPwJU80hqQFnrX5XI3SETUO3VHIEGgM1/qb/9SNIVydygcZ79 YcT0EcMqy9MbEZt7eA3ODQKb9Jq7PrkNHKuQ6d9QYWcegAUdAG0+4NMHfjLqQAfnghOXNWLu v42uN34x6bPVgHZMWyAXcIG8LZocfQqZ7gaRkaQzY69Qinl1qTmfHHOind+i1bfyJEwL8k/2 SAuRf+/L+fv/ayzQKZ/3PP7q5RhMDqxrJ4dYKxY4kuW3TRYzSTFcdcso65zXIISSaUmRMXee z30lcd1gJImjfsly+O0FzQMkLboUgTAjfZuC6laD3Y0IrErPZQMbsYuWqfGSGpsnbI9esMoJ 5jziaXsYFaAgjHmzm479/UVwtynk7xunY6l/UP5kYvGbf2RYUh27D3xnklWasoDWb/8sQqAe NuBMbT6LJfdk6bdWnQui1qzMa3Vno+Ex+aSgxa0/blmQR+jTR81Q8V1cYflnAP+NY0TIRF/f 3NNuBtmKtVRsEbYKphDKMKQNexCGbKXRXQWVjiamjPBeUCITbAupT36LI66KWjf4EJ1oI7nN DbXFZRpQcJCjXT4A21rel2Gzz2MReAtG7Wu7JjDrBCy8jBeIY=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.93,214,1654560000"; d="scan'208,217";a="918240345"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 04 Aug 2022 04:20:17 +0000
Received: from mail.cisco.com (xfe-aln-005.cisco.com [173.37.135.125]) by alln-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id 2744KHhE015710 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=OK); Thu, 4 Aug 2022 04:20:17 GMT
Received: from xfe-rtp-002.cisco.com (64.101.210.232) by xfe-aln-005.cisco.com (173.37.135.125) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.14; Wed, 3 Aug 2022 23:20:16 -0500
Received: from NAM11-BN8-obe.outbound.protection.outlook.com (64.101.32.56) by xfe-rtp-002.cisco.com (64.101.210.232) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.14 via Frontend Transport; Thu, 4 Aug 2022 00:20:16 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=czEaLltEJd9gCa8fOB7S/T1Q5fTdRzncn04QCBfvBHWa9XW/K4CSnFZeVKvyo3q1gjsO2ryzvrnGga2xW3F59gdWwmi7uLgvqYTeTUz5dm6W+O1GZKIlPZ3Ahq3EjNSAmz++st3WgGISKCq9kYvHops3V1CTlPKrOcK0mNGtAkyJ10q4aFAm8nCKwJVHAyAJF6qsH36AKDNMuJYFnSTRZDeuvQ19WPHpdn8oakjLdwr+MxMxckMzjMwvzVNJpPyEozegHDEYJabg9orlG4gsyXtKOqI1que3rMU3JqxpwXFuahcqv1w69xFPvGQk5JEc9jrD5aU/w0o/xyHTQdcoGw==
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-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=S9l0PMSj2B9wtvQfgdBMVQv9pLAm0WlR2Ib6NqvAaFo=; b=O4DoZp2hxPBS0i7hCFy8PPOjYYLWQCG9EMVoaELMw0lQ/FLNDDdHdwBUHsllv4zH6wmuJLO5gTQRXTS1xhUrLh45mnSZXJz4gc3c2p8bo2fdBt7AD3waUmcAmBqFLJIl5QyKcEJKA3RCtsfiYKHhjFeGu30uhpxmFChqR1cVUuLIfAtPqcSIvSs6q489f6qwX4z/Ve/dWEOfOZ7zVfWevryTf7a62IIH3Y+SI7dLwz70etZBPYwh3JaFsdkWNeCO/0fV5RykJOZzrBpg8Z/ApI7d82iGKmEoAFPejIHkGFkFPnOFlw5FfezsZUcqU9+zi6JRtzRjTgOBYe1MUvgLfA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=S9l0PMSj2B9wtvQfgdBMVQv9pLAm0WlR2Ib6NqvAaFo=; b=O9o40k3XcuSgX7ZhAbKwI1Hf3Zk6ummVfndd0u4j8do41R2hSd2DLFm1zBZ0fouru40OQ5d7KlwNP1iOn70575qjOlZxp+kVzKM5KZQZwsbKhONSaBeCaUt0vdHB+TslWplITkX+j1gSDoaIuoCK/GrqXFwYBzTPDz7zx6j4v0E=
Received: from BY5PR11MB4337.namprd11.prod.outlook.com (2603:10b6:a03:1c1::14) by CH2PR11MB4437.namprd11.prod.outlook.com (2603:10b6:610:47::27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5482.14; Thu, 4 Aug 2022 04:20:08 +0000
Received: from BY5PR11MB4337.namprd11.prod.outlook.com ([fe80::290d:2dc1:eaf8:6b1b]) by BY5PR11MB4337.namprd11.prod.outlook.com ([fe80::290d:2dc1:eaf8:6b1b%4]) with mapi id 15.20.5504.014; Thu, 4 Aug 2022 04:20:07 +0000
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "zhang.zheng@zte.com.cn" <zhang.zheng@zte.com.cn>, "acee=40cisco.com@dmarc.ietf.org" <acee=40cisco.com@dmarc.ietf.org>, "ginsberg=40cisco.com@dmarc.ietf.org" <ginsberg=40cisco.com@dmarc.ietf.org>
CC: "tte@cs.fau.de" <tte@cs.fau.de>, "huaimo.chen@futurewei.com" <huaimo.chen@futurewei.com>, "bier@ietf.org" <bier@ietf.org>, "chen.ran@zte.com.cn" <chen.ran@zte.com.cn>
Thread-Topic: [Bier] I-D Action: draft-ietf-bier-te-isis-01.txt
Thread-Index: AQHYo39zdI9X1n82nUiLsx5a78v1La2V0I5ggAayYICAABJhAIAARI4AgAAyPwCAAC+SYIAAB4IAgAAAl5CAAAJYAIAA0ykAgAAPXFA=
Date: Thu, 04 Aug 2022 04:20:07 +0000
Message-ID: <BY5PR11MB4337B2F8E26FD0033701CE24C19F9@BY5PR11MB4337.namprd11.prod.outlook.com>
References: 202208031610020423221@zte.com.cn, 981A4743-4D0F-4FAD-B156-F818D5BFEDD5@cisco.com, BY5PR11MB433772FEDD897D9027EC2588C19C9@BY5PR11MB4337.namprd11.prod.outlook.com, 18F1F356-5620-4A81-8E2F-C1CAAD5AFAF6@cisco.com, BY5PR11MB4337F8CAB5CC8191A5373AE8C19C9@BY5PR11MB4337.namprd11.prod.outlook.com, 45C3D940-A8EE-4808-9CA4-E527C5FDA55A@cisco.com <202208041113161788102@zte.com.cn>
In-Reply-To: <202208041113161788102@zte.com.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=cisco.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: a7ff0df3-f606-4fa4-32f9-08da75d09d41
x-ms-traffictypediagnostic: CH2PR11MB4437:EE_
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 4x0ivsRLRktR8LegbPR4XwNkyFBBOJx2TYutWC6+1YSYHJa1lgj98j28JKXnf/BE/rhvlFjaM5OOO30/kOpkLGhzc6Af0J5G5HIEhUv6X2Ow6yO1HHCzoG6Zx3Qwov0cTkBG1a2zXy6SphIQ69dEXC/Ben5ylVCWmDFeJv0iYBSPz6zM2a1hDnnPVfy1AjEEvP2hwMwSUewmjVS+bcposfONcmO5eF+Ffic9dYBAd2wsk9Gy4ftuc2s4hljkLHXBZkBs7bPUeiPu7LnbDFbbYX1uCo3QWiMqDfwTQtl2uKTRBNML/HkdkqVHb8vXoBzRHQDh2QRHZO5R8sl/rHyHNDkIKQa8bDFCEAsx1RfJ6iWV2W+1p0hUQI/TN2gEfeIou82CAqYYKQ7FVJUPywEqtukCq3nCO8OBYUm5mBuySI9le0bSUlWOToJzz0xbltHxk0WR5Bl6S3023lMCUpk5EKxavWSBXVcr9EsX/WQsK8URL9vpqy4T0Ky71/QRuDY4GKunCiw3LKyMdOp7hxig7xpkIBGJNboUGxIILzhE6bLaa9H1f7/V8EjE2Z49Ws9vTf2s6mPag8n8DucOqy3xaFcEFlDRiFOVVJMXubmWl8EJ0PVj0fDTx9PLe+qIatZUM+foA8VRVx15VfsNw4v0TiB9838V6Z8HZIktP4biFR3NWFDvMOq4wxc5byEqrCicAg+XSrILM7bf7R/p2B0r0NDBGPJGLzOo4AMVkJXRkAMJ21YsITu6qC6MSHp6/CnJCFLqn0dqXMj8BLTByhJyGSXIZn2hsvx2IHEzLfSjO98NBP2PpRzcGuN+nF7d+GgbHf8zuflM535l2JNlrv5/SYjYf0WHrLNQzRl9zDbJRWpfxymS1UV/8qDnS6d2OT1v
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BY5PR11MB4337.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230016)(4636009)(396003)(366004)(39860400002)(376002)(136003)(346002)(76116006)(38070700005)(122000001)(8676002)(4326008)(83380400001)(8936002)(5660300002)(30864003)(86362001)(2906002)(186003)(55016003)(66946007)(64756008)(316002)(110136005)(54906003)(66574015)(966005)(33656002)(45080400002)(38100700002)(52536014)(66446008)(53546011)(66556008)(478600001)(41300700001)(166002)(9686003)(7696005)(6506007)(71200400001)(66476007)(579004); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: 0jf11XRi0O9W2+o1cdRqB2uGKKQXnMIc+je9NCUxgXnckUlPD8gaEMZG6Ig7mBiwlAHi3mLX3eub0JtBwOhNicQ01WBYD1KWzwMjWlxjYx3r2ZKVlxDGA6oFsnO9JQ2yZMadESpSbikthGzcqt20Q2wrMwdb20dlzO82+1snz6SRB1gsdCaHctz/hmuGDrz1jwFD+VdvJMfnKE7lnXIrkF8yJp93JuigQhG24aSEFqf999zhDa6C5mm3Ywf3erjo7MRMJLP5mnGqLzU2dvhIxY2LSnD6tjI1XmX3Ed3+DavOpNLQI1kRLls3CmUxk8qIX19gsKGm1pbsjGRwuea8aI4fk/N4I3+opQMvMum6V+Ksc7SlTNqKSsumN6K9nCmKTAfu+1SbLJ2n2ZEhfODE5jua1pMOzM3saYjmf1Kx1JFhMly0nUqgtLE6gUD5+jcnf6yDvciUOn5ZBXn5NB/NYygGR3ENxi/d8bhD8l9ZVSc03TiFN/Z3QM3Z0ecdYQVB/5v1Xb41PY7k8MAja2k2Bl+MdUGoj/5IpXkVyYRNNAtmQVe0ZBqC781FirEkrXSsEJeZu/hFlnHvGT7iSucdZj9FdbPT4ktStaZZGkKMRCXSemOJJsuUgQu9aysdIOM8Km80cCIoLZ4hJxNE73N5xJpFtiY0adThvoVj6JQHBzlYRb38N0y4K+dMZ2wSTRxnqWgfooJvah8GIfOZRJV30QbX8dmqPHGd81JdtUlJzZ0KSlGy4sT7PNydWWMVY99r+7gzOOq/nknSTIr+S0tIc6v2oVRGoP61D2wSpNZhqVQCTxqLxrkXHBOLEaA/WvY9Le/1WZzwr1BwTKkX3TPBsma7ZBWNqxYrvQhwtIpHbBivP95RUHwQM08WFkFzLEc+JglYVlO4bMMa7MXxfYTZeRNpZWYhhJKM2cY57b6v1mr5e15/MsdOD7XwEPFC0MVxJMdQ0hXKSw4hr/bdDfhF8plM4W3MaSz+9o0xMR4aJ5CkV37bUeJvYbZ/J027A4tVxKZq9gP35PaCc50NyM5hBVOe7cCuHT1aEwEUooSW5vzkE3+tN1eynXW5e9b/NGMEWOuMjDIzyTnteZJGK36HkYPJeMOt+LW/kD82O8XU2+YcVSBfL/XjVZmfUzs5fMOtBMOC3KQxPz2msUhW4GJL61C4YC2C0wY+PGs3dNhCVv94vdbgrU7cGMl3telxpUbhQIppz4r4PHZtBqH6ZiYsyLqS7eGM7lgzriw/olgtI9+r5KBowPoqtmnnDfmO92xZIatt7HgFArUOKgA5S08x7alGfGS1sN+tMdFmpDjbJbt20aYJ2Jrqbeg3ZmNp0FgIQff+GEMg+eWpxS5PM+qupG87nWFQVU0bIxVZXO/KjOhAjhYMIMuXQkIL9nFgfeodS/sXF6EqLXLMucntlsCkOSYyBeJzeL2IzxcjeyZnAtRELm632p+o2mXnJAqBxrED0BshiCFrKHaM86wg5DQhhJV8Wmyam0VwXMeXeFIdsmC8qWOujSoPdkUm9cxxZsCOjViJrzh15PvpXSN5vu0HtQ2OUBMVKvJoU4t0ngt2keRY0vMMmbaoOG4dBq59jS8VzapzpVpIF557sx1H3U21/ZkT8UtDmgYf4tTEgymehKyl3+AiUPunHf1dVl4C/pC1
Content-Type: multipart/alternative; boundary="_000_BY5PR11MB4337B2F8E26FD0033701CE24C19F9BY5PR11MB4337namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BY5PR11MB4337.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: a7ff0df3-f606-4fa4-32f9-08da75d09d41
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Aug 2022 04:20:07.7664 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: fz+hD/n6IMqnfLC8b8T46JUasbbe0pX5sNqTHqaEIl0dXn6zdNd+W0iZVOeP0Hi30oCekedWju0lrdLGnsCgZQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH2PR11MB4437
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.135.125, xfe-aln-005.cisco.com
X-Outbound-Node: alln-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/K2rIhg4OqlC5epcgi-QdczgtbGU>
Subject: Re: [Bier] I-D Action: draft-ietf-bier-te-isis-01.txt
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 04 Aug 2022 04:20:24 -0000

Sandy -



You could do this per protocol or per function or a single draft for everything.
I suspect if you ask three different people you will get three different answers. 😊



Given that the BGP-LS content is protocol independent and the actual content of each functional draft is modest, I am inclined to say go for a single draft that combines all of the current 5 drafts (including expired BGP-LS).

But any approach which reduces the number of drafts would be an improvement.



   Les



> -----Original Message-----

> From: zhang.zheng@zte.com.cn <zhang.zheng@zte.com.cn>

> Sent: Wednesday, August 3, 2022 8:13 PM

> To: acee=40cisco.com@dmarc.ietf.org;

> ginsberg=40cisco.com@dmarc.ietf.org

> Cc: Les Ginsberg (ginsberg) <ginsberg@cisco.com>; tte@cs.fau.de;

> huaimo.chen@futurewei.com; bier@ietf.org; chen.ran@zte.com.cn

> Subject: Re: [Bier] I-D Action: draft-ietf-bier-te-isis-01.txt

>

> Hi Acee, Les,

> Thank you very much for your suggestion.

> I agree with you that the IGP extension drafts need to be combined.

> IMO the drafts maybe combined by function. That is the BP advertisement

> for all the IGP protocols can be combined into one draft, the BIFT-ID

> advertisement for all the IGP protocols can be combined into another draft,

> do you think it's a reasonable way? But it's just my opinion, I am not sure

> what other people thinking.

> And in fact there is a BGP-LS extension draft already:

> https://datatracker.ietf.org/doc/draft-cz-bier-bgp-ls-bier-te-ext/, though it's

> expired now.

> Best regards,

> Sandy

>

>

> ------------------Original------------------

> From: AceeLindem(acee) <acee=40cisco.com@dmarc.ietf.org<mailto:acee=40cisco.com@dmarc.ietf.org>>

> To: Les Ginsberg (ginsberg) <ginsberg@cisco.com<mailto:ginsberg@cisco.com>>;Les Ginsberg (ginsberg)

> <ginsberg=40cisco.com@dmarc.ietf.org<mailto:ginsberg=40cisco.com@dmarc.ietf.org>>;张征00007940;tte@cs.fau.de

> <tte@cs.fau.de<mailto:tte@cs.fau.de>>;

> Cc: huaimo.chen@futurewei.com<mailto:huaimo.chen@futurewei.com>

> <huaimo.chen@futurewei.com<mailto:huaimo.chen@futurewei.com>>;bier@ietf.org <bier@ietf.org<mailto:bier@ietf.org>>;

> Date: 2022年08月03日 22:37

> Subject: Re: [Bier] I-D Action: draft-ietf-bier-te-isis-01.txt

> That would be another alternative - incorporate the additional extensions

> into the base drafts.

> Thanks,

> Acee

> On 8/3/22, 10:34 AM, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com<mailto:ginsberg@cisco.com>>

> wrote:

> Acee -

> My comment was only on the two IS-IS drafts:

> draft-ietf-bier-te-isis

> draft-zwx-bier-te-isis-extensions

> Your comment was apparently regarding all the IGP drafts.

> Fewer drafts is better in this case - and if BIER WG wants to follow the LSR

> model and combine IS-IS/OSPF/OSPFv3 into a single draft I am happy to

> support that.

> But even if BIER wants to maintain drafts per protocol, I see no reason to

> have multiple drafts per protocol for this functionality.

> I also support Acee's suggestion to Include BGP-LS support in the same draft.

> Les

> > -----Original Message-----

> > From: Acee Lindem (acee) <acee@cisco.com<mailto:acee@cisco.com>>

> > Sent: Wednesday, August 3, 2022 7:27 AM

> > To: Les Ginsberg (ginsberg) <ginsberg=40cisco.com@dmarc.ietf.org<mailto:ginsberg=40cisco.com@dmarc.ietf.org>>;

> > zhang.zheng@zte.com.cn<mailto:zhang.zheng@zte.com.cn>; tte@cs.fau.de<mailto:tte@cs.fau.de>

> > Cc: huaimo.chen@futurewei.com<mailto:huaimo.chen@futurewei.com>; Les Ginsberg (ginsberg)

> > <ginsberg@cisco.com<mailto:ginsberg@cisco.com>>; bier@ietf.org<mailto:bier@ietf.org>

> > Subject: Re: [Bier] I-D Action: draft-ietf-bier-te-isis-01.txt

> >

> >

> >

> > On 8/3/22, 10:06 AM, "Les Ginsberg (ginsberg)"

> > <ginsberg=40cisco.com@dmarc.ietf.org<mailto:ginsberg=40cisco.com@dmarc.ietf.org>> wrote:

> >

> >     I tend to agree w Acee's comment.

> >     Two drafts seems excessive here.

> >

> > Actually there are 3 (IS-IS, OSPF, OSPFv3), not even counting the inevitable

> > BGP-LS draft.

> >

> > One point I made before on the cut and paste between drafts. In

> > OSPF/OSPFv3, Sub-TLVs are referred to as Sub-TLVs no matter what their

> > level of nesting. If we would have adopted the sub-sub....-TLV notation,

> we

> > have many levels of nesting for the CCAMP TE LSAs for Optical

> technologies.

> >

> > Thanks,

> > Acee

> >

> >     If the argument is that you want to keep the IS-IS  MPLS related stuff in a

> > separate draft, I point out that RFC 8401 did NOT do that.

> >

> >         Les

> >

> >     > -----Original Message-----

> >     > From: BIER <bier-bounces@ietf.org<mailto:bier-bounces@ietf.org>> On Behalf Of Acee Lindem (acee)

> >     > Sent: Wednesday, August 3, 2022 4:10 AM

> >     > To: zhang.zheng@zte.com.cn<mailto:zhang.zheng@zte.com.cn>; tte@cs.fau.de<mailto:tte@cs.fau.de>

> >     > Cc: huaimo.chen@futurewei.com<mailto:huaimo.chen@futurewei.com>;

> > ginsberg=40cisco.com@dmarc.ietf.org<mailto:ginsberg=40cisco.com@dmarc.ietf.org>;

> >     > bier@ietf.org<mailto:bier@ietf.org>

> >     > Subject: Re: [Bier] I-D Action: draft-ietf-bier-te-isis-01.txt

> >     >

> >     > Hi Sandy,

> >     > Why didn't you put all the IGP extensions in the same draft in different

> >     > sections? It is basically the same two Sub-TLVs with different IANA

> >     > considerations. When you consolidate, can you also add the BGP-LS

> >     > extension?

> >     > Thanks,

> >     > Acee

> >     >

> >     > On 8/3/22, 4:11 AM, "BIER on behalf of zhang.zheng@zte.com.cn<mailto:zhang.zheng@zte.com.cn>"

> <bier-

> >     > bounces@ietf.org<mailto:bounces@ietf.org> on behalf of zhang.zheng@zte.com.cn<mailto:zhang.zheng@zte.com.cn>> wrote:

> >     >

> >     >     Hi Toerless,

> >     >     The BIFT-ID advertisement as you said in the email, has been defined

> in

> >     > these drafts:

> >     >     https://datatracker.ietf.org/doc/draft-zwx-bier-te-isis-extensions/

> >     >     https://datatracker.ietf.org/doc/draft-zwx-bier-te-ospf-extensions/

> >     >     https://datatracker.ietf.org/doc/draft-zwx-bier-te-ospfv3-<https://datatracker.ietf.org/doc/draft-zwx-bier-te-ospfv3-extensions/>

> extensions/<https://datatracker.ietf.org/doc/draft-zwx-bier-te-ospfv3-extensions/>

> >     >     And these drafts was presented in IETF114 BIER WG meeting.

> >     >     Looking forward for your comments and suggestions.

> >     >     Best regards,

> >     >     Sandy

> >     >

> >     >     ------------------Original------------------

> >     >     From: ToerlessEckert <tte@cs.fau.de<mailto:tte@cs.fau.de>>

> >     >     To: Huaimo Chen <huaimo.chen@futurewei.com<mailto:huaimo.chen@futurewei.com>>;

> >     >     Cc: Les Ginsberg (ginsberg)

> >     > <ginsberg=40cisco.com@dmarc.ietf.org<mailto:ginsberg=40cisco.com@dmarc.ietf.org>>;bier@ietf.org

> <bier@ietf.org<mailto:bier@ietf.org>>;

> >     >     Date: 2022年08月03日 12:05

> >     >     Subject: Re: [Bier] I-D Action: draft-ietf-bier-te-isis-01.txt

> >     >     Hey folks

> >     >     I am trying to wrap my head around how one would use these IS-IS

> >     > extensions for BIER-TE,

> >     >     and what if any of such semantic information might help the

> > document...

> >     >     The way i assume this extension to be used is that some poor

> >     > system/operator assigns BIER-TE

> >     >     bits and configures the actual BIER-TE BIFT entries with

> > forward_connected

> >     > entries to

> >     >     the neighbors. Similarily to how the same poor system/operator

> would

> >     > configure interface

> >     >     IP addresses on routers. This IS-IS work does not help to eliminate

> any

> > of

> >     > this initial provisioning. [Yes/No]

> >     >     The way the IS-IS kicks in is to disseminate the information from

> those

> >     > forward_connected BIER-TE

> >     >     BIFT entries across the domain, so that for example ingres-PE could

> >     > calculate BIER-TE paths through the

> >     >     topology. [Yes/No].

> >     >     If i am on the right track, then let me continue:

> >     >     The first detail is that these IS-IS entries will seemingly have some

> >     > elements from rfc5303

> >     >     that identify the interface and/or neighbor. So those need to match

> > what

> >     > would be found in

> >     >     the BIFT. I am not sure if it is obvious to every implementer how to

> > achieve

> >     > that without

> >     >     additional guidance. For example i guess we ALSO need to have the

> IS-

> > IS

> >     > signaling for the

> >     >     label ranges for the SD/SI in BIER. Have we checked thart we simply

> >     > should/can use them also

> >     >     for the SD that we use for BIER-TE ? I hope so, but i can not

> remember

> > the

> >     > discussion.

> >     >     Likewise for BIER-TE over L2 (not MPLS), we have the dependency

> > against

> >     > picking one particular

> >     >     bift-id encoding, and the "i don't know which" signaling we may have

> to

> >     > support it (could

> >     >     of course be all manual configured).

> >     >     Yes, this is just dependencies to make a deployment work, not

> > necessarily

> >     > something an

> >     >     IGP specialist wants to see in an IGP draft/RFC, but i hope we can

> have

> > this

> >     > more

> >     >     holistic discussion here ;-)

> >     >     So, then RFC5305 has all those wonderful adjacency parameters to

> help

> > for

> >     > example ingres

> >     >     PE CSPF calculations. And i remember those from  RSVP-TE days. But

> > now

> >     > the ISIS draft

> >     >     proposal introduces the BAR/IPA parameters, and i have never seen

> > those

> >     > being mentioned

> >     >     or used in conjunction with TE in general or CSPF specifically. So it

> > would be

> >     > great

> >     >     to have at least one example of how to use PAR/IPA be explained

> > here. If

> >     > we can not

> >     >     construct such examples, then BIER/IPA may be leftovers from the

> IS-

> > IS

> >     > encodings for

> >     >     BIER, where of course there is no CSPF and the like...

> >     >     Next question: Would it be possible to express with these IS-IS

> option

> > the

> >     > forward_routed()

> >     >     I think it would be great if we would build the IS-IS extensions such

> that

> >     > that is possible,

> >     >     because forward_routed entries can be a great help to get along with

> > the

> >     > available bits.

> >     >     I also would need to get my head around those IS-IS pseudonodes...

> if

> >     > anyone has an example,

> >     >     that would be great.

> >     >     Thanks so much!

> >     >     Toerless

> >     >     On Wed, Aug 03, 2022 at 02:58:53AM +0000, Huaimo Chen wrote:

> >     >     > Hi Les,

> >     >     >

> >     >     >     Thank you very much for your valuable comments.

> >     >     >     I have addressed them in the updated draft (uploaded).

> >     >     >     My responses are also inline below with [HC].

> >     >     >

> >     >     > Best Regards,

> >     >     > Huaimo

> >     >     > -----Original Message-----

> >     >     > From: BIER <bier-bounces@ietf.org<mailto:bier-bounces@ietf.org>> On Behalf Of Les Ginsberg

> >     > (ginsberg)

> >     >     > Sent: Friday, July 29, 2022 4:59 PM

> >     >     > To: bier@ietf.org<mailto:bier@ietf.org>

> >     >     > Subject: Re: [Bier] I-D Action: draft-ietf-bier-te-isis-01.txt

> >     >     >

> >     >     > Some pedantic comments on this draft:

> >     >     >

> >     >     > For the new BIER-TE sub-TLV:

> >     >     >

> >     >     > 1)The relevant registry has been renamed to be "IS-IS Sub-TLVs for

> > TLVs

> >     > Advertising Neighbor Information". Please use this new name.

> >     >     >

> >     >

> >

> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fww

> >     > w.iana.org%2Fassignments%2Fisis-tlv-codepoints%2Fisis-tlv-

> >     > codepoints.xhtml%23isis-tlv-codepoints-advertising-neighbor-

> >     >

> >

> information&amp;data=05%7C01%7Chuaimo.chen%40futurewei.com%7C5b

> >     >

> >

> bd38c256024261ea5608da71a546c0%7C0fee8ff2a3b240189c753a1d5591fedc%

> >     >

> >

> 7C1%7C0%7C637947251926210034%7CUnknown%7CTWFpbGZsb3d8eyJWIjoi

> >     >

> >

> MC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C300

> >     >

> >

> 0%7C%7C%7C&amp;sdata=ybC6zOJkG1sRe%2FQosV23MElysXHkg7jnHS70N

> >     > %2Bf7bpE%3D&amp;reserved=0

> >     >     > [HC]: I have renamed it as you suggested.

> >     >     >

> >     >     > 2)Please do NOT insert padding to keep content aligned on a 4 byte

> >     > boundary. This may be useful for OSPF, but it is not for IS-IS as TLVs are

> > NOT

> >     > aligned inside an LSP. All you are doing is wasting space - which is

> precious

> > in

> >     > IS-IS given the limited LSP space.

> >     >     > [HC]: Removed padding.

> >     >     >

> >     >     > 3)You say in Section 2:

> >     >     >

> >     >     > "Note that if each of BitPosition

> >     >     >    and DrEndBitPosition uses more than 2 octets, we use 4 or more

> > octets

> >     >     >    for each of them."

> >     >     >

> >     >     > I do not see how the receiver of the sub-TLV could tell whether the

> 2

> >     > octet or 4 octet encoding was sent as you have nothing that specifies

> the

> >     > length of these fields.

> >     >     > You can't use the total length of the sub-TLV as it could include

> > optional

> >     > sub-sub-TLVs.

> >     >     >

> >     >     > ??

> >     >     > [HC]: Deleted the quoted text.

> >     >     >

> >     >     > 4)In IANA section, I do not know why you specified "N" for TLVs 23

> > and

> >     > 223.

> >     >     > While RFC 5311 (which defines these TLVs) is not popular, if there

> was

> > an

> >     > implementation, I see no reason why it should be invalid to send the

> > BIER-TE

> >     > info in these TLVs.

> >     >     > [HC]: Changed "n" to "y" for TLVs 23 and 223.

> >     >     >

> >     >     > Thanx.

> >     >     >

> >     >     >     Les

> >     >     >

> >     >     >

> >     >     > > -----Original Message-----

> >     >     > > From: BIER <bier-bounces@ietf.org<mailto:bier-bounces@ietf.org>> On Behalf Of internet-

> >     > drafts@ietf.org<mailto:drafts@ietf.org>

> >     >     > > Sent: Friday, July 29, 2022 12:13 PM

> >     >     > > To: i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>

> >     >     > > Cc: bier@ietf.org<mailto:bier@ietf.org>

> >     >     > > Subject: [Bier] I-D Action: draft-ietf-bier-te-isis-01.txt

> >     >     > >

> >     >     > >

> >     >     > > A New Internet-Draft is available from the on-line Internet-Drafts

> >     > directories.

> >     >     > > This draft is a work item of the Bit Indexed Explicit Replication WG

> > of

> >     > the IETF.

> >     >     > >

> >     >     > >         Title           : IS-IS Extensions for BIER-TE

> >     >     > >         Authors         : Huaimo Chen

> >     >     > >                           Mike McBride

> >     >     > >                           Aijun Wang

> >     >     > >                           Gyan S. Mishra

> >     >     > >                           Yanhe Fan

> >     >     > >                           Lei Liu

> >     >     > >                           Xufeng Liu

> >     >     > >   Filename        : draft-ietf-bier-te-isis-01.txt

> >     >     > >   Pages           : 7

> >     >     > >   Date            : 2022-07-29

> >     >     > >

> >     >     > > Abstract:

> >     >     > >    This document describes IS-IS extensions for distributing

> >     >     > >    BitPositions configured on the links in "Bit Index Explicit

> >     >     > >    Replication Traffic Engineering" (BIER-TE) domain.

> >     >     > >

> >     >     > >

> >     >     > >

> >     >     > > The IETF datatracker status page for this draft is:

> >     >     > >

> >     >

> >

> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdata

> >     > tracker.ietf.org%2Fdoc%2Fdraft-ietf-bier-te-

> >     >

> >

> isis%2F&amp;data=05%7C01%7Chuaimo.chen%40futurewei.com%7C5bbd38

> >     >

> >

> c256024261ea5608da71a546c0%7C0fee8ff2a3b240189c753a1d5591fedc%7C1

> >     >

> >

> %7C0%7C637947251926210034%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC

> >     >

> >

> 4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%

> >     >

> >

> 7C%7C%7C&amp;sdata=99ojCa2m%2BTeMk0OfxeifsmVrhvNaK7jQJp0fu0syR

> >     > N8%3D&amp;reserved=0

> >     >     > >

> >     >     > > There is also an htmlized version available at:

> >     >     > >

> >     >

> >

> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdata

> >     > tracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-bier-te-isis-

> >     >

> >

> 01&amp;data=05%7C01%7Chuaimo.chen%40futurewei.com%7C5bbd38c256

> >     >

> >

> 024261ea5608da71a546c0%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0

> >     >

> >

> %7C637947251926210034%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjA

> >     >

> >

> wMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C

> >     >

> >

> %7C&amp;sdata=%2F8qaH0ZvQBAfGM4WIre0jpcI6As7wjXjdqbxOfdGHxo%3

> >     > D&amp;reserved=0

> >     >     > >

> >     >     > > A diff from the previous version is available at:

> >     >     > >

> >     >

> >

> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fww

> >     > w.ietf.org%2Frfcdiff%3Furl2%3Ddraft-ietf-bier-te-isis-

> >     >

> >

> 01&amp;data=05%7C01%7Chuaimo.chen%40futurewei.com%7C5bbd38c256

> >     >

> >

> 024261ea5608da71a546c0%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0

> >     >

> >

> %7C637947251926210034%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjA

> >     >

> >

> wMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C

> >     >

> >

> %7C&amp;sdata=L77o0dGWGuSwL9vSm1Durc56Fl5zONoDq%2F8ij12v9lc%3D

> >     > &amp;reserved=0

> >     >     > >

> >     >     > >

> >     >     > > Internet-Drafts are also available by rsync at

> > rsync.ietf.org::internet-

> >     > drafts

> >     >     > >

> >     >     > >

> >     >     > > _______________________________________________

> >     >     > > BIER mailing list

> >     >     > > BIER@ietf.org<mailto:BIER@ietf.org>

> >     >     > >

> >     >

> >

> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fww

> >     >

> >

> w.ietf.org%2Fmailman%2Flistinfo%2Fbier&amp;data=05%7C01%7Chuaimo.c

> >     >

> >

> hen%40futurewei.com%7C5bbd38c256024261ea5608da71a546c0%7C0fee8ff

> >     >

> >

> 2a3b240189c753a1d5591fedc%7C1%7C0%7C637947251926210034%7CUnkno

> >     >

> >

> wn%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1

> >     >

> >

> haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=em5K2lvVvXwkSl

> >     > ye1egSX%2BgtdfeqDArSsAycQJTPArI%3D&amp;reserved=0

> >     >     >

> >     >     > _______________________________________________

> >     >     > BIER mailing list

> >     >     > BIER@ietf.org<mailto:BIER@ietf.org>

> >     >     >

> >     >

> >

> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fww

> >     >

> >

> w.ietf.org%2Fmailman%2Flistinfo%2Fbier&amp;data=05%7C01%7Chuaimo.c

> >     >

> >

> hen%40futurewei.com%7C5bbd38c256024261ea5608da71a546c0%7C0fee8ff

> >     >

> >

> 2a3b240189c753a1d5591fedc%7C1%7C0%7C637947251926210034%7CUnkno

> >     >

> >

> wn%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1

> >     >

> >

> haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=em5K2lvVvXwkSl

> >     > ye1egSX%2BgtdfeqDArSsAycQJTPArI%3D&amp;reserved=0

> >     >     >

> >     >     --

> >     >     ---

> >     >     tte@cs.fau.de<mailto:tte@cs.fau.de>

> >     >     _______________________________________________

> >     >     BIER mailing list

> >     >     BIER@ietf.org<mailto:BIER@ietf.org>

> >     >     https://www.ietf.org/mailman/listinfo/bier

> >     >

> >     >     _______________________________________________

> >     >     BIER mailing list

> >     >     BIER@ietf.org<mailto:BIER@ietf.org>

> >     >     https://www.ietf.org/mailman/listinfo/bier

> >     >

> >     > _______________________________________________

> >     > BIER mailing list

> >     > BIER@ietf.org<mailto:BIER@ietf.org>

> >     > https://www.ietf.org/mailman/listinfo/bier

> _______________________________________________

> BIER mailing list

> BIER@ietf.org<mailto:BIER@ietf.org>

> https://www.ietf.org/mailman/listinfo/bier