Re: [PWE3] Question about PW MIBs
Yaakov Stein <yaakov_s@rad.com> Sun, 03 June 2012 10:51 UTC
Return-Path: <yaakov_s@rad.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77E3921F8686 for <pwe3@ietfa.amsl.com>; Sun, 3 Jun 2012 03:51:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level:
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g4QfidF9ojEB for <pwe3@ietfa.amsl.com>; Sun, 3 Jun 2012 03:51:52 -0700 (PDT)
Received: from rad.co.il (mailrelay01.rad.co.il [62.0.23.252]) by ietfa.amsl.com (Postfix) with ESMTP id 5124621F8685 for <pwe3@ietf.org>; Sun, 3 Jun 2012 03:51:48 -0700 (PDT)
Received: from Internal Mail-Server by MailRelay01 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 3 Jun 2012 13:33:44 +0300
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by EXRAD5.ad.rad.co.il ([192.114.24.28]) with mapi id 14.01.0323.003; Sun, 3 Jun 2012 13:51:45 +0300
From: Yaakov Stein <yaakov_s@rad.com>
To: Apostolos Manolitzas <manap@intracom.gr>, "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [PWE3] Question about PW MIBs
Thread-Index: AQHNPv0kTBp+f7YtokyyIasTh/pOfJbobaLw
Date: Sun, 03 Jun 2012 10:51:45 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC9043D6B83@EXRAD5.ad.rad.co.il>
References: <4FC71A3B.7020000@intracom.gr>
In-Reply-To: <4FC71A3B.7020000@intracom.gr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.17.141.36]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Commtouch-Refid: str=0001.0A0B0203.4FCB41C2.0056,ss=1,fgs=0
Subject: Re: [PWE3] Question about PW MIBs
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jun 2012 10:51:52 -0000
Regarding the CESoPSN and TDMoIP MIB definitions, those drafts were merged into 5604. See all the places where 5604 mentions XXX where XXX = CESoPSN or TDMoIP. (I checked with Orly to make sure that my understanding is correct.) Regarding Ethernet, the IETF is not responsible for Ethernet, and thus PWE3 did not define Ethernet as a PSN - only MPLS, L2TPv2/IP, and for the TDM drafts - UDP/IP. MEF defined TDM PWs over Ethernet in MEF-8, but I don't recall any MIB work on it. I will check. Y(J)S -----Original Message----- From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Apostolos Manolitzas Sent: Thursday, May 31, 2012 10:14 To: pwe3@ietf.org Subject: [PWE3] Question about PW MIBs Hello all, based on the RFC5604 there should exist MIBs in the service layer for the CESoPSN and TDMoIP module, but those where drafts that where deprecated. Is there any other standard option for them? What should be used for management? Some custom approach perhaps? Furthermore, there is nothing available for managing psn as Ethernet, even the IANAPwPsnTypeTC doesn't support the Ethernet as psn, why is that? Is there any standard/draft alternative MIB that should be used to fill the gap in the PSN layer? best regards, -Apostolos Manolitzas _______________________________________________ pwe3 mailing list pwe3@ietf.org https://www.ietf.org/mailman/listinfo/pwe3
- [PWE3] Question about PW MIBs Apostolos Manolitzas
- Re: [PWE3] Question about PW MIBs Yaakov Stein
- Re: [PWE3] Question about PW MIBs Daniel Cohn