Re: how well will IDRP nee BGP work?

Tony Li <tli@cisco.com> Tue, 22 August 1995 00:57 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa19372; 21 Aug 95 20:57 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa19368; 21 Aug 95 20:57 EDT
Received: from interlock.ans.net by CNRI.Reston.VA.US id aa23314; 21 Aug 95 20:57 EDT
Received: by interlock.ans.net id AA37184 (InterLock SMTP Gateway 3.0 for iwg-out@ans.net); Mon, 21 Aug 1995 20:51:48 -0400
Message-Id: <199508220051.AA37184@interlock.ans.net>
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-2); Mon, 21 Aug 1995 20:51:48 -0400
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-1); Mon, 21 Aug 1995 20:51:48 -0400
Date: Mon, 21 Aug 1995 17:51:43 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Tony Li <tli@cisco.com>
To: bmanning@isi.edu
Cc: dhaskin@baynetworks.com, bmanning@isi.edu, bgp@ans.net
In-Reply-To: <199508211801.AA48537@interlock.ans.net> (bmanning@ISI.EDU)
Subject: Re: how well will IDRP nee BGP work?

   > I believe that major pain of renumbering is with hosts nor routers. Hence,
   > I guess, some manual re-configuration of routers is acceptable and
   > probably unavoidable.  Do you think otherwise?

   I am not so sure.  Hosts effectivly need to be treated once. The
   routers will be different. The routers carry complex configurations
   and access-lists.  Hand crafting them is hard enough w/o the
   requirement to readjust them every time you, your provider, or any
   of your peers renumbers, particularly when this is done with any
   regularity.  In this case a more simple construct of static routes
   may be easier to manage.

Let's talk reality here:  there are two cases that need to be
considered.  Either the DMZ is being renumbered, or it's an internal
renumbering.  No renumbering is necessary for any prefixes which are
wholly internal to your provider or your peer.  [Yes, if your prefix
changes because your provider's prefix changed, then you renumber...
see case 2.]

If a DMZ is being renumbered, then you may have a number of neighbors
to renumber.  Upload config, run a sed script (in the tradition of
this group), download config.  Manually remove old neighbors when
stable.  Effective thinking time: 10min.

If it's an internal renumbering, then a NAME will only suffice if you
can beat the chicken and egg problem (as has been pointed out) AND if
you have names that are specific to the interface that you want to
peer with (usually a loopback address).  Iterate above procedure for
all BGP peers.

Note that with automatic discovery, some folks might want to consider
how this works in the face of the two hierarchical distribution
techniques.

Tony