RE: Internal Update Process of BGP4
Anoop Ghanwani <anoop@cosinecom.com> Wed, 09 May 2001 18:38 UTC
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id OAA21969 for <idr-archive@nic.merit.edu>; Wed, 9 May 2001 14:38:24 -0400 (EDT)
Received: by segue.merit.edu (Postfix) id ED3E45DF59; Wed, 9 May 2001 14:23:11 -0400 (EDT)
Delivered-To: idr-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56) id 77B1C5DF67; Wed, 9 May 2001 14:09:50 -0400 (EDT)
Received: from exchsrv1.cosinecom.com (mail.cosinecom.com [63.88.104.16]) by segue.merit.edu (Postfix) with ESMTP id A48885E168 for <idr@merit.edu>; Wed, 9 May 2001 13:56:38 -0400 (EDT)
Received: by exchsrv1.cosinecom.com with Internet Mail Service (5.5.2653.19) id <KR6J53WR>; Wed, 9 May 2001 10:56:29 -0700
Message-ID: <6CECAF1A722ED842B24EC8EDA5B07604019D61@exchsrv4>
From: Anoop Ghanwani <anoop@cosinecom.com>
To: 'deepak_srivastava' <deepak_srivastava@infy.com>, idr@merit.edu
Subject: RE: Internal Update Process of BGP4
Date: Wed, 09 May 2001 10:56:37 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0D8B1.64AAA590"
Sender: owner-idr@merit.edu
Precedence: bulk
> You will know that x3 is your best route for putting in Loc-RIB, ONLY > AFTER > phase2, but its written in draft and rfc1771 both, that > internal updates > can > be sent (after/as part of) phase 1 itself. I think all that this is saying is that a peer should send its updates based on its set of best (active) routes without waiting forever to receive an update from its neighbor...it just gets the process going. Every active route has already been through the path selection criteria. What do you think is a more approriate algorithm? -Anoop
- RE: Internal Update Process of BGP4 deepak_srivastava
- Re: Internal Update Process of BGP4 proto man
- Re: Internal Update Process of BGP4 deepak_srivastava
- RE: Internal Update Process of BGP4 Anoop Ghanwani