[L2sm] Support of and interworking with legacy L2VPN types

"Adrian Farrel" <adrian@olddog.co.uk> Wed, 11 October 2017 13:02 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: l2sm@ietfa.amsl.com
Delivered-To: l2sm@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 5C53913318B for <l2sm@ietfa.amsl.com>; Wed, 11 Oct 2017 06:02:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.08
X-Spam-Status: No, score=0.08 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id JfnDaTYwV77h for <l2sm@ietfa.amsl.com>; Wed, 11 Oct 2017 06:02:43 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E260513430F for <l2sm@ietf.org>; Wed, 11 Oct 2017 06:02:39 -0700 (PDT)
Received: from asmtp5.iomartmail.com (localhost.localdomain []) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id v9BD2b2r012465 for <l2sm@ietf.org>; Wed, 11 Oct 2017 14:02:37 +0100
Received: from 950129200 ( []) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id v9BD2aMv012442 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <l2sm@ietf.org>; Wed, 11 Oct 2017 14:02:37 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: l2sm@ietf.org
Date: Wed, 11 Oct 2017 14:02:38 +0100
Message-ID: <05b801d34291$37876e70$a6964b50$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdNCkSmpJ7cPChOgSN2ry5YAuT50cQ==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-
X-TM-AS-Result: No--7.026-10.0-31-10
X-imss-scan-details: No--7.026-10.0-31-10
X-TMASE-MatchedRID: aQCt577mlyRkgQopOf2aEtOEZs/2oH3cW9oi9MZ8/xLvxSNLwtVQB00B k5DM7WKlpzaCfOWoVYptkfvwyItc5S9FtW7XfHueq1ZJZ2z+SbascK/K2DlvjhahL68yPcDbOex 2qLEoLQYjypnGhZoY9YdziXCvHmFESSOWVJeuO1A5f9Xw/xqKXVsKO+9Zlb5Jxq9PbUOwsP9QSF bL1bvQASAHAopEd76v/J6QUQ6MgenKQWrlQuoIgDLHNZLD/CklamwyQ1cv1ip85DxNPaUO5Q==
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2sm/NOHa_t1fqD5M5APQSVORR_gTt_Q>
Subject: [L2sm] Support of and interworking with legacy L2VPN types
X-BeenThere: l2sm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "The Layer Two Virtual Private Network Service Model \(L2SM\)" <l2sm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2sm>, <mailto:l2sm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l2sm/>
List-Post: <mailto:l2sm@ietf.org>
List-Help: <mailto:l2sm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2sm>, <mailto:l2sm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Oct 2017 13:02:44 -0000

Another issue on our list was whether we should support legacy VPN services like

At the interim we decided that while there is a lot of legacy deployment, there
are also four things to consider:

1. Legacy deployments are, erm, already deployed. They are static and don't need
more work for operational commissioning.

2. New deployments of legacy services are very, very rare.

3. Migration to new L2VPN services does happen, but is covered by the existing

4. Interworking between legacy and new services is something so unusual that we
should not work on it.

As a result we determined to not support any form of ATM PVC.

Again, please shout if you have an issue with this.