IETF Logo Mail Archive

RE: Representation of VPLS attachment circuits in the VPLS MIB draft

Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Tue, 20 May 2014 15:46 UTC

Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: l2vpn@ietfa.amsl.com
Delivered-To: l2vpn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D6841A06FA for <l2vpn@ietfa.amsl.com>; Tue, 20 May 2014 08:46:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 giEVpg6dqI38 for <l2vpn@ietfa.amsl.com>; Tue, 20 May 2014 08:46:36 -0700 (PDT)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1lp0015.outbound.protection.outlook.com [213.199.154.15]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFA4F1A076C for <l2vpn@ietf.org>; Tue, 20 May 2014 08:46:34 -0700 (PDT)
Received: from AM3PR03MB612.eurprd03.prod.outlook.com (10.242.110.144) by AM3PR03MB530.eurprd03.prod.outlook.com (10.242.109.154) with Microsoft SMTP Server (TLS) id 15.0.944.11; Tue, 20 May 2014 15:46:32 +0000
Received: from AM3PR03MB612.eurprd03.prod.outlook.com ([10.242.110.144]) by AM3PR03MB612.eurprd03.prod.outlook.com ([10.242.110.144]) with mapi id 15.00.0944.000; Tue, 20 May 2014 15:46:31 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Thomas Nadeau <tnadeau@lucidvision.com>, "Giles Heron (giles.heron@gmail.com)" <giles.heron@gmail.com>
Subject: RE: Representation of VPLS attachment circuits in the VPLS MIB draft
Thread-Topic: Representation of VPLS attachment circuits in the VPLS MIB draft
Thread-Index: Ac9zRXZtGaEhhrgKQHa1aq4D/fY9OAAJrpqAAADWPaAANDPUAA==
Date: Tue, 20 May 2014 15:46:30 +0000
Message-ID: <625bd69ef3be4c8f9c61292c760b28fb@AM3PR03MB612.eurprd03.prod.outlook.com>
References: <b8fe93b3b39d4bb78dd64bbac8aec4cb@AM3PR03MB612.eurprd03.prod.outlook.com> <4F06F912-87F9-4D78-B685-000FA9FD6C0D@lucidvision.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.234.56.21]
x-forefront-prvs: 02176E2458
x-forefront-antispam-report: SFV:NSPM; SFS:(428001)(199002)(189002)(377454003)(24454002)(252514010)(53754006)(77096999)(79102001)(76176999)(76482001)(80022001)(74316001)(54356999)(83072002)(33646001)(15202345003)(81342001)(21056001)(20776003)(19300405004)(19625215002)(85852003)(4396001)(64706001)(19580395003)(31966008)(74502001)(50986999)(86362001)(74662001)(66066001)(46102001)(16236675002)(99396002)(76576001)(19580405001)(2656002)(83322001)(92566001)(15975445006)(19609705001)(77982001)(87936001)(81542001)(101416001)(24736002)(217873001)(562404015); DIR:OUT; SFP:; SCL:1; SRVR:AM3PR03MB530; H:AM3PR03MB612.eurprd03.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (: ecitele.com does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Alexander.Vainshtein@ecitele.com;
Content-Type: multipart/alternative; boundary="_000_625bd69ef3be4c8f9c61292c760b28fbAM3PR03MB612eurprd03pro_"
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/5oumP1r1VnP7JB4skiwKo4jlSYo
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, "kkoushik@cisco.com" <kkoushik@cisco.com>, "rohit.mediratta@alcatel-lucent.com" <rohit.mediratta@alcatel-lucent.com>, Rotem Cohen <Rotem.Cohen@ecitele.com>
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Layer 2 Virtual Private Networks <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2vpn/>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 May 2014 15:46:40 -0000

Hi all,
This is a gentle reminder that I still have not seen any answers to my question - or, to be more specific, an answer that refers to specific objects defined in the VPLS MIB draft.
I am adding Giles (who was the shepherd of this document) and Nabil to this thread.


For the reference, the L3VPN MIB (RFC 4382<http://www.rfc-editor.org/rfc/rfc4382.txt>) defines a dedicated table (mplsL3VpnIfConfTable) that performs this functionality.

I would expect something similar in this draft, but could not find it in there.

Regards,
       Sasha
Email: Alexander.Vainshtein@ecitele.com
Mobile: 054-9266302

From: Alexander Vainshtein
Sent: Monday, May 19, 2014 5:40 PM
To: 'Thomas Nadeau'
Cc: kkoushik@cisco.com; rohit.mediratta@alcatel-lucent.com; l2vpn@ietf.org; Gideon Agmon; Rotem Cohen
Subject: RE: Representation of VPLS attachment circuits in the VPLS MIB draft

Tom,
Lots of thanks for a prompt response.

Unfortunately ACs as IfMIB entries are not mentioned anywhere in the draft.
I would expect something similar to the PW Binding table for binding ACs to a VPLS instance, but there is no such thing there.

And while the draft mentions that it uses the definitions for RFC 2863 in the text, the actual  IMPORT clauses do not list this RFC at all!


Could you please elaborate?

Regards, and lots of thanks in advance,
       Sasha
Email: Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>
Mobile: 054-9266302

From: Thomas Nadeau [mailto:tnadeau@lucidvision.com]
Sent: Monday, May 19, 2014 5:11 PM
To: Alexander Vainshtein
Cc: kkoushik@cisco.com<mailto:kkoushik@cisco.com>; rohit.mediratta@alcatel-lucent.com<mailto:rohit.mediratta@alcatel-lucent.com>; l2vpn@ietf.org<mailto:l2vpn@ietf.org>; Gideon Agmon; Rotem Cohen
Subject: Re: Representation of VPLS attachment circuits in the VPLS MIB draft


          ACs are attached to the VPLS instances and are represented as IfMIB entries.

          --Tom


On May 19, 2014:5:34 AM, at 5:34 AM, Alexander Vainshtein <Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>> wrote:

Hi all,
I've looked up the current version of draft-ietf-l2vpn-vpls-mib<https://datatracker.ietf.org/doc/draft-ietf-l2vpn-vpls-mib/?include_text=1> and I did not find there any explicit reference to (local) attachment circuits of VPLS. (Neither the term "attachment circuit" nor its common abbreviation "AC" appear in the text.)

At the same time, to the best of my understanding, attachment circuits form a substantial component of any VPLS instance.

Did I miss something?

If yes, could somebody please explain how one could indicate that, say, a specific VLAN on a specific Ethernet port belongs to a given VPLS instance as defined in the draft?

If not, could somebody please explain why presenting such functionality is considered unnecessary in the VPLS MIB?

Regards, lots of thanks in advance,
       Sasha
Email: Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>
Mobile: 054-9266302

v2.8.7 | Report a Bug | By Email