[OSPF] use of O bit in Hello packets

"Enrico Dutti" <enrico.dutti@marconi.com> Tue, 10 October 2006 13:12 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXHPC-0006NQ-Sr; Tue, 10 Oct 2006 09:12:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXHPB-0006NL-7p for ospf@ietf.org; Tue, 10 Oct 2006 09:12:21 -0400
Received: from smtpoutuk02.marconi.com ([128.87.251.113]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXHP9-0000FV-Ov for ospf@ietf.org; Tue, 10 Oct 2006 09:12:21 -0400
Received: from cvdgwy02.uk.marconicomms.com (cvis27.uk.marconicomms.com [128.87.251.110]) by smtpoutuk02.marconi.com (8.12.11.20060614/8.12.11) with ESMTP id k9ADCBrV032031 for <ospf@ietf.org>; Tue, 10 Oct 2006 14:12:11 +0100 (envelope-from enrico.dutti@marconi.com)
Sensitivity:
To: ospf@ietf.org
X-Mailer: Lotus Notes Release 5.0.12 February 13, 2003
Message-ID: <OF425B659B.E2850724-ONC1257203.00472391-C1257203.0048E602@uk.marconicomms.com>
From: Enrico Dutti <enrico.dutti@marconi.com>
Date: Tue, 10 Oct 2006 15:08:54 +0200
X-MIMETrack: Serialize by Router on CVDGWY02/S/EXT/MC1(Release 5.0.13a |April 8, 2004) at 10/10/2006 14:12:15
MIME-Version: 1.0
Content-type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Subject: [OSPF] use of O bit in Hello packets
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

Hi all,

I need a clarification regarding the use of the O bit in OSPF's hello
packets (rfcs 2328 + 2370).

Should (or must) an opaque capable router set the O bit to 1 in his Hello
packets?

Let's say I have an OSPF router that must use opaque objects in order work
correctly.
Is it correct/allowable if this router rejects a neighbour because it
doesn't set the O bit in the Hello packet it transmits?

thank you

Enrico Dutti



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