[Pals] Progressing draft-busi-pals-pw-cw-stitching-01

Italo Busi <Italo.Busi@huawei.com> Tue, 05 February 2019 14:02 UTC

Return-Path: <Italo.Busi@huawei.com>
X-Original-To: pals@ietfa.amsl.com
Delivered-To: pals@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DF3E1310C4 for <pals@ietfa.amsl.com>; Tue, 5 Feb 2019 06:02:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 sa7L9WktbNOe for <pals@ietfa.amsl.com>; Tue, 5 Feb 2019 06:02:15 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 A652213110A for <pals@ietf.org>; Tue, 5 Feb 2019 06:02:15 -0800 (PST)
Received: from LHREML711-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 81AEC3EE32F674A4070B for <pals@ietf.org>; Tue, 5 Feb 2019 14:02:13 +0000 (GMT)
Received: from LHREML504-MBX.china.huawei.com ([10.201.109.60]) by LHREML711-CAH.china.huawei.com ([10.201.108.34]) with mapi id 14.03.0415.000; Tue, 5 Feb 2019 14:02:09 +0000
From: Italo Busi <Italo.Busi@huawei.com>
To: "pals@ietf.org" <pals@ietf.org>
Thread-Topic: Progressing draft-busi-pals-pw-cw-stitching-01
Thread-Index: AdS9WpkL5kOT97WfRNugi8RYbpVEww==
Date: Tue, 05 Feb 2019 14:02:08 +0000
Message-ID: <91E3A1BD737FDF4FA14118387FF6766B276B14AB@lhreml504-mbx>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.203.246.251]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pals/EC7DavMAlRq5oHhxbtTq47ajgOM>
Subject: [Pals] Progressing draft-busi-pals-pw-cw-stitching-01
X-BeenThere: pals@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Pseudowire And LDP-enabled Services dicussion list." <pals.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pals>, <mailto:pals-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pals/>
List-Post: <mailto:pals@ietf.org>
List-Help: <mailto:pals-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pals>, <mailto:pals-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Feb 2019 14:02:21 -0000

During IETF 103, draft-busi-pals-pw-cw-stitching-01 has been presented and discussed
 
We have received very valid technical comments that we think can be addressed in the future versions of the draft
 
One of the main outstanding comment is about whether the solution proposed in the draft is addressing a real need in deployed networks
 
The draft is proposing a solution that could resolve the issues described in RFC 8469 when PWs are deployed without the CW because an existing T-PE is not capable to insert the CW
 
It is worth noting, as outlined during the IETF 103 discussion, that we are considering only T-PEs which are not capable to insert the CW because of hardware limitations and not T-PEs that are capable to insert the CW but configured not to do so. In the latter case, the solution in RFC 8469 (recommending to enable the use of CW) seems sufficient
 
As outlined by Dave in the meeting notes, more analysis needs to be done on:
	1. the use cases where this function would be used e.g., mobile transport? Ethernet enterprise services? data center interconnect? etc.
	2. In these cases identified, how likely would it be where the TPE would not be upgraded? 
 
Since these issues are related to existing network deployments and future/planned network upgrades, we would appreciate any input from operators about these questions

Thanks in advance

Italo (on behalf of co-authors)