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

jnc@mercury.lcs.mit.edu (Noel Chiappa) Mon, 10 September 2007 02:25 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 1IUYxv-0003fr-2Q; Sun, 09 Sep 2007 22:25:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IUYxt-0003ff-Gd for ram@iab.org; Sun, 09 Sep 2007 22:25:29 -0400
Received: from mercury.lcs.mit.edu ([18.26.0.122]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IUYxs-0005io-Ct for ram@iab.org; Sun, 09 Sep 2007 22:25:29 -0400
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 2DF6A87322; Sun, 9 Sep 2007 22:25:28 -0400 (EDT)
To: ram@iab.org
Subject: Re: [RAM] Number of DFZ routers - radical improvement of BGP unlikely
Message-Id: <20070910022528.2DF6A87322@mercury.lcs.mit.edu>
Date: Sun, 09 Sep 2007 22:25:28 -0400
From: jnc@mercury.lcs.mit.edu
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
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>

    > At the very least a new protocol would have to support the situation
    > where the new protocol is spoken in the middle and BGP both on the left
    > and on the right.

Right, and if the fundamental concepts of the new design are very different
from those of BGP (e.g. it exchages maps, rather than routing table entries),
that translation, forwards and backwards, could be rather tricky.

    > It gets even more interesting when two clouds speaking the new protocol
    > are separated by a BGP cloud.

Now you're either i) limiting the new system to having the capabilities of
BGP (in which case, you lose a lot of the point of doing something new), or
ii) you have to accept that two such discontiguous regions of New Stuff
simply don't get all the benefits of New Stuff until they somehow manage to
connect directly.


    > I don't think an internet-wide map based protocol is feasible

We will have to agree to differ... :-)

    > A system where there is a map of the "center" of the network (as seen
    > from a given vantage point) where mapping to/from prefix tables
    > happens at the edges of the map would be very interesting.

It happens that map-based system are ideally suited to building systems where
eveyone has a different view of the network...

	Noel

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