Re: [RAM] Number of DFZ routers - radical improvement of BGP unlikely

jnc@mercury.lcs.mit.edu (Noel Chiappa) Fri, 07 September 2007 01:47 UTC

Return-path: <ram-bounces@iab.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ITSwk-0004CG-JQ; Thu, 06 Sep 2007 21:47:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ITSwk-0004CB-2c for ram@iab.org; Thu, 06 Sep 2007 21:47:46 -0400
Received: from mercury.lcs.mit.edu ([18.26.0.122]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ITSwi-0002ld-Tp for ram@iab.org; Thu, 06 Sep 2007 21:47:46 -0400
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 773DF872F3; Thu, 6 Sep 2007 21:47:44 -0400 (EDT)
To: ram@iab.org
Subject: Re: [RAM] Number of DFZ routers - radical improvement of BGP unlikely
Message-Id: <20070907014744.773DF872F3@mercury.lcs.mit.edu>
Date: Thu, 06 Sep 2007 21:47:44 -0400
From: jnc@mercury.lcs.mit.edu
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ram@iab.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing and Addressing Mailing List <ram.iab.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ram>
List-Post: <mailto:ram@iab.org>
List-Help: <mailto:ram-request@iab.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=subscribe>
Errors-To: ram-bounces@iab.org

    > From: Iljitsch van Beijnum <iljitsch@muada.com>

    > The question is whether it would be easier to replace it. So far, I
    > can't think of anyone else other than myself speaking out in favor of
    > that, or even entertaining the question seriously. :-)

Really? :-)

    > Obviously a new protocol would have to be able to interact with BGP and
    > be not much worse at talking BGP than a native speaker.

Well, "interact with BGP" and "talk BGP" sound like two very different things
to me - unless by "talk BGP" you mean "emulate a BGP speaker".

The thing is that if you have a system with a fundamentally different model
of the world (e.g. map-based, instead of route-table based), the interface
between it and BGP is necessarily going to be something of a kludge, and any
emulation is perforce going to be be something less than stellar.

	Noel

_______________________________________________
RAM mailing list
RAM@iab.org
https://www1.ietf.org/mailman/listinfo/ram