[Pals] Progressing draft-busi-pals-pw-cw-stitching-01
Italo Busi <[email protected]>
| Newsgroups | gmane.ietf.pwe3 |
|---|---|
| Message-ID | <91E3A1BD737FDF4FA14118387FF6766B276B14AB@lhreml504-mbx> |
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)