RE: [MIB-DOCTORS] IETF Ops Area interested in context-aware approach?
"David Levi" <dlevi@nortel.com> Thu, 22 February 2007 17:35 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HKHqd-0005e4-Lq; Thu, 22 Feb 2007 12:35:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HKH2q-0001EL-DT for mib-doctors@ietf.org; Thu, 22 Feb 2007 11:43:48 -0500
Received: from zcars04e.nortel.com ([47.129.242.56]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKH2n-0006hC-QZ for mib-doctors@ietf.org; Thu, 22 Feb 2007 11:43:48 -0500
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com [47.103.123.71]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id l1MGZXN29243; Thu, 22 Feb 2007 11:35:33 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MIB-DOCTORS] IETF Ops Area interested in context-aware approach?
Date: Thu, 22 Feb 2007 10:43:36 -0600
Message-ID: <C5A96676FCD00745B64AE42D5FCC9B6E0F8E3C59@zrc2hxm0.corp.nortel.com>
In-Reply-To: <D4D321F6118846429CD792F0B5AF471F2EAB98@DEEXC1U02.de.lucent.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [MIB-DOCTORS] IETF Ops Area interested in context-aware approach?
Thread-Index: AcdWmtomnUUrWIzySAu/VU7li5rSmQAAiXCgAAC+oDA=
From: David Levi <dlevi@nortel.com>
To: "Wijnen, Bert (Bert)" <bwijnen@alcatel-lucent.com>, "Thomas D. Nadeau" <tnadeau@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0e9ebc0cbd700a87c0637ad0e2c91610
X-Mailman-Approved-At: Thu, 22 Feb 2007 12:35:14 -0500
Cc: mib-doctors@ietf.org
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
Errors-To: mib-doctors-bounces@ietf.org
This isn't clear to me either. Are you saying you're using some structure in the contextName? -Dave -----Original Message----- From: Wijnen, Bert (Bert) [mailto:bwijnen@alcatel-lucent.com] Sent: Thursday, February 22, 2007 11:20 AM To: Thomas D. Nadeau Cc: mib-doctors@ietf.org; Romascanu, Dan ((Dan)); david.kessens@nokia.com; Levi, David (SC100:323) Subject: RE: [MIB-DOCTORS] IETF Ops Area interested in context-aware approach? [added David Levi] I do not understand you. contextName is ONE of the paramters as input to the isAccessAllowed ASI which is the interface to VACM. See the figure in sect 3.1. on page 8 of RFC315. Bert > -----Original Message----- > From: Thomas D. Nadeau [mailto:tnadeau@cisco.com] > Sent: donderdag 22 februari 2007 17:01 > To: Wijnen, Bert (Bert) > Cc: mib-doctors@ietf.org; Romascanu, Dan ((Dan)); > david.kessens@nokia.com > Subject: Re: [MIB-DOCTORS] IETF Ops Area interested in context-aware > approach? > > > Because it is not granular enough. Using the VACM allows you to be > more precise about which (disjoint perhaps) pieces of the tree can be > accessed by a particular context. > So what you really need is a combination of contextName + VACM access. > > --Tom > > > > IF you want to use contextNames for multiple instntiations of a MIB > > module, then pls explain to me why the standardized > approach specified > > in the SNMPv3 RFCs is not sufficient or not working? > > > > Bert > > > >> -----Original Message----- > >> From: Thomas D. Nadeau [mailto:tnadeau@cisco.com] > >> Sent: donderdag 22 februari 2007 16:01 > >> To: mib-doctors@ietf.org; Romascanu, Dan ((Dan)); > >> david.kessens@nokia.com > >> Subject: [MIB-DOCTORS] IETF Ops Area interested in context-aware > >> approach? > >> > >> > >> [CC: list pruned to ADs and MIB doctor list] > >> > >> In the meantime, is the IETF's ops area interested in > producing a > >> document (perhaps informational) on how one can do > multiple-contexts > >> using the existing VACM? Cisco has deployed/patented a technology > >> whereby we can do per-context addressing down to the > object/instance > >> level using only the standard VACM and v2c/v3 security > features. If > >> you guys think this would be useful for the IETF, I believe that > >> Cisco would be interested in giving it to the IETF on the > same terms > >> that we did recently in IPFIX with Netflow. > >> > >> I think this would solve a lot of problems related to > having to hack > >> older MIBs to add one or more extra index values, as well as doing > >> this for new ones. The issue there is that one index may not be > >> future-proof. Recently, for instance, multi-topology routing came > >> out, which in effect, requires THREE indexes. Fortunately, the > >> approach I am referring to above doesn't rely on the MIB tables' > >> indexes per se to allow for per-context addressing, so we > were able > >> to use the same approach to address the now 3 levels of virtual > >> indexing needed. The approach I describe should work for arbitrary > >> indexing too, BTW. > >> > >> --Tom > >> > >> > >> > >> > >> > >> On Feb 22, 2007:9:36 AM, at 9:36 AM, Romascanu, Dan ((Dan)) wrote: > >> > >>> > >>> > >>> > >>> > >>> > >>>> -----Original Message----- > >>>> From: Thomas D. Nadeau [mailto:tnadeau@cisco.com] > >>>> Sent: Thursday, February 22, 2007 4:19 PM > >>>> To: Romascanu, Dan (Dan) > >>>> Cc: david.kessens@nokia.com; Vach Kompella; A Kiran Koushik S; > >>>> Townsley Mark; Shane Amante; Wijnen, Bert (Bert); David Levi > >>>> Subject: Re: l2vpn mib interaction with RFC > >>>> > >>>> > >>>> On Feb 22, 2007:12:56 AM, at 12:56 AM, Romascanu, Dan > >> ((Dan)) wrote: > >>>> > >>>>> Tom, > >>>>> > >>>>> 1) I agree with the editors. What are the arguments of > those who > >>>>> suggest copying objects from one MIB module into the L2VPN > >>>> MIB rather > >>>>> than re-using them? > >>>> > >>>> The arguments in favor are simply that this is the most > >> expeditious > >>>> and easiest way of supporting many instances of VPLS bridge > >>>> information. > >>> > >>> - expeditious and easiest for whom? For the people who write the > >>> standard, for those who write implementations or for those > >> who deploy? > >>> - maybe I mis-understood you - by 'copy' you mean take the > >> objects in > >>> the bridge tables with their semantics and adding and index (or > >>> more) to > >>> multiplex among VPN instances? > >>> > >>>> > >>>>> 2) As per RFC 4663 further development of the Bridge MIB > >>>> modules was > >>>>> transferred to the IEEE 802.1 Working Group. The IEEE WG is > >>>> developing > >>>>> separate MIB modules for new IEEE 802.1 protocols like > >> IEEE 802.1ag > >>>>> (Connectivity Fault Management a.k.a. OAM) and is > extending the > >>>>> original Bridge MIB modules as project IEEE 802.1ap now at > >>>> its first > >>>>> Task Group ballot. IEEE 802.1ap is actually including > >>>> re-indexation. I > >>>>> would suggest that you look at what the IEEE are doing. I > >> copy Bert > >>>>> who is also participating in the IEEE 802.1 and David Levi > >>>> who is the > >>>>> editor of the MIB module in IEEE 802.1ap. > >>>> > >>>> What are the timelines for this work, and what is the plan for > >>>> multiple-contexts in these MIBs? > >>> > >>> The projected completion date for the standard is July > >> 2008. I would > >>> suggest that you have a look at the proposal now in TG > >> ballot, because > >>> what you ask for ('multiple-contexts' may or may not be > >> in, it is not > >>> however a goal but rather means for something else I think. > >>> > >>> Dan > >>> > >>> > >>>> > >>>> --Tom > >> > >> _______________________________________________ > >> MIB-DOCTORS mailing list > >> MIB-DOCTORS@ietf.org > >> https://www1.ietf.org/mailman/listinfo/mib-doctors > >> > _______________________________________________ MIB-DOCTORS mailing list MIB-DOCTORS@ietf.org https://www1.ietf.org/mailman/listinfo/mib-doctors
- [MIB-DOCTORS] IETF Ops Area interested in context… Thomas D. Nadeau
- RE: [MIB-DOCTORS] IETF Ops Area interested in con… Wijnen, Bert (Bert)
- Re: [MIB-DOCTORS] IETF Ops Area interested in con… Thomas D. Nadeau
- RE: [MIB-DOCTORS] IETF Ops Area interested in con… Wijnen, Bert (Bert)
- RE: [MIB-DOCTORS] IETF Ops Area interested in con… David Levi