IETF Logo Mail Archive

Re: [Idr] 答复: draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14 to 10/28/2019) -

Huaimo Chen <huaimo.chen@futurewei.com> Mon, 28 October 2019 01:16 UTC

Return-Path: <huaimo.chen@futurewei.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 7D90812008F for <idr@ietfa.amsl.com>; Sun, 27 Oct 2019 18:16:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 aGrrUKDP0SHF for <idr@ietfa.amsl.com>; Sun, 27 Oct 2019 18:16:45 -0700 (PDT)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-eopbgr750098.outbound.protection.outlook.com [40.107.75.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A961C12008D for <idr@ietf.org>; Sun, 27 Oct 2019 18:16:44 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=VFCLW2NtW9YfTMwMFv46Jw2eTDH5VTMSq9BaoRJUo5VIyObJ9LyrnkGVdepixTVU0Ev7wUD+5ETbXGVUnyfUx1FwZW0bT+Y+IXQG3faZvSFtW56KIglWZpkFUMC4a9aE+JpInEEO0pwjhF/bjKbctqyo9lzgjQEGHHk7XgVldEoNEWY08Zi9fhrjzJoBKaB/aAZnNNnyXwdmoZmAfWgqg6JPcjtd/QrDcs2BerI1sC4k7Sk6l96bRZOTl3Vyu2mqJ2cWM+picIS8Gxemrs1VNC4TCNEeX0XF4MnuTFPHeMIjfJtg9zOuJyigYKHLcaqEyh4p4dExwAEoo88JgQSGvw==
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=y5rRPsHJ5n0xUcdpEVcmUU6mmUFMJXWGllho7jogKNg=; b=EVCvxZR04r+vnovcWz26B5e9YTP1NpV+4lMv/LUC8WOgAE4+OFwbR+czWT0LrrxG8BrF/zr+SdabtNlGxnExvx/b2Mr/CJpkGg68CHekA24o1UJTiUueUtDkhBKebL1Q3DnGNtdt6YvK+fY9M092MPyu97I32RVsTb4A8vkLogqVcAsRVteDG/PXro5X9i60w3h2VnVwNjwu9Ig9tyNuW3gNEpucxVFF8RhztoYnrFDpDvxFS+EkAWgWpgEL6QdVtKGRW5dlobzRFTSfwse4x1hKlXiDaRRMdlHq+pWFYOkNBT6RYLI0WnG7RopE6aL6jtgrR5yZTvAtKdZp4NkJ9Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=y5rRPsHJ5n0xUcdpEVcmUU6mmUFMJXWGllho7jogKNg=; b=nE72dGp94vNaA+H+5a+xIqgvCmUhcvvulircQH3UgjuM6RkwHQie1oH/LVq1kwVNiw09LvZyqjWS+d1b8cGvmR87uXKDSm5WK1Tk4yrs/rSdSc7TYErD2YG7bc0zbMFp0kM4J3edrOTmn2hdiSerFZ1w+E61vlUDeCk9x8LRFv0=
Received: from MWHPR13MB1805.namprd13.prod.outlook.com (10.171.146.11) by MWHPR13MB0909.namprd13.prod.outlook.com (10.169.172.157) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2408.15; Mon, 28 Oct 2019 01:16:39 +0000
Received: from MWHPR13MB1805.namprd13.prod.outlook.com ([fe80::e1f0:92f3:6f71:6e97]) by MWHPR13MB1805.namprd13.prod.outlook.com ([fe80::e1f0:92f3:6f71:6e97%12]) with mapi id 15.20.2408.014; Mon, 28 Oct 2019 01:16:39 +0000
From: Huaimo Chen <huaimo.chen@futurewei.com>
To: "Chengli (Cheng Li)" <chengli13@huawei.com>, Susan Hares <shares@ndzh.com>, 'idr wg' <idr@ietf.org>
CC: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
Thread-Topic: [Idr] 答复: draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14 to 10/28/2019) -
Thread-Index: AQHVjEBprHH/ARpSSkeD0VkEycboSqdvPnEo
Date: Mon, 28 Oct 2019 01:16:39 +0000
Message-ID: <MWHPR13MB18059351426F69EF89025E58F2660@MWHPR13MB1805.namprd13.prod.outlook.com>
References: <00f401d58b43$aa968ac0$ffc3a040$@ndzh.com>, <C7C2E1C43D652C4E9E49FE7517C236CB02763C75@dggeml529-mbx.china.huawei.com>
In-Reply-To: <C7C2E1C43D652C4E9E49FE7517C236CB02763C75@dggeml529-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=huaimo.chen@futurewei.com;
x-originating-ip: [2601:199:4300:8e5a:d1a7:5c25:a967:f1d8]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3ae429f4-04de-4112-e61b-08d75b447c47
x-ms-traffictypediagnostic: MWHPR13MB0909:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <MWHPR13MB09090816F60B7FECE5B96214F2660@MWHPR13MB0909.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0204F0BDE2
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(376002)(346002)(396003)(39830400003)(366004)(136003)(189003)(199004)(33656002)(476003)(44832011)(6116002)(224303003)(486006)(606006)(11346002)(446003)(2906002)(25786009)(19627405001)(7736002)(74316002)(14454004)(76116006)(66476007)(66556008)(64756008)(66446008)(86362001)(478600001)(66946007)(110136005)(6436002)(316002)(81156014)(55016002)(71200400001)(71190400001)(4326008)(6246003)(5660300002)(236005)(6306002)(54896002)(9686003)(52536014)(256004)(76176011)(7696005)(14444005)(6506007)(53546011)(229853002)(99286004)(8936002)(186003)(46003)(105004)(102836004)(81166006); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR13MB0909; H:MWHPR13MB1805.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: futurewei.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 27sENs54PoHvKPH94f9f7nxdSJQezMnn8jnHidgT1LVYqEDhFAbgy4/GnxDyUYl3d7Wy/SL7LvBBt7+muoeEPuNlSzGZHEzTTK/JqfJcYxWAV8o3P0fsWYDRYaMT4piubOJsAlmvE8VH5CQ2iBrZu4UUJrdPFEreJdKQWynamZhnSL7Jgvv7PQCMy8AnpckUKX6ygRmZUOHsD/DDSr8WOvwVDHKW1JjiVPrbI0EAnFllx5qnMKZ7S/zTKbLRW02UaOU9LAC/lZmztuBuwLS2Kau++jtLNCwUiCO4NxApcmbcNtbuk4uD0DPaFTxSzd5B92IHSlF/LN7LSdmjDXyJ+exMESPHf31omiIHaKH1MG6r8BjMNk+D3KK7T9LGXCVWDzt1xWfBpCFe+HP7+lD77nopTn/gxznKQHs9kQFn18uqsZN7JKvkrM04JjHV932UW/JyoUom+5u4kuLBlIY+f0XSXqEHaMGGUBBoO08pHdw=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MWHPR13MB18059351426F69EF89025E58F2660MWHPR13MB1805namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 3ae429f4-04de-4112-e61b-08d75b447c47
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Oct 2019 01:16:39.3876 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: v4cUzJsBXa5Uqhqc2MCuGN1DNB8KxGW0NotSy2Cm6uKW53cpqj6A0GctI2B/crhjl7dWAvF3tdjVs1DL+n6ptg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR13MB0909
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/h6q-vYg6kGLgh5MKzkS480NP88s>
Subject: Re: [Idr] 答复: draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14 to 10/28/2019) -
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: Mon, 28 Oct 2019 01:16:49 -0000

