Re: [OSPF] OSPF GR query
"sujay gupta" <sujay.ietf@gmail.com> Tue, 02 January 2007 05:43 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H1cQO-00035b-Hk; Tue, 02 Jan 2007 00:43:00 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H1cQN-00035N-1w for ospf@ietf.org; Tue, 02 Jan 2007 00:42:59 -0500
Received: from nf-out-0910.google.com ([64.233.182.191]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H1cQK-0007nf-8Y for ospf@ietf.org; Tue, 02 Jan 2007 00:42:59 -0500
Received: by nf-out-0910.google.com with SMTP id l36so4827004nfa for <ospf@ietf.org>; Mon, 01 Jan 2007 21:42:55 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=j4ruY9rOpGjbGtjT1ioIT6vxZVjBJB+pqT4xfQN2R2Lnxkzr624aJNbxe60deWKiEtPIS+wVX3YrtsWbV55SjwLieKs1N/wpwlmEEi60iCyHh1cpRMnrHvUBIdS7UXG9CKgF1klL6ImDVLM0gUdExkx2CzkJzP8u4kVK6ZOy28w=
Received: by 10.49.107.3 with SMTP id j3mr9573800nfm.1167716575395; Mon, 01 Jan 2007 21:42:55 -0800 (PST)
Received: by 10.49.42.14 with HTTP; Mon, 1 Jan 2007 21:42:55 -0800 (PST)
Message-ID: <b33c82d0701012142h2f8399e7ie2f06713e91f7026@mail.gmail.com>
Date: Tue, 02 Jan 2007 11:12:55 +0530
From: sujay gupta <sujay.ietf@gmail.com>
To: Acee Lindem <acee@cisco.com>
Subject: Re: [OSPF] OSPF GR query
In-Reply-To: <4575B97C.90801@cisco.com>
MIME-Version: 1.0
References: <988EE2C769AC284ABAE9328BFC10703F011AAD88@ZMY16EXM66.ds.mot.com> <45252069.10200@cisco.com> <b33c82d0610260041v216237d4w653d1042b9ec6bb@mail.gmail.com> <4575B97C.90801@cisco.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: a4e5f67c5e230eddf754446d1a2201a4
Cc: 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>
Content-Type: multipart/mixed; boundary="===============0283714220=="
Errors-To: ospf-bounces@ietf.org
Hi Acee, all, A late reply on this thread. Some comments with relevant text. <snip> No - The presumption is when you reach FULL state you don't need to "quit" helping - you have "finished" helping. Over the years, there have been a few situations that could have been better documented - however, this never caused any confusion in the past. <snip> I'm not sure what the network picture looks like but a helper router can always terminate graceful restart by flooding an inconsistent router or network LSA to the restarting router. <snip/> While going with the basic OSPF protocol working, when the helper exits. -before reaching Full State would be to regenerate LSA's, giving a snapshot of the incomplete state with the Restarting router, causing an "inconsistent" lsa generation which in turn would cause the restarting router exit GR. -after reaching Full State would be to regenerate LSA's, but this time a duped LSA reporting "inconsistent" states, which in turn would cause the restarting router to exit GR. While I immediately see 'wee' bit of an ethical problem by this approach(for it looks more like a hack ;), it is still a way of explicit signaling, works for me! Some other ways could have been "a one-way hello" or "lls signaling". Some more text. <snip> Over the years, there have been a few situations that could have been better documented - however, this never caused any confusion in the past. <snip/> Acee, with my limited experience in the OSPF WG, I have had and seen confusions. Please note RFC3623 Exit GR procedures (Section 3.2) does not entail the helper GR to produce inconsistent LSA's, an addendum should have a better future rather than raising the same queries again. There have been some more issues raised on the GR and update by Mitchell, which I shall shortly address in a separate e-mail. Best Regards & HNY'07, -Sujay On 12/5/06, Acee Lindem <acee@cisco.com> wrote: > > Hi Sujay, > sujay gupta wrote: > > Hi Acee, > > A late mail on this thread. > > > > given the scenario if R3-R1 is a stub area > > and the incoming LSA is a type-5, even with strict LSA > > checking enabled will not exit Helper mode. > I'm not sure what the network picture looks like but a helper > router can always terminate graceful restart by flooding an > inconsistent router or network LSA to the restarting router. > > Thanks, > Acee > > > > > It can be a nice idea to give some explicit notification > > by R2 to R1 about exiting helper mode. > > > > As rightly pointed by you the above conditions and more > > has been causing some confusion for some time. > > Our proposal ; > > > http://tools.ietf.org/wg/ospf/draft-holla-ospf-update-graceful-restart-02.txt > > > > hopefully resolves this. > > Could we add this as an addendum/reference to RFC3623?, purely an > > add-on. > > Best Regards. > > Sujay > > > > On 10/5/06, Acee Lindem <acee@cisco.com> wrote: > >> > >> Khan Amir-G20247 wrote: > >> > Hi Ace > >> > > >> > But reaching to a FULL state is not one of the conditions for > >> Helper to > >> > quit Helper mode, I guess a Helper who has reached > >> > to FULL state with its restarting router will wait for Grace LSAs > >> to be > >> > flushed or GR timeout to happen for exiting Helper mode. > >> > > >> No - The presumption is when you reach FULL state you don't need to > >> "quit" > >> helping - you have "finished" helping. Over the years, there have been > a > >> few situations that could have been better documented - however, this > >> never > >> caused any confusion in the past. > >> > >> Thanks, > >> Acee > >> > >> > Regards > >> > Aamir > >> > > >> > > >> > -----Original Message----- > >> > From: Acee Lindem [mailto:acee@cisco.com] > >> > Sent: Thursday, October 05, 2006 8:00 PM > >> > To: Khan Amir-G20247 > >> > Cc: ospf@ietf.org > >> > Subject: Re: [OSPF] OSPF GR query > >> > > >> > Hello Amir, > >> > > >> > Khan Amir-G20247 wrote: > >> > > >> >> > >> >> > >> >> Hi > >> >> > >> >> I have query related to OSPF Graceful Restart. > >> >> > >> >> Consider this scenario: > >> >> > >> >> > >> >> > >> >> - Three Routers R1, R2 and R3 connected via Broadcast networks. > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> - Where R1 is a DR on both the segments, where as R2 and R3 are in > >> >> DR-other > >> >> - Now R1 wants to perform GR, R2 and R3 agrees to be its Helpers. > >> >> - Now after restart R1 will try to form adjacency with both R2 and > >> R3. > >> >> > >> > > >> > > >> >> - Lets say R1 and R2 had become FULL, while R1 and R3 had reached > >> >> Exstart state. Now at this time R2 receives an LSA (any type 1-5 > >> and > >> >> 7, from some other router existing in the same area, not pictured > >> >> here) which he needs to flood to R1. > >> >> - This will force R2 to quit Helper Status, while R1 and R3 are > still > >> >> in process of forming adjacency. > >> >> > >> >> > >> > Since he has reached FULL state, he is no longer a helper router. > >> > > >> >> Considering above scenario, my doubts are: > >> >> > >> >> - How will R1 come to know that its Helper R2 has quit? > >> >> > >> >> > >> > Since he has reached FULL state, he is no longer a helper router. > >> > > >> >> - Will the adjacency between R1 and R2 needs to go down, as R2 quits > >> >> helper mode? > >> >> > >> >> > >> > No > >> > > >> >> - Will this effect the adjacency formation of R1 and R3? > >> >> > >> >> > >> > No. R3 MAY exit helper status and re-originate a new router LSA if he > >> > receives the new LSA before reaching FULL state with R1 AND he is has > >> > strict-LSA-checking configured. > >> > > >> > Hope this helps, > >> > Acee > >> > > >> >> > >> >> > >> >> Regards > >> >> Aamir > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> ---------------------------------------------------------------------- > >> >> -- > >> >> > >> >> _______________________________________________ > >> >> OSPF mailing list > >> >> OSPF@ietf.org > >> >> https://www1.ietf.org/mailman/listinfo/ospf > >> >> > >> >> > >> > > >> > > >> > >> _______________________________________________ > >> OSPF mailing list > >> OSPF@ietf.org > >> https://www1.ietf.org/mailman/listinfo/ospf > >> > > >
_______________________________________________ OSPF mailing list OSPF@ietf.org https://www1.ietf.org/mailman/listinfo/ospf
- [OSPF] OSPF GR query Khan Amir-G20247
- RE: [OSPF] OSPF GR query Don Goodspeed
- Re: [OSPF] OSPF GR query Acee Lindem
- [OSPF] OSPF GR query Khan Amir-G20247
- Re: [OSPF] OSPF GR query Acee Lindem
- RE: [OSPF] OSPF GR query Khan Amir-G20247
- Re: [OSPF] OSPF GR query Acee Lindem
- Re: [OSPF] OSPF GR query sujay gupta
- [OSPF] OSPF GR query Khan Amir-G20247
- Re: [OSPF] OSPF GR query Abhay D.S
- Re: [OSPF] OSPF GR query sujay gupta
- Re: [OSPF] OSPF GR query Vivek Dubey
- Re: [OSPF] OSPF GR query Abhay D.S
- Re: [OSPF] OSPF GR query Vivek Dubey
- Re: [OSPF] OSPF GR query Acee Lindem
- Re: [OSPF] OSPF GR query Abhay D.S
- Re: [OSPF] OSPF GR query sujay gupta
- Re: [OSPF] OSPF GR query Acee Lindem