[OSPF] Extensions to OSPF for Advertising Optional Router Capabilities

Erblichs <erblichs@earthlink.net> Tue, 12 December 2006 17:28 UTC

Received: from [] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GuBQs-0005H6-3y; Tue, 12 Dec 2006 12:28:46 -0500
Received: from [] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GuBQp-0005Gt-VL for ospf@ietf.org; Tue, 12 Dec 2006 12:28:43 -0500
Received: from elasmtp-kukur.atl.sa.earthlink.net ([]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuBQn-0002Ib-2A for ospf@ietf.org; Tue, 12 Dec 2006 12:28:43 -0500
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=IPeR5PMpp1VXrZRaoofD/z9cTdjG18rZOI5PJjnw+ELVmqSUFkERi4x8YZNt9x2a; h=Received:Message-ID:Date:From:X-Sender:X-Mailer:X-Accept-Language:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [] (helo=earthlink.net) by elasmtp-kukur.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1GuBQm-0004XH-Do for ospf@ietf.org; Tue, 12 Dec 2006 12:28:40 -0500
Message-ID: <457EE558.C26ACBB9@earthlink.net>
Date: Tue, 12 Dec 2006 09:22:32 -0800
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: ospf@ietf.org
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 074f60c55517ea841aa676d7e74259b7b3291a7d08dfec79454e0d2f0e8c2e3bcef107dd0774da18350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Subject: [OSPF] Extensions to OSPF for Advertising Optional Router Capabilities
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


	It has come to my attention about a possible
	inconsistency or ordering of non-consistent
	options now exist.

	Let me clarify... Graceful Restart example

		This new draft introduces new options / capabilities
		(Graceful Restart) with bit 0 and bit 1. These two bits
		alone can cause confusion, but with the additional
		requirement that GR requires Opaque LSA support we have
		a THIRD bit involvement.

		In some document, there needs clarification as to at
		least GR, whether the Opaque bit should first be checked
		before either of these two other bits to validate
		whether GR support is possible.

			The first doc (GRACE) never suggested the Opaque
			bit LSA check before a GR-LSA was initially adv...

		Secondly, there needs to be a clarification as what
		should be done if a router originates Grace-LSAs that
		originated this LSA and did NOT set bit 0 
		(OSPF graceful restart capable)

		Thirdly, does the adv having not set bit 1 
		(OSPF graceful restart helper) SUGGEST all full adj 
		nbrs that with to enter GR and understand this bit,
		check that this bit was set? And not send out a Grace-LSA
		if it wasn't...

		Fourth, does the support of either bit assume that the other
		bit is supported? If we set bit 1, does that mean bit "0" must
		be set?

	2) General comment / questions

	 A) What is meant by "OSPF routers MAY optionally advertise their
optional capabilities"?

		Thus, what is "gained" by advertising say the GR bits?

		Can a rtr optionally support its optional advs?
			Or stated another way..

		Can a rtr that has advertised GR functionality, support this
		to only a subset of its nbrs?
		Ex: Can a DR only support a rtr that is a BDR doing a GR and not
		    any DRothers doing a GR??????

	Thank you,
		Mitchell Erblich

OSPF mailing list