Re: [Pce] Quick review of draft-chen-pce-sr-ingress-protection-00

Huaimo Chen <huaimo.chen@futurewei.com> Sun, 21 July 2019 03:50 UTC

Return-Path: <huaimo.chen@futurewei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23A881200EF; Sat, 20 Jul 2019 20:50:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 OyO0K9fyYQSk; Sat, 20 Jul 2019 20:50:54 -0700 (PDT)
Received: from NAM05-DM3-obe.outbound.protection.outlook.com (mail-dm3nam05on071c.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe51::71c]) (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 0D66E12006A; Sat, 20 Jul 2019 20:50:53 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=AE5NO4MCjwryhceikGXLAmhrUDDFWJez512IOxIPgPMjyNTp02YPDZ3sE/7GM0MSNr0Ni4iJjZIVy9Fm7hJioGZN4UpshOK5CXxstKDkMf0Y7Czn9/vxNAtzKgxgQ54bElAjgHg7vYKF4BMAF9+2OtKYO8q2aA1gAK5G7bwp4WdBGeW4aBeylH0thtDW8QJnwJ8y4P03SylEbI3XnYIVpk9aFyB9L98sNORcQ40EyEAdtj3Cus0repwqMkDw1doBeWlfSRBbmWpbeLQmGEODVoOtK1QOg/BLtqs02yt+CkiwrUsd250jmqOl6vaKbcKxdhvtgRjP0I5q6PWvp7TZ+Q==
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=EhmOEYUSCCCFZD2ODkp4BB7gX8sNps585hEshNRxJh0=; b=GG+F01S5g8zbRP7PdasZmi0WgLrbMHaX6iFSoyCi3rVysSffXXJAGAg52tZht68dspkhf9RgWRXlgEZm5lfwjbUYj7zd5RlIoJayhqGeu71qQidyTw0kfG4+K1/pmYdLcDSAOrWADSJccS0YRMbxydNbb3ACWTIWEp9PkbO09XppCv7/1v996ZS8r5qBdQd4dmXC6uiVTvfJzfinvvy8BIg19vdmStVSgewYL7vmO7f08e5H34lbVdMbX/nw1Zrv2j30+QwU1/teqiuw2zaFb/9Q0Erm5CW0sqygHcMWF/ayT+xnVmf0SvKw0qFVeADvSaP8/i0NX//4Exo8HSLG3A==
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=EhmOEYUSCCCFZD2ODkp4BB7gX8sNps585hEshNRxJh0=; b=ddCueagg3FpzMtFNOv85gov1y4O4hsLoBrpTeGFqyVjVwx+RlOPHo6h58cd9oEVHKZMZyz0CzlJALUYRkJPiyEaSPSNxGFa6XTrvg3uzHyrAXD5ac4QnD+c+7WyAcK1bgYLx7iOwPFFLwNkcmmt76AF8jvp9dBSaWlqR5I7FZ6M=
Received: from MN2PR13MB3470.namprd13.prod.outlook.com (10.255.237.83) by MN2PR13MB3341.namprd13.prod.outlook.com (10.255.236.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2115.9; Sun, 21 Jul 2019 03:50:50 +0000
Received: from MN2PR13MB3470.namprd13.prod.outlook.com ([fe80::4dd2:d307:a7ef:2279]) by MN2PR13MB3470.namprd13.prod.outlook.com ([fe80::4dd2:d307:a7ef:2279%4]) with mapi id 15.20.2115.003; Sun, 21 Jul 2019 03:50:50 +0000
From: Huaimo Chen <huaimo.chen@futurewei.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>, "draft-chen-pce-sr-ingress-protection@ietf.org" <draft-chen-pce-sr-ingress-protection@ietf.org>
CC: "pce@ietf.org" <pce@ietf.org>
Thread-Topic: Quick review of draft-chen-pce-sr-ingress-protection-00
Thread-Index: AQHVOyHR6KsiyEksUk+wcOY03TpnPqbUcrDQ
Date: Sun, 21 Jul 2019 03:50:50 +0000
Message-ID: <MN2PR13MB3470115E28AB02A01B0C4F2EF2C50@MN2PR13MB3470.namprd13.prod.outlook.com>
References: <CAB75xn7s2b3rp4Ef+V35-_hHRzhYTHM1dxi3uF7MScFaH4bJYg@mail.gmail.com>
In-Reply-To: <CAB75xn7s2b3rp4Ef+V35-_hHRzhYTHM1dxi3uF7MScFaH4bJYg@mail.gmail.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: [73.114.233.24]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ecf0e03b-ec3e-42e6-6f60-08d70d8e9f3d
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR13MB3341;
x-ms-traffictypediagnostic: MN2PR13MB3341:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <MN2PR13MB3341F555BFD9EFC446BF42E2F2C50@MN2PR13MB3341.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0105DAA385
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(39840400004)(396003)(346002)(376002)(366004)(136003)(13464003)(189003)(199004)(37854004)(52536014)(44832011)(64756008)(66556008)(66476007)(66946007)(102836004)(6246003)(2906002)(7736002)(14454004)(305945005)(53546011)(6506007)(86362001)(3846002)(68736007)(99286004)(5660300002)(486006)(76116006)(66066001)(66446008)(6116002)(256004)(14444005)(2501003)(110136005)(55016002)(316002)(6306002)(33656002)(478600001)(45080400002)(966005)(6436002)(53936002)(76176011)(7696005)(11346002)(71200400001)(71190400001)(8936002)(74316002)(229853002)(4326008)(476003)(186003)(25786009)(9686003)(81156014)(81166006)(8676002)(26005)(446003); DIR:OUT; SFP:1102; SCL:1; SRVR:MN2PR13MB3341; H:MN2PR13MB3470.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-message-info: Ez2vSIynAwQWXHWyLNQnZexDchEJaGqgq/YeqrMtKfSKnNTZ3W5ap4cYMr+dG+BFic2+43v3fz5WlN0liPmxV5Be9+XMqa33fF7Tue8rtzwBKIueP3XsZEtwKSyxjUX5gnGthmGcxEu7v+MLad4vm5Nh4n9Xd4z5+sHmcjSDzhhBZvNwz0QNDJ66wm5SMHs0lVkeAjleT1nPG76opHsQjn/zPfYUzz3y36tpHaYHGTWfHojvZ8fn3/5zc5UN3gYuquyqBw6MT+lfkul6hv+Tk7PuI1Jpe9kkDW1TqQjhVqR+Vr+5GBePaUjzK05xku7oZhAHnnyx+gGC1W/fNZV7MHwtBGjXX4oP4LVsW2AGpKNXY4CbLenPqX6WETrXSKAmljwHNl2dH9wwczG6I52zru8C9TWV6wVJQmwTG5j6YGU=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ecf0e03b-ec3e-42e6-6f60-08d70d8e9f3d
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Jul 2019 03:50:50.2806 (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: hchen@futurewei.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR13MB3341
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/Qb_8loOzcmrymzRJsisrmaISTXQ>
Subject: Re: [Pce] Quick review of draft-chen-pce-sr-ingress-protection-00
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Jul 2019 03:50:56 -0000

Hi Dhruv,

    Thank you very much for your valuable comments. 
    My answers/explanations are inline below with prefix [HC].

Best Regards,
Huaimo
-----Original Message-----
From: Dhruv Dhody <dhruv.ietf@gmail.com> 
Sent: Monday, July 15, 2019 11:27 AM
To: draft-chen-pce-sr-ingress-protection@ietf.org
Cc: pce@ietf.org
Subject: Quick review of draft-chen-pce-sr-ingress-protection-00

Hi Authors,

I did a quick review of your I-D, but some key questions came up, it would be nice if they could be clarified before hand.

(1) It needs to be made clear that why does backup egress needs to know about the details of the primary SR path at the primary ingress?
Since things are driven by PCE/controller and there is no signalling, the motivation needs to be different than RFC 8424 for RSVP-TE.  IMHO the only reason for backup ingress to be aware of these details would be to detect the failure of the primary ingress itself. And the benefit offered by that isn't clear.

[HC] The information about the primary SR path at the primary ingress is not needed at the backup ingress. We will remove the text related to this from the draft. 
For the backup ingress to detect the failure of the primary ingress, it should know the IP address of the primary ingress node. 
If the primary SR path carries a service which is identified by a service ID or label, then this service ID or label should be sent to the backup ingress node. 
We will update the draft to clarify these.

(2) Once the motivations are cleared up, then we should explore the use of existing techniques like PCEP-Flowspec [1] instead of defining new sub-TLVs for traffic description.  I see you have a few new things like virtual network but not clear how they would be used and why are tightly coupled for this use-case.

[HC] Regarding to using existing Flowspec or new sub-TLVs for traffic description, it seems that there should have some discussions. The latter seems more general and powerful.
For virtual network, we will consider it further.

I hope you would focus on these aspects during your presentation.
Discussion on the list would be even better.

[HC] We will focus on these in our presentation accordingly.

Thanks,
Dhruv

[1] https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-pce-pcep-flowspec-03&amp;data=02%7C01%7Chuaimo.chen%40futurewei.com%7C732f5b6ab36d4d187f6b08d70938f2cb%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C636988012506152829&amp;sdata=FnMU0LBRfXa5fI32smojCNrtC3%2BnKn13ofmMb7nnhlU%3D&amp;reserved=0