Re: [RAM] ViP: Anycast ITRs in the DFZ & mobile tunnels

Robin Whittle <rw@firstpr.com.au> Fri, 15 June 2007 07:06 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 1Hz5su-0001iu-Ur; Fri, 15 Jun 2007 03:06:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hz5st-0001im-Fn for ram@iab.org; Fri, 15 Jun 2007 03:06:15 -0400
Received: from gair.firstpr.com.au ([150.101.162.123]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hz5ss-0002Wo-Tg for ram@iab.org; Fri, 15 Jun 2007 03:06:15 -0400
Received: from [10.0.0.8] (zita.firstpr.com.au [10.0.0.8]) by gair.firstpr.com.au (Postfix) with ESMTP id E227F59E4B; Fri, 15 Jun 2007 17:06:11 +1000 (EST)
Message-ID: <46723A5A.9000809@firstpr.com.au>
Date: Fri, 15 Jun 2007 17:06:02 +1000
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: ram@iab.org
Subject: Re: [RAM] ViP: Anycast ITRs in the DFZ & mobile tunnels
References: <46720DED.9090608@firstpr.com.au> <1FDC4EF3-97D4-4CA7-A7EF-5012D4EA5DB8@cisco.com>
In-Reply-To: <1FDC4EF3-97D4-4CA7-A7EF-5012D4EA5DB8@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc:
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

Hi Dino,

You wrote:

> Can you tell me what is different here than LISP plus the use of
> NERD?

  http://tools.ietf.org/html/draft-lear-lisp-nerd

My understanding of LISP may be faulty, but I thought that the IP
addresses which are used as locators do not come from prefixes which
are advertised via BGP.  Therefore, to my understanding, if a host
in an edge network wants to send a packet to such an IP address, the
edge network needs a LISP ITR function in one or more routers -
either inside the edge network or at the border router.

Maybe what I wrote only exposes my misunderstanding of LISP and of
other aspects of routing and addressing.  If so, hopefully this will
have some educational value for others.

My mention of anycast is probably wrong.  What I want to achieve is
multiple routers such as transit or border routers to perform the
ITR function, and my plan was that they would all advertise the same
prefix: 22.22.0.0/16.  I don't know if there is a precedent for this
with BGP or whether it is impossible, but anycast is a separate
technology which is probably not needed here.

>>      However, it would be technically possible to have the ITR
>>      function performed by a single-homed border router or by
>>      specialised router which has only a single interface which
>>      connects to a transit router or to any border router.  

. . .

> Tell me what is different here than a LISP ITR running on a CE router
> with BGP enabled?

There's no technical difference.  Its just that, as I understand it,
 with LISP, the edge network needs to run an ITR if its users are to
be able to send packets to LISP-mapped addresses.

I am going out and will reply more fully in the next day or so.

   - Robin


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