Re: [OSPF] Removal of MOSPF from OSPFv3
Erblichs <erblichs@earthlink.net> Fri, 03 August 2007 20:55 UTC
Return-path: <ospf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IH4At-0005lF-Jt; Fri, 03 Aug 2007 16:55:07 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IH4As-0005l8-Ab for ospf@ietf.org; Fri, 03 Aug 2007 16:55:06 -0400
Received: from elasmtp-spurfowl.atl.sa.earthlink.net ([209.86.89.66]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IH4Ar-0007ky-QI for ospf@ietf.org; Fri, 03 Aug 2007 16:55:06 -0400
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=ntI+ou+GYg+lOExBR/mW5OrF46XOUerqMyMETZjZU1IeW+8Z1DFwieEVnW7ktQlj; h=Received:Message-ID:Date:From:X-Sender:X-Mailer:X-Accept-Language:MIME-Version:To:CC:Subject:References:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [68.164.83.247] (helo=earthlink.net) by elasmtp-spurfowl.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1IH4Aq-0005aG-AM; Fri, 03 Aug 2007 16:55:04 -0400
Message-ID: <46B396B2.1B1E441B@earthlink.net>
Date: Fri, 03 Aug 2007 13:57:22 -0700
From: Erblichs <erblichs@earthlink.net>
X-Sender: "Erblichs" <erblichs@earthlink.net@smtpauth.earthlink.net> (Unverified)
X-Mailer: Mozilla 4.72 [en]C-gatewaynet (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Anton Smirnov <asmirnov@cisco.com>
Subject: Re: [OSPF] Removal of MOSPF from OSPFv3
References: <66A3A59B-F3DA-437C-9107-67C36A4B93F7@redback.com> <4B7DAC3FEFD35D4A96BDD011699050140A4245F9@zrtphxm1.corp.nortel.com> <93E269EB-87EB-4B6F-B212-B3E15C049B55@redback.com> <46B21BEF.F72A2FB2@earthlink.net> <D6ACB2DD-BBB5-44FA-9B41-B7B4FB594810@redback.com> <46B25A86.72B967B9@earthlink.net> <46B2D4AC.9080608@teamlog.com> <46B2DE57.8090402@cisco.com>
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 074f60c55517ea841aa676d7e74259b7b3291a7d08dfec79ab41d01c2ae56ce0b47d5ab0349919ba350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 68.164.83.247
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: OSPF List <ospf@ietf.org>
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
Errors-To: ospf-bounces@ietf.org
Group, First, doesn't removal of MOSPF from a well-known RFC remove it from the use by multiple vendors? IMO, this work would not be done if their is belief that MOSPF has strong backing. Who can raise their hands and state that most OSPFv3 capable routers don't have at least 1 MOSPF CLI command? I think that the CLI commands will conflict and need to be changed if re-use is done. This non-support is awareness of MOSPF and that is all is needed for breakage!!!!! How many of these CLI commands are with routers that are no longer supported? It was my undestanding of a couple of years ago that MOSPF was basicly NOT classified as "historic", but was being treated as such within a WG meeting a couple of years ago. This was one of multiple multicast items. However, IFF we are going for re-use of the capability bit, then why don't we go for the re-use of the MOSPF LSA type value? They both have defined meanings and if you have no-issues with one, shouldn't you expect no issues with the other? Just looking it from the extreme case and I don't recommend this!!!! Minimally, DON"T ALL need to be DEPRECATED including the MOSPF RFC for v3, if any re-use is done for the publicly defined pieces. Thus, IMO available workarounds remove the need for re-use and allows the cruft to exist WITHOUT additional headaches that MIGHT follow the removal of MOSPF in OSPFv3. This is the secondary definition of an obsolete public interace and is one reason why private interfaces are created. Mitchell Erblich ------------------ Anton Smirnov wrote: > > Hi, > with OSPFv2 most implementations did not implement MOSPF (shall I > say MOSPFv2) and the same will probably be true for OSPFv3/MOSPFv3. So I > think it is very reasonable that we want to separate mandatory part of > OSPFv3 from optional (and so far not very well specified) MOSPFv3. > We are not banning MOSPFv3 work completely. If there is interest in > MOSPFv3 it can be taken as separate work by interested parties. > > Thanks, > > Anton > > Vincent Nogues wrote: > > Hi, > > > > I don't know any MOSPF implementation for IPv6. However, maybe, we will > > developp such an implementation in the coming months. This project is > > not yet definitive, so I would appreciate if this removal could be > > postponed. > > > > Thanks, > > > > --------------------------------------------------- > > > > *Vincent NOGUES* > > > > --------------------------------------------------- > > _______________________________________________ OSPF mailing list OSPF@ietf.org https://www1.ietf.org/mailman/listinfo/ospf
- [OSPF] Removal of MOSPF from OSPFv3 Acee Lindem
- RE: [OSPF] Removal of MOSPF from OSPFv3 Daniel Joyal
- Re: [OSPF] Removal of MOSPF from OSPFv3 Acee Lindem
- Re: [OSPF] Removal of MOSPF from OSPFv3 Erblichs
- Re: [OSPF] Removal of MOSPF from OSPFv3 Acee Lindem
- Re: [OSPF] Removal of MOSPF from OSPFv3 Erblichs
- Re: [OSPF] Removal of MOSPF from OSPFv3 Erblichs
- Re: [OSPF] Removal of MOSPF from OSPFv3 Acee Lindem
- Re: [OSPF] Removal of MOSPF from OSPFv3 Acee Lindem
- Re: [OSPF] Removal of MOSPF from OSPFv3 Vincent Nogues
- Re: [OSPF] Removal of MOSPF from OSPFv3 Anton Smirnov
- Re: [OSPF] Removal of MOSPF from OSPFv3 Acee Lindem
- Re: [OSPF] Removal of MOSPF from OSPFv3 Erblichs
- Re: [OSPF] Removal of MOSPF from OSPFv3 Russ White
- Re: [OSPF] Removal of MOSPF from OSPFv3 Erblichs
- Re: [OSPF] Removal of MOSPF from OSPFv3 Russ White
- Re: [OSPF] Removal of MOSPF from OSPFv3 Erblichs
- Re: [OSPF] Removal of MOSPF from OSPFv3 Acee Lindem