IETF Logo Mail Archive

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

Thomas Nadeau <tnadeau@lucidvision.com> Mon, 19 May 2014 14:11 UTC

Return-Path: <tnadeau@lucidvision.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 452201A038D for <l2vpn@ietfa.amsl.com>; Mon, 19 May 2014 07:11:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level:
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651, 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 oILjSmy1uzvP for <l2vpn@ietfa.amsl.com>; Mon, 19 May 2014 07:11:06 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id AA1531A005C for <l2vpn@ietf.org>; Mon, 19 May 2014 07:11:05 -0700 (PDT)
Received: from [172.30.1.206] (c-98-247-226-85.hsd1.wa.comcast.net [98.247.226.85]) by lucidvision.com (Postfix) with ESMTP id 5C92127B17B0; Mon, 19 May 2014 10:11:03 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_C9A50079-FE83-4150-9145-FB9D4457A7AF"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Representation of VPLS attachment circuits in the VPLS MIB draft
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <b8fe93b3b39d4bb78dd64bbac8aec4cb@AM3PR03MB612.eurprd03.prod.outlook.com>
Date: Mon, 19 May 2014 10:11:13 -0400
Message-Id: <4F06F912-87F9-4D78-B685-000FA9FD6C0D@lucidvision.com>
References: <b8fe93b3b39d4bb78dd64bbac8aec4cb@AM3PR03MB612.eurprd03.prod.outlook.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/771j3MEoUIb5LsLPuPJwls3ptAk
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: Mon, 19 May 2014 14:11:13 -0000

	
	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> wrote:

> Hi all,
> I’ve looked up the current version of draft-ietf-l2vpn-vpls-mib 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
> Mobile: 054-9266302

v2.23.0 | Report a Bug | By Email