Re: Status of "alternative ABR implementations" draft?

Acee Lindem <acee@REDBACK.COM> Thu, 22 August 2002 14:06 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 KAA26300 for <ospf-archive@LISTS.IETF.ORG>; Thu, 22 Aug 2002 10:06:01 -0400 (EDT)
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <6.006E5A1D@cherry.ease.lsoft.com>; Thu, 22 Aug 2002 10:07:25 -0400
Received: from DISCUSS.MICROSOFT.COM by DISCUSS.MICROSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 86988 for OSPF@DISCUSS.MICROSOFT.COM; Thu, 22 Aug 2002 10:07:25 -0400
Received: from 155.53.12.9 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Thu, 22 Aug 2002 10:07:24 -0400
Received: from redback.com (login003.redback.com [155.53.12.55]) by prattle.redback.com (Postfix) with ESMTP id 8E46D473CCE for <OSPF@DISCUSS.MICROSOFT.COM>; Thu, 22 Aug 2002 07:07:23 -0700 (PDT)
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: <Pine.A41.4.31.0208221455480.49770-100000@pandora.inf.elte.hu>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID: <3D64F018.30704@redback.com>
Date: Thu, 22 Aug 2002 10:07:20 -0400
Reply-To: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
Sender: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
From: Acee Lindem <acee@REDBACK.COM>
Subject: Re: Status of "alternative ABR implementations" draft?
To: OSPF@DISCUSS.MICROSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit

Nohl Attila Rajmund wrote:

> Hello!


Hello NAR,


>
> I would like to know the current status of the
> draft-ietf-ospf-abr-alt-04.txt document. It is listed on the workgroup's
> homepage at http://www.ietf.org/html.charters/ospf-charter.html but
> according to its header, it expired last September.


I believe the draft is going to be published as an informational RFC. I'll
ping Alex to see where we stand with the last set of comments.

>
>>From the draft it looks like that some vendors already implemented this
> draft. I know, that in the GNU zebra routing software, one can configure
> the router to use one of the techniques specified in the document. Do
> you have any information about how widespread is the implementation of
> this draft among the router vendors?


Note that this is an informational RFC (vis-a-vis, a standards track RFC).
A properly designed OSPF network would not require the behavior described
in the draft. As a co-author, my primary motivation for implementing the
alternate ABR behavior was a satisfy a strong customer requirement.

In answer to your question, I'm not sure how many router vendors (other
than the ones listed in the draft) have implemented it.


>
>                                 Bye,NAR
>
>


--
Acee