Re: [lisp] LISP-GPE Review

Dino Farinacci <> Thu, 08 March 2018 18:32 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C1AE212706D for <>; Thu, 8 Mar 2018 10:32:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.175
X-Spam-Status: No, score=0.175 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_IMAGE_ONLY_24=1.618, HTML_IMAGE_RATIO_04=0.556, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id O_dxo5CS94TB for <>; Thu, 8 Mar 2018 10:32:01 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:400e:c00::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4C32C126D74 for <>; Thu, 8 Mar 2018 10:32:01 -0800 (PST)
Received: by with SMTP id u5so236098pfh.6 for <>; Thu, 08 Mar 2018 10:32:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=0eHyeRZ9Vp9zvi4zOqjA3v/IZkAOjN8cABgUQY5O75M=; b=LgACTsYS658Yxc20XSEaEzWb7GxXkzOma1+3vYrcwbuU8qbA6eYe494ORdusY/4Yh+ NBtrTBO097UbPOV2phOrC8d0sZdSp3iqPRxSyvfySFnAHFlejBfmVW0jSfmnabrxkKSz GDPJnx1WyF9YoD4Na3l2WPI63xHGg4WTQ5zqGQE/412pOqjeKaSKawQy/2knM51XFx0V 9MJILUCy9EDqLHWYhztEHN5hwdWhOwaaYXRyhFPSje/xO/gyvhsAQbiTlsWw4m5uegI3 hR3hg/nENnu9WymTIPLrucU8D6L6nvI1+x61ede/J1Ey3gIR/dRNPN3PTwkPIfzGO03i O/jw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=0eHyeRZ9Vp9zvi4zOqjA3v/IZkAOjN8cABgUQY5O75M=; b=T2t4Z9GSr8WlW9EJ0WWLbgn7Plb8k8c7S+wAAr/1SOBBA627v3GiaqluKR/D9KVTkR jbnkLnejb8VFiSJDwchN8G4+Y02aIU9BfDk22mY7P1kATOVZa/IBl9549wFyNAMNueru bVHTII/m7PsLAjmRxzxUA5Srr7/N7oWsrsIMYgdxrdggM/1LQj78nXrnVvzknKWi6Anl IACKIZd7V/NHE5CLzb7++uOWxZ8OVc2Ij8IIc+gdvK5syTqMpt7R/E+cX9VF79aTC+LE p90hlFdC4V/xTNmwRnjpCUqWwYzw/mQZ1Aq3zO1YEimcUcqeAomZ6PsVnGuI4JDpz/fn dLJA==
X-Gm-Message-State: AElRT7GeE/C530Xk+TdswgZu+WiudnOtlIzoTD57OxA5zdPrKg3K2jtC PZ8y/CZw/SUxNGjekTLV5iSN9t7/
X-Google-Smtp-Source: AG47ELtW1MYypFzZmbpXMcxSMWZwutsRMdsnH6WDUNhtvhpR7dWk5ZVWbFcNVZbmuFyGzz/r1t8xpw==
X-Received: by with SMTP id k195mr9741685pga.312.1520533920824; Thu, 08 Mar 2018 10:32:00 -0800 (PST)
Received: from [] ([]) by with ESMTPSA id y18sm38780343pfl.146.2018. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 08 Mar 2018 10:31:59 -0800 (PST)
From: Dino Farinacci <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_01ADF7F1-E7FA-439B-8037-BE6C083FF1B6"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Thu, 08 Mar 2018 10:31:58 -0800
In-Reply-To: <>
Cc: " list" <>
To: Luigi Iannone <>
References: <>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <>
Subject: Re: [lisp] LISP-GPE Review
X-Mailman-Version: 2.1.22
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: Thu, 08 Mar 2018 18:32:08 -0000

> I think this is too restrictive IMO and will will cause problem in incremental deployments. 
> Imagine deploying LISP-GPE in the beta network…  we cannot because this would mean having a flag day, which is impossible.
> I think would be better to have bits N, E, V to 0 when P is 1 in this way there is compatibility.
> A legacy LISP data-plane box will never participate in a mapping that is not IP over IP, hence LISP-GPE can send traffic with P=1 and Next protocol equal 1 or 2.
> The legacy LISP box will receive the packet, will ignore the P bit and decapsulate as IP over IP and will work without problems.
> For the other direction, legacy LISP box sending to LISP-GPE box, everything depends again on the mappings. 
> Legacy LISP will talk only to xTR that locators using IP over IP, cannot do otherwise. The receiving LISP-GPE is able to handle legacy LISP traffic.
> The mappings deliver the information of "what is mapped on what"  just using LCAF, but details are out of the scope of this document. 

We have a code-point for GPE (VXLAN-GPE) in the Encapsulation Format LCAF. This document should describe the usage of this so a LISP-GPE node can tell when it RLOC-probes a LISP node that it needs to encapsulate using the RFC6830bis format.

The authors would have to decide if the VXLAN-GPE bit below would be sufficient or a new one needs to be allocated for LISP-GPE.