Re: FW: OSPF WG Charter Proposal

Rohit Dube <rohit@XEBEO.COM> Tue, 29 October 2002 20:08 UTC

Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22641 for <ospf-archive@LISTS.IETF.ORG>; Tue, 29 Oct 2002 15:08:59 -0500 (EST)
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <14.00799C1C@cherry.ease.lsoft.com>; Tue, 29 Oct 2002 15:11:19 -0500
Received: from DISCUSS.MICROSOFT.COM by DISCUSS.MICROSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 356404 for OSPF@DISCUSS.MICROSOFT.COM; Tue, 29 Oct 2002 15:11:19 -0500
Received: from 204.192.44.242 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Tue, 29 Oct 2002 15:11:18 -0400
Received: (qmail 10036 invoked from network); 29 Oct 2002 20:11:18 -0000
Received: from bigbird.xebeo.com (192.168.0.21) by lxmail.xebeo.com with SMTP; 29 Oct 2002 20:11:18 -0000
Received: from bigbird.xebeo.com (localhost.localdomain [127.0.0.1]) by bigbird.xebeo.com (8.9.3/8.9.3) with ESMTP id PAA00822; Tue, 29 Oct 2002 15:11:18 -0500
X-Mailer: exmh version 2.1.1 10/15/1999
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-ID: <200210292011.PAA00822@bigbird.xebeo.com>
Date: Tue, 29 Oct 2002 15:11:18 -0500
Reply-To: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
Sender: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
From: Rohit Dube <rohit@XEBEO.COM>
Subject: Re: FW: OSPF WG Charter Proposal
Comments: To: "Singh, Ajay" <ajays@netplane.com>
Comments: cc: "Venkata.Naidu@MARCONI.COM" <Venkata.Naidu@MARCONI.COM>, "acee@REDBACK.COM" <acee@REDBACK.COM>
To: OSPF@DISCUSS.MICROSOFT.COM
In-Reply-To: Message from "Singh, Ajay" <ajays@netplane.com> of "Mon, 28 Oct 2002 22:46:31 EST." <E7E13AAF2F3ED41197C100508BD6A3286044BE@india_exch.hyderabad.mindspeed.com>
Precedence: list

On Mon, 28 Oct 2002 22:46:31 -0500 "Singh, Ajay" writes:
=>Hello Venkata,Acee, Rohit,
=>  With regards to OSPF-TE mib requirements, i would like to differ from what
=>venkata has to say. OSPF - TE requirements as is, are not part of OSPF
=>protocol requirements/ of any use in OSPF networks. Its only that OSPF acts
=>as a transport mechanism to propagate the TE info in the network( which
=>quite often would be a superset of OSPF network(TE links and associated
=>nodes may not be running OSPF for that matter)). Injection( and hence its
=>generation) of this TE info, per se, should not lie in the perview of OSPF
=>group, as the requirements are to be dealt with by the users of the
=>information( e.g connecting MPLS modules, LMP etc) . Hence, is it right to
=>develop the OSPF-TE mib as an OSPF working group item.
=>Please let me know disconnects in my understandings.
=>Thanks
=>Ajay

Ajay,

Acee and I discussed this. I would agree with you. Any OSPF-TE mib is
likely to be equally relevant to ISIS. I would prefer to not get into
specifying this here - if at all, the TEWG can specify (perhaps they
do already) the contents of the TED to be extracted into a MIB.

Regards,
--rohit.

PS: I am cc'ing the list as well. Hope you don't mind.