Hi Cheng,

    Thanks much for your support and comments.

Best Regards,
Huaimo
________________________________
From: Idr <idr-bounces@ietf.org> on behalf of Chengli (Cheng Li) <chengli13@huawei.com>
Sent: Saturday, October 26, 2019 5:00 PM
To: Susan Hares <shares@ndzh.com>; 'idr wg' <idr@ietf.org>
Cc: Pengshuping (Peng Shuping) <pengshuping@huawei.com>
Subject: [Idr] 答复: draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14 to 10/28/2019) -


Hi WG,



After reading the document, I think it is useful to distribute routing policy in BGP, and I think it is ready for WG adoption.



Well,  I have some comments and questions:



0．  Section 3, Problem statement, may add more text to specify

[HC]: We will consider adding more details.



1．In #section-3.1<https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-li-idr-flowspec-rpd-05%23section-3.1&data=02%7C01%7Chuaimo.chen%40futurewei.com%7C870c870aa7634e2d601d08d75a57891f%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637077204344010037&sdata=NMbvqyvY2wF0IJ17mZ3LMrtDbJhrhKRvIEiY5cW7ydU%3D&reserved=0> and 3.2, P node should be illustrated in the figure, I do not find it in the figure. Also, it is a little bit hard for me to get what is inbound and outbound from the figure. May add more text to clarify?

[HC]: We will add some P nodes in the figure and some details.



2. Section 4.1,

Distinguisher:  4 octet value, it should be 4 octets or 4-octet?

[HC]:  Good catch. We will update it accordingly.



3. Section 4.1, may add reference to 0?



When receiving a BGP UPDATE message, a BGP speaker processes it only

   if the peer IP address in the NLRI is the IP address of the BGP

   speaker or 0.

[HC]:  We may rephrase it.



Best Regards,

Cheng





发件人: Idr [mailto:idr-bounces@ietf.org] 代表 Susan Hares
发送时间: 2019年10月25日 22:51
收件人: 'idr wg' <idr@ietf.org>
主题: Re: [Idr] draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14 to 10/28/2019) -



Greetings:



The WG Adoption call for daft-li-idr-flowspec-rpd-05.txt need additional support for adoption.   I encourage the authors to make sure those wishing to make comments on this draft to do so over the weekend.



This draft deploys the passing of BGP policy in a new AFI/SAFI and Wide communities.   At this point, my understanding from the email is that mechanisms eases the configuration burden in some networks.



Are there any operators who are concerned that this mechanism (AFI/SAFI + Wide Communities), contains information that will leak into their network by accident?   Or will the AFI/SAFI + WIDE communities provide a clear delineation between a group of networks who support this feature and those who do not.



Thank you, Sue Hares

v2.29.0 | Report a Bug | By Email | System Status