IETF Logo Mail Archive

Re: [OSPF] Removal of MOSPF from OSPFv3

Russ White <riw@cisco.com> Tue, 07 August 2007 14:05 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 1IIPh4-0003o8-FI; Tue, 07 Aug 2007 10:05:54 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IIPh3-0003nL-Fg for ospf@ietf.org; Tue, 07 Aug 2007 10:05:53 -0400
Received: from xmail11.myhosting.com ([168.144.250.171]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IIPh3-0007OQ-5q for ospf@ietf.org; Tue, 07 Aug 2007 10:05:53 -0400
Received: (qmail 3292 invoked from network); 7 Aug 2007 14:05:52 -0000
Received: from unknown (HELO [192.168.100.205]) (Authenticated-user:_russ@riw.us@[65.190.218.139]) (envelope-sender <riw@cisco.com>) by xmail11.myhosting.com (qmail-ldap-1.03) with ESMTPA for <erblichs@earthlink.net>; 7 Aug 2007 14:05:51 -0000
Message-ID: <46B87C39.3030705@cisco.com>
Date: Tue, 07 Aug 2007 10:05:45 -0400
From: Russ White <riw@cisco.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Erblichs <erblichs@earthlink.net>
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> <7EA6C521-AA32-4E8E-8196-E28BC38E9F42@redback.com> <46B7A291.9000601@cisco.com> <46B7A6DA.7125122E@earthlink.net>
In-Reply-To: <46B7A6DA.7125122E@earthlink.net>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


>      Ok, now what do you do with 100s of documents outside
>      of this RFC that says the bits are used for MOSPF?

Are there 100's? I can't imagine there are many for MOSPF for v3, rather
than v2.... Can you point to some?

>      Group, no one needs to implement MOSPF for v3, just that
>      vendors have to believe that if someone did impliment it,
>      THEN they would be using those bits..
> 
>      That makes those bits UN-USEABLE for anything else.

There are other bits, no?

:-)

Russ

- --
riw@cisco.com CCIE <>< Grace Alone

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGuHw5ER27sUhU9OQRAthJAJ9VS9yi3QcTjdpVkNvszqt683j6xwCfWDOj
VHl3vYjyc2GLp+DY0KCxl5k=
=L/j9
-----END PGP SIGNATURE-----

_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www1.ietf.org/mailman/listinfo/ospf

v2.23.0 | Report a Bug | By Email