Re: Re: [OSPF] draft-ietf-ospf-ospfv3-graceful-restart-03

"Vivek Dubey" <vivek_ospf@rediffmail.com> Wed, 03 May 2006 03:59 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fb8Wm-0008GU-JH; Tue, 02 May 2006 23:59:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fb8Wl-0008BL-59 for ospf@ietf.org; Tue, 02 May 2006 23:59:51 -0400
Received: from [203.199.83.135] (helo=rediffmail.com) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Fb8Wi-0008VW-4L for ospf@ietf.org; Tue, 02 May 2006 23:59:51 -0400
Received: (qmail 17007 invoked by uid 510); 3 May 2006 03:58:46 -0000
Date: Wed, 03 May 2006 03:58:46 -0000
Message-ID: <20060503035846.17006.qmail@webmail45.rediffmail.com>
Received: from unknown (203.126.136.220) by rediffmail.com via HTTP; 03 may 2006 03:58:46 -0000
MIME-Version: 1.0
From: Vivek Dubey <vivek_ospf@rediffmail.com>
To: Acee Lindem <acee@cisco.com>
Subject: Re: Re: [OSPF] draft-ietf-ospf-ospfv3-graceful-restart-03
X-Spam-Score: 1.6 (+)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: ospf@ietf.org
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Vivek Dubey <vivek_ospf@rediffmail.com>
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="===============1580512786=="
Errors-To: ospf-bounces@ietf.org

Acee,
I agree/understand the, reasons to keep Interface-Id same across restarts.
But the current phrasing seems to imply that reason for preserving Interface-Id is to keep "the pre-restart and post-restart LSAs same".

The phrasing used in explanation below is more clear.

Thanks
Vivek


On Wed, 03 May 2006 Acee Lindem wrote :
>Vivek,
>
>Vivek Dubey wrote:
>
>>Section 3.2:
>>If this were not the case, the pre-restart and post-restart LSAs wouldn't be the same and the restart would be disruptive.
>>
>><vivek> If "post-restart" here means "after router undergoing restart has exited/exiting graceful-restart", it is supposed to reoriginate LSAs as per Section 2.3 RFC 3623. Description in Section 2.3 RFC 3623 does not mandate the contents to be same. Than why do pre-restart and post-restart LSAs need to be same?
>>
>>Preservation of Interface IDs have more to do with figuring out whether restarting router has re-established all its adjacencies.
>>  
>Since the interface ID is in the link data for OSPFv3 router LSAs, a change in interface ID
>could result in a mismatch between neighbor adjacency state for the restarting router and
>the pre-restart router LSA. Synchronizing the change across the restarting router and
>the helping routers would be very difficult (if not next to impossible) and would probably
>result in unreachability or premature graceful restart termination. It is much better for the
>restarting router to preserve this state across restarts.
>
>Hope this helps,
>Acee
>
>>-Vivek
>>
>>
>>  
>>  
>>------------------------------------------------------------------------
>>
>>_______________________________________________
>>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