Re: OSPF WG Charter Proposal

Acee Lindem <acee@REDBACK.COM> Tue, 29 October 2002 02:33 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 VAA07640 for <ospf-archive@LISTS.IETF.ORG>; Mon, 28 Oct 2002 21:33:35 -0500 (EST)
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <23.00798103@cherry.ease.lsoft.com>; Mon, 28 Oct 2002 21:35:55 -0500
Received: from DISCUSS.MICROSOFT.COM by DISCUSS.MICROSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 352275 for OSPF@DISCUSS.MICROSOFT.COM; Mon, 28 Oct 2002 21:35:55 -0500
Received: from 155.53.12.9 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Mon, 28 Oct 2002 21:35:55 -0400
Received: from redback.com (login005.redback.com [155.53.12.60]) by prattle.redback.com (Postfix) with ESMTP id 5BDE4FC055 for <OSPF@DISCUSS.MICROSOFT.COM>; Mon, 28 Oct 2002 18:35:53 -0800 (PST)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3
X-Accept-Language: en-us
MIME-Version: 1.0
References: <39469E08BD83D411A3D900204840EC5576341E@vie-msgusr-01.dc.fore.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID: <3DBDF375.6010000@redback.com>
Date: Mon, 28 Oct 2002 21:33:25 -0500
Reply-To: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
Sender: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
From: Acee Lindem <acee@REDBACK.COM>
Subject: Re: OSPF WG Charter Proposal
To: OSPF@DISCUSS.MICROSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit

Naidu, Venkata wrote:

> Rohit,
>
> -> => 3. "OSPF TE" and "OSPF Hitless Restart" MIBs must be
> -> =>    considered as separate drafts. Recent OSPFv2 MIB only
> -> =>    talks about Opaque LSAs - but content carried in those
> -> =>    LSAs are not specified in any MIB. I am be willing
> -> =>    to write those drafts - what is your opinion, Kireeti/Padma ?
> ->
> -> I was considering reflecting OSPF-TE in a MIB too. And this could
> -> be a potential item for this or a future. But is there an operator
> -> burning for this stuff?
>
>   Yes :-) there are definite requests I encounter for OSPF-TE MIB.
>   If not Hitless Restart MIB, we do need OSPF-TE mib. As you know,
>   it is potential candidate for deployment in MPLS (apart from VPNs).
>
> -> =>
> -> => 4. "Flooding over Parallel Point-to-Point Links" can be
> -> =>    considered as an informational RFC.
> ->
> -> What draft are you referring to?
>
>   draft-ietf-ospf-ppp-flood-01.txt


Venkata,

This draft has expired and I don't think there are any plans
to re-submit it.

>
> --
> Venkata.
>
>

Thanks,
--
Acee