Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers

"Darrel Lewis (darlewis)" <> Mon, 11 January 2010 20:32 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C01DD3A6951 for <>; Mon, 11 Jan 2010 12:32:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id xR-b9lvv9lFB for <>; Mon, 11 Jan 2010 12:32:21 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id ED85A3A6926 for <>; Mon, 11 Jan 2010 12:32:20 -0800 (PST)
Authentication-Results:; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEABsZS0urR7H+/2dsb2JhbADDHJQEhC8E
X-IronPort-AV: E=Sophos;i="4.49,258,1262563200"; d="scan'208";a="231972477"
Received: from ([]) by with ESMTP; 11 Jan 2010 20:32:18 +0000
Received: from ( []) by (8.13.8/8.14.3) with ESMTP id o0BKWIKp013194; Mon, 11 Jan 2010 20:32:18 GMT
Received: from ([]) by with Microsoft SMTPSVC(6.0.3790.3959); Mon, 11 Jan 2010 12:32:18 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 11 Jan 2010 12:32:18 -0800
Message-ID: <>
In-Reply-To: <>
Thread-Topic: [lisp] LISP Interworking: Proxy Egress Tunnel Routers
Thread-Index: AcqQvfPcv7cADXebQCGrbD8d0pFoEQCOBobQ
References: <> <>
From: "Darrel Lewis (darlewis)" <>
To: <>
X-OriginalArrivalTime: 11 Jan 2010 20:32:18.0858 (UTC) FILETIME=[2B8DE0A0:01CA92FD]
Subject: Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 11 Jan 2010 20:32:21 -0000

> I do not understand the two application scenarios and how PETRs can 
> help. Could you explain that in more detail, please?


Today when an ITR receives a packet on its local interface with the
destination address of a non-lisp site, today it forwards it without
encapsulation.  To be specific, an ITR has a map-cache that contains
both 'positive' and 'negative' cache entries.  When a packet's
destination address matches a positive entry, it is encapsulated to the
locators in the mapping.  When a packet's destination address matches a
negative entry, the packet is forwarded natively without encapsulation
(to the next hop).

However, there are a couple of cases where this non-encapsulated packet
will get dropped.

First, the Provider Edge router may be doing some sort of strict
filtering on the source address of packets sent by the CE device (the
ITR).  Thus packets with the source of an EID may be dropped because the
PE router does not have an route to the EID out the interface.  

Second, the Provider Edge router may only support IPv4.  So an ITR
sending a IPv6 packet will obviously fail.

The Proxy ETR allows an ITR to encapsulate packets that match 'negative'
map-cache entries to a destination that can bypass both the above
situations.  In the first case, the encapsulated packet's outer header
has a correct source address.  In the second case, the encapsulated
outer header would be an IPv4 packet.  Of course, this implies that the
Proxy ETR has dual stack external connectivity (post decapsulation) the
Proxy ETR's upstream router(s) use loose mode uRPF.

Hope this helps explain the situation a little bit more clearly.