Re: status of RFC 2154
Acee Lindem <acee@CISCO.COM> Fri, 22 April 2005 15:15 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 LAA26563 for <ospf-archive@LISTS.IETF.ORG>; Fri, 22 Apr 2005 11:15:01 -0400 (EDT)
Received: from vms.dc.lsoft.com (209.119.0.2) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <15.010216D9@cherry.ease.lsoft.com>; Fri, 22 Apr 2005 11:15:01 -0400
Received: by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 14.3) with spool id 67639626 for OSPF@PEACH.EASE.LSOFT.COM; Fri, 22 Apr 2005 11:15:00 -0400
Received: from 64.102.122.148 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0l) with TCP; Fri, 22 Apr 2005 11:15:00 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-1.cisco.com with ESMTP; 22 Apr 2005 11:26:25 -0400
X-IronPort-AV: i="3.92,124,1112587200"; d="scan'208"; a="45730347:sNHT25859288"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j3MFETeL008031 for <OSPF@PEACH.EASE.LSOFT.COM>; Fri, 22 Apr 2005 11:14:57 -0400 (EDT)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 22 Apr 2005 11:14:46 -0400
Received: from [10.82.241.23] ([10.82.241.23]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 22 Apr 2005 11:14:45 -0400
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
X-Accept-Language: en-us, en
MIME-Version: 1.0
References: <d9243d13050422040343d476ef@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Apr 2005 15:14:45.0532 (UTC) FILETIME=[04504DC0:01C5474E]
Message-ID: <426914E6.8060902@cisco.com>
Date: Fri, 22 Apr 2005 11:14:46 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Acee Lindem <acee@CISCO.COM>
Subject: Re: status of RFC 2154
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To: <d9243d13050422040343d476ef@mail.gmail.com>
Precedence: list
Content-Transfer-Encoding: 7bit
Hi Deepak, Deepak Dandekar wrote: >Hello, >I tried searching for this RFC on the OSPF charter, but didn't find >any information. > > It is an experimental RFC that went through a different process than standards track WG documents. Another example would be RFC 2676. >Is there any vendor who has implemented this RFC? > I don't know of any commercial implementations. However, I haven't looked too hard either. >Is there any need to >implement this RFC?? > > I wouldn't think so. However, I'm somewhat biased since I don't really think this is a good idea. I certainly don't want to quell any innovation. Hope this helps, Acee >Appreciate your help. > >thanks, >deepak. > > >
- status of RFC 2154 Deepak Dandekar
- Re: status of RFC 2154 Acee Lindem