Re: [Idr] WG LC draft-ietf-idr-flowspec-path-redirect-10.txt [11/17/2019 to 12/2/2019]

"Henderickx, Wim (Nokia - BE/Antwerp)" <wim.henderickx@nokia.com> Thu, 28 November 2019 18:10 UTC

Return-Path: <wim.henderickx@nokia.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 EB207120809 for <idr@ietfa.amsl.com>; Thu, 28 Nov 2019 10:10:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.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 Ig98hgTNYCLi for <idr@ietfa.amsl.com>; Thu, 28 Nov 2019 10:10:07 -0800 (PST)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-eopbgr30110.outbound.protection.outlook.com [40.107.3.110]) (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 80080120840 for <idr@ietf.org>; Thu, 28 Nov 2019 10:10:06 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=JSAnZHAuIx2AoQwk1q9BRTYZlGxqWb+CkNT8W/z0Ljl8RjlhpxEIbkjXwlc4SHUOEDLsGGgDk62ZRD/Xa2BjEEqe9Btcb5DEl7//GoX5FVuJhnMzdmyNBTh76w7Xj2myOCm5Mh/n2KsrB53U0OOXs2HLLUuJwk4fhxqRMbOKzNfYZvBSobFJsp5YkJ/FbHwBEa6hlHzRsFmpf1dx2qgL03ShNOKYUcXFa2HZELFPNpfDE4ebwH7udQuWKde48FEi96Id1f9eNYBjSxqHRfYKWtLggmqZEh7Y/vReSX4JyViI0NDQUm9M21cf66VTrMfIdkuimmHpXGG8eh360zSZeA==
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=80ueTiyH+BI5K12qlgzjuorfeBRhylVMar9FSEeqI7E=; b=k0wJysIzaLeyZqZwG9xj3FOTVyAOBqGdJU2cjG1ri5Nah1PsqmitnTizRmEnsfpooQOVosPdlbt91U4GZ42Ls5AKE7RtTeP2+7A1CZUns1oUZ0UU4MTc7V4ZVwt/jQoDyImTYqnFrDXmNXqAR1YeelYvc/C6H1hhg/pz2OJrWzzC9qbwglTLtaLkAxHHzgtvdMCExBTv39qMx6odB2jxFSjuTFi2kOzOdePmWAcUkByRWSRgOuWQBsAhgQiPougQCwOxa0mUPQc7+0WJ6axDAHOwykDcmHpX8Gn4wcyNu0Lla9uBdnNfjU8yAs5KFO68Wzus5THCIV2vq0Vy+dS6DQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nokia.com; dmarc=pass action=none header.from=nokia.com; dkim=pass header.d=nokia.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com; s=selector1-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=80ueTiyH+BI5K12qlgzjuorfeBRhylVMar9FSEeqI7E=; b=emHaWqt3YZdnx5Lt7H2Ejlkkcf1+Dsn6z8S5iiU2V70T/vunfSJNGoeezHEvQciZs2TZsZp6C4byzSsTmZhHVAz73aJgwbdljwSmLdkktHj9DmAYkO/gxjvFl2lgmkAUyK5jVgNLs0MRMLXwY2nmGCsbYsznHgP3DyoVRFKA4ew=
Received: from HE1PR0701MB2714.eurprd07.prod.outlook.com (10.168.185.11) by HE1PR0701MB2955.eurprd07.prod.outlook.com (10.168.92.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2516.5; Thu, 28 Nov 2019 18:10:03 +0000
Received: from HE1PR0701MB2714.eurprd07.prod.outlook.com ([fe80::fd4a:2a3:2da0:a3d5]) by HE1PR0701MB2714.eurprd07.prod.outlook.com ([fe80::fd4a:2a3:2da0:a3d5%4]) with mapi id 15.20.2516.003; Thu, 28 Nov 2019 18:10:03 +0000
From: "Henderickx, Wim (Nokia - BE/Antwerp)" <wim.henderickx@nokia.com>
To: Lizhenbin <lizhenbin@huawei.com>, Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] WG LC draft-ietf-idr-flowspec-path-redirect-10.txt [11/17/2019 to 12/2/2019]
Thread-Index: AdWd0gRnmm6Aw4Y9ShOHyzWN65U36QH4juaQAAZtuKAABULLoAAIJ/yA
Date: Thu, 28 Nov 2019 18:10:03 +0000
Message-ID: <A77DDEB0-9DE6-47E8-8C67-46003C1DFAF3@nokia.com>
References: <016501d59dd2$e5458850$afd098f0$@ndzh.com> <1E61161D6E31D849BEA887261DB609348C9F8255@nkgeml514-mbx.china.huawei.com> <AM6PR07MB4823A7DFBF381C71B7FF5E93E0470@AM6PR07MB4823.eurprd07.prod.outlook.com> <5A5B4DE12C0DAC44AF501CD9A2B01A8D935739C1@DGGEMM532-MBX.china.huawei.com>
In-Reply-To: <5A5B4DE12C0DAC44AF501CD9A2B01A8D935739C1@DGGEMM532-MBX.china.huawei.com>
Accept-Language: nl-BE, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1f.0.191110
authentication-results: spf=none (sender IP is ) smtp.mailfrom=wim.henderickx@nokia.com;
x-originating-ip: [2a02:1810:350a:96f0:522:cda4:2d5c:b9d9]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 3a6db41f-2231-4828-e770-08d7742e312f
x-ms-traffictypediagnostic: HE1PR0701MB2955:
x-microsoft-antispam-prvs: <HE1PR0701MB29553DCBDFB5B3EE45D3117983470@HE1PR0701MB2955.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0235CBE7D0
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(39860400002)(346002)(376002)(366004)(396003)(189003)(199004)(58126008)(81166006)(110136005)(36756003)(99286004)(81156014)(229853002)(8936002)(6486002)(6436002)(8676002)(53546011)(2616005)(6506007)(71190400001)(71200400001)(186003)(256004)(76176011)(11346002)(102836004)(446003)(46003)(33656002)(7736002)(6512007)(54896002)(6246003)(6116002)(5660300002)(236005)(2906002)(6306002)(316002)(2501003)(66556008)(64756008)(606006)(25786009)(86362001)(66446008)(966005)(66476007)(91956017)(76116006)(66946007)(478600001)(14454004); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR0701MB2955; H:HE1PR0701MB2714.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: nokia.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: hLrKnKJDrwjIXmQ2Rb3glffaPvUuiGNtGZRQNwVSIE4hFKJvki/ULsV44fUJ5rW3d6qQyc05FxT9YusvJAixH9NRLtGYcHzgkXQr1xgBLT8wYWjZ/m5gw5If2Rwasuwl+sRTX01XUPi/d0rXrbwcQS9SU+N3uTlQCUH2+yY+NW/YUegcw2zAT2O2vQJ8S19UWf4fUy43cIscLNEP0EX8UGJT5u/z15jaI/xaILugz/P7YGJ+lbddEVnUcMEC34eIplA3i6J/wlQAjRMeB9JFeIiQQqOtcqCd4BWDVyXcEZk9YUBGQD1HEbhjhfXtMS15qeWUgrL+clHNd31lCNbkhbhvBG6EoXzvZK7Q4xsQjvT18XQ8u7ck8KtZ0fOV41PTQfWRQqeAUV5Ub/hpuao7GoCIUxvBgfOaqZ+KH9m71WF1ioIuRA027wlQ+TsCPldMbS9jj/lKzAlrmXblqpeED7JH6wgflORoP89aENYgd2M=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_A77DDEB09DE647E88C6746003C1DFAF3nokiacom_"
MIME-Version: 1.0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 3a6db41f-2231-4828-e770-08d7742e312f
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Nov 2019 18:10:03.6756 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: vfk0s9hA/uKvlhoHzHqF2cQqiYrhh622P7+W/dK/7ht2Zn/57S8NhP0cyVkOrFHxyrsiBKz/amMI6FYEQeTZYd3qdgdKIlc1sR9pNiws27o=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2955
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Bvs3z6e9fz1ODpHBQxh9ZGFodZQ>
Subject: Re: [Idr] WG LC draft-ietf-idr-flowspec-path-redirect-10.txt [11/17/2019 to 12/2/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: Thu, 28 Nov 2019 18:10:10 -0000

1)       Is compatible with draft-ietf-rfc5575bis-17.txt?
YES

2)       Whether the draft is useful for deployments of flow specification
YES, it is being deployed in customer environments

3)       Is this technology ready for deployment?
YES as mentioned before

4)       Is the write-up of this technology in draft-ietf-idr-flowspec-path-redirect clearly written and ready for publication?
YES


From: Idr <idr-bounces@ietf.org>; on behalf of Lizhenbin <lizhenbin@huawei.com>;
Date: Thursday, 28 November 2019 at 13:02
To: Susan Hares <shares@ndzh.com>;, IDR <idr@ietf.org>;
Subject: Re: [Idr] WG LC draft-ietf-idr-flowspec-path-redirect-10.txt [11/17/2019 to 12/2/2019]

Hi Sue & WG,
I support the last call of this document as the co-author. In the past years it is proved that the use cases proposed in the draft is very useful
and the solution is practical. After several rounds of refining the document is well written and ready for publication.


Best Regards,
Zhenbin (Robin)




From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Monday, November 18, 2019 1:42 PM
To: idr@ietf.org<mailto:idr@ietf.org>
Subject: [Idr] WG LC draft-ietf-idr-flowspec-path-redirect-10.txt [11/17/2019 to 12/2/2019]

This begins a 2 week WG Last call on draft-idr-flowspec-path-redirect-10.txt from [11/17/2019 to 12/2/2019].

You can obtain the draft at:

https://datatracker.ietf.org/doc/draft-ietf-idr-flowspec-path-redirect/

Consider in your review whether this draft:


  1.  Is compatible with draft-ietf-rfc5575bis-17.txt?
  2.  Whether the draft is useful for deployments of flow specification
  3.  Is this technology ready for deployment?
  4.  Is the write-up of this technology in draft-ietf-idr-flowspec-path-redirect clearly written and ready for publication?

Thank you for considering this draft.

Cheerily, Susan Hares