IETF Logo Mail Archive

Re: [Idr] draft-wu-idr-bgp-segment-allocation-ext-02.txt [4/18 - 5/2/2019] - 2 week WG adoption call

li zhenqiang <li_zhenqiang@hotmail.com> Wed, 24 April 2019 07:51 UTC

Return-Path: <li_zhenqiang@hotmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE09D1200F6; Wed, 24 Apr 2019 00:51:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.115
X-Spam-Level:
X-Spam-Status: No, score=-1.115 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_HOTMAIL_RCVD2=0.874, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.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 JP1b6iTcX1Iw; Wed, 24 Apr 2019 00:51:35 -0700 (PDT)
Received: from APC01-PU1-obe.outbound.protection.outlook.com (mail-oln040092254093.outbound.protection.outlook.com [40.92.254.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4634712006F; Wed, 24 Apr 2019 00:51:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=vJ/BHnherM98W9YqwVMwm/6D1/ZZIedbe5jy1WsC3RY=; b=UJ3fMK6aaBiYeH8ycAE6DXshLGR3bPvFf9uOmbXO+h/yty0Ie+GtMuAxUbN3ddvBmkluNF//b1NS+AIRX4opgKDvvd4WCPMawt8pvy41Qe6TerSnEOZMtBIrHeSDZjqsCYMttfbv2Dr2YY0XbtN3+l1DPIfyiDCXMAj4eVnZWIvzUW0mL78SYmlCuug7kE+6Rs72i2vB8kbiQIWHpGtjkaQ9RYXWFxnY728ytnPyptoe02YAzzWaUdv+0rdVhl2Ig/f/izwPrj3o5ClRese98lgzDX1T9VJdMx0byKp3TmQufgwZtzzjBCbFsZcyYrfJ3q+xTpnw+oujYQmL9/0yUQ==
Received: from HK2APC01FT009.eop-APC01.prod.protection.outlook.com (10.152.248.51) by HK2APC01HT027.eop-APC01.prod.protection.outlook.com (10.152.249.207) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1771.16; Wed, 24 Apr 2019 07:51:26 +0000
Received: from HK0PR06MB2564.apcprd06.prod.outlook.com (10.152.248.51) by HK2APC01FT009.mail.protection.outlook.com (10.152.248.93) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1771.16 via Frontend Transport; Wed, 24 Apr 2019 07:51:26 +0000
Received: from HK0PR06MB2564.apcprd06.prod.outlook.com ([fe80::b434:4960:48cf:6aea]) by HK0PR06MB2564.apcprd06.prod.outlook.com ([fe80::b434:4960:48cf:6aea%5]) with mapi id 15.20.1835.010; Wed, 24 Apr 2019 07:51:25 +0000
From: li zhenqiang <li_zhenqiang@hotmail.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
CC: draft-ietf-teas-enhanced-vpn <draft-ietf-teas-enhanced-vpn@ietf.org>, draft-dong-lsr-sr-enhanced-vpn <draft-dong-lsr-sr-enhanced-vpn@ietf.org>
Thread-Topic: [Idr] draft-wu-idr-bgp-segment-allocation-ext-02.txt [4/18 - 5/2/2019] - 2 week WG adoption call
Thread-Index: AdT17jAMyz+sjMM6SRqyoxzf6xKAMQ==
Date: Wed, 24 Apr 2019 07:51:25 +0000
Message-ID: <HK0PR06MB2564F6AA8D6EAC625A9B4698FC3C0@HK0PR06MB2564.apcprd06.prod.outlook.com>
References: <013301d4f5ef$b1b51310$151f3930$@ndzh.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: HK0P153CA0002.APCP153.PROD.OUTLOOK.COM (2603:1096:203:18::14) To HK0PR06MB2564.apcprd06.prod.outlook.com (2603:1096:203:6d::19)
x-incomingtopheadermarker: OriginalChecksum:97304114D8E74B936B9F42E2B26344ADD177FFD9B53C0E184896B4713E12631D; UpperCasedChecksum:0526599F9A0D43B8397464C963A81E9965F68A2B3EB8115B14EBCE9395A2BC91; SizeAsReceived:7615; Count:51
x-ms-exchange-messagesentrepresentingtype: 1
x-has-attach: no
x-mailer: Foxmail 7.2.9.156[cn]
x-tmn: [OJV3IzInGxnf/H45SIBdrUM7jcUAtJRYgj/AN82f9uA=]
x-microsoft-original-message-id: <2019042415512248669312@hotmail.com>
x-ms-publictraffictype: Email
x-incomingheadercount: 51
x-eopattributedmessage: 0
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(5050001)(7020095)(20181119110)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031323274)(2017031324274)(2017031322404)(1601125500)(1603101475)(1701031045); SRVR:HK2APC01HT027;
x-ms-traffictypediagnostic: HK2APC01HT027:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-message-info: OJv65M2irfEUBkBxUGfXXIa4LpTd1e96H0QgdK6gnB9o8saprNkUjeMAf1FegtlMOn4fMK4yTcrOoPhN0PDBd3L4TP0q6yYRQ65oP9TyEFXIdnu71lfYZMv6dr4s/HzuXUsakdE4m+dg/MbiXah5YMPhmdSY3TOBGg5XCoAKPWkbzHaFE8CixyFQAqTdbdvV
Content-Type: multipart/alternative; boundary="_000_HK0PR06MB2564F6AA8D6EAC625A9B4698FC3C0HK0PR06MB2564apcp_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: b339b92c-14ef-4468-d40c-08d6c889a64d
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Apr 2019 07:51:25.8566 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HK2APC01HT027
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/7JPO-W4OGWc7CFS04R2_L1TNld4>
Subject: Re: [Idr] draft-wu-idr-bgp-segment-allocation-ext-02.txt [4/18 - 5/2/2019] - 2 week WG adoption call
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Apr 2019 07:51:38 -0000

Hi Sue and All,

Zhenqiang Li from China Mobile.

I see the value to allocate SIDs in a centralized way, especially for the SIDs representing network resources as proposed in https://datatracker.ietf.org/doc/draft-ietf-teas-enhanced-vpn/ and https://datatracker.ietf.org/doc/draft-dong-lsr-sr-enhanced-vpn/.

However, I want to know why BGP-LS is chosen to to complete this work, not PCEP or netconf? BGP-LS is mainly used to collect information from network, other than configure network from a controller.

Best Regards,
Zhenqiang Li
________________________________
li_zhenqiang@hotmail.com

From: Susan Hares<mailto:shares@ndzh.com>
Date: 2019-04-18 22:04
To: idr@ietf.org<mailto:idr@ietf.org>
Subject: [Idr] draft-wu-idr-bgp-segment-allocation-ext-02.txt [4/18 - 5/2/2019] - 2 week WG adoption call
This begins a 2 week WG Adoption call for draft-wu-idr-bgp-segment-allocation-ext-02.txt.  You can access the draft at:

https://datatracker.ietf.org/doc/draft-wu-idr-bgp-segment-allocation-ext/

In your comments, consider:


1)      Does this draft mechanisms for  extending BGP-LS to provide IDs for allocation provide a beneficial addition to BGP mechanisms for segment routing?

2)      Is the mechanism well-formed enough to adopted as a WG draft?

3)      Do you see any problems with using these IDs for flow redirection?

4)      Do you support extending BGP-LS?

5)      Should we provide an early allocation for this technology?

6)      Do you know of any early implementations?

By answering these questions during WG Adoption call, you will help John and I determine what issues need to be considered prior to finalizing this WG draft.    Your answer will help us increase the speed of processing BGP-LS drafts.

If enough people indicate that they wish an early allocation upon adoption, I will then send this early allocation to Alvaro.

Sue Hares

PS – I’m trying new methods of WG adoption calls to help speed up the process in IDR WG.   Please send any thoughts on these new methods to me or John.

v2.23.0 | Report a Bug | By Email