RE: Feedback needed: retiring MOSPF and other specs?

"Susan Hares" <skh@nexthop.com> Mon, 02 January 2006 12:36 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EtOvQ-0007Zq-8G; Mon, 02 Jan 2006 07:36:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EoXGd-0001jq-Ek for rtg-dir@megatron.ietf.org; Mon, 19 Dec 2005 21:30:19 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24806 for <rtg-dir@ietf.org>; Mon, 19 Dec 2005 21:29:15 -0500 (EST)
Received: from gateout02.mbox.net ([165.212.64.22]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EoXIx-0000bp-NG for rtg-dir@ietf.org; Mon, 19 Dec 2005 21:32:44 -0500
Received: from gateout02.mbox.net (gateout02.mbox.net [165.212.64.22]) by gateout02.mbox.net (Postfix) with ESMTP id 2A63E178A; Tue, 20 Dec 2005 02:29:52 +0000 (GMT)
Received: from gateout02.mbox.net [127.0.0.1] by gateout02.mbox.net via mtad (C8.MAIN.3.27E) with ESMTP id 769JLTcdY0095Mo2; Tue, 20 Dec 2005 02:29:51 GMT
Received: from gateout02.mbox.net [127.0.0.1] by gateout02.mbox.net via mtad (C8.MAIN.3.27E) with ESMTP id 768JLTcdx0149Mo2; Tue, 20 Dec 2005 02:29:48 GMT
X-USANET-Routed: 2 gwsout-vs R:localhost:1825
Received: from GW1.EXCHPROD.USA.NET [165.212.116.254] by gateout02.mbox.net via smtad (C8.MAIN.3.27I); Tue, 20 Dec 2005 02:29:48 GMT
X-USANET-Source: 165.212.116.254 IN skh@nexthop.com GW1.EXCHPROD.USA.NET
X-USANET-MsgId: XID010JLTcdx4991Xo2
Received: from VS4.EXCHPROD.USA.NET ([10.116.208.142]) by GW1.EXCHPROD.USA.NET with Microsoft SMTPSVC(6.0.3790.211); Mon, 19 Dec 2005 19:29:48 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7232.53
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 19 Dec 2005 19:29:46 -0700
Message-ID: <6F44D7F6B24A8F4DA0AB46C9BE924F020295C0C1@VS4.EXCHPROD.USA.NET>
Thread-Topic: Feedback needed: retiring MOSPF and other specs?
Thread-Index: AcYE+kiW99+5oHdZQ4W0J+/EZulByAAEuF2Q
From: Susan Hares <skh@nexthop.com>
To: Radia Perlman <Radia.Perlman@sun.com>, Alex Zinin <zinin@psg.com>
X-OriginalArrivalTime: 20 Dec 2005 02:29:48.0894 (UTC) FILETIME=[3FC09FE0:01C6050D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 02 Jan 2006 07:36:27 -0500
Cc: rtg-dir@ietf.org, Acee Lindem <acee@cisco.com>, Rohit Dube <dube_rohit@yahoo.com>
Subject: RE: Feedback needed: retiring MOSPF and other specs?
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
Sender: rtg-dir-bounces@ietf.org
Errors-To: rtg-dir-bounces@ietf.org

Alex:

I think there are some environments where MOSPF might be useful.
How do we want to judge this?

sue

-----Original Message-----
From: rtg-dir-bounces@ietf.org [mailto:rtg-dir-bounces@ietf.org] On
Behalf Of Radia Perlman
Sent: Monday, December 19, 2005 7:10 PM
To: Alex Zinin
Cc: rtg-dir@ietf.org; Acee Lindem; Rohit Dube
Subject: Re: Feedback needed: retiring MOSPF and other specs?

Seems reasonable. What's the downside of doing this?

Radia



Alex Zinin wrote:

>Acee, Rohit, RTG-DIR members:
>
>  In case you didn't see this doc:
>
http://www.ietf.org/internet-drafts/draft-ietf-newtrk-decruft-experiment
-02.txt
>
>  I'm holding a DISCUSS on this. The doc suggests to retire MOSPF and a
>  bunch of other specs to Historic. I need to know your opinion on
this.
>
>  Here's what I have on my list of questionable retirements:
>
>  
>
>>      RFC1378 (The PPP AppleTalk Control Protocol (ATCP))
>>      RFC1469 (IP Multicast over Token-Ring Local Area Networks)
>>      RFC1582 (Extensions to RIP to Support Demand Circuits)
>>      RFC1584 (Multicast Extensions to OSPF)
>>      RFC1598 (PPP in X.25)
>>      RFC1755 (ATM Signaling Support for IP over ATM)
>>    
>>
>
>  I'd like to hear opinions on this.
>
>  
>