Re: [lisp] Secdir last call review of draft-ietf-lisp-rfc6830bis-15

Dino Farinacci <> Thu, 30 August 2018 14:58 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E58DB130F40; Thu, 30 Aug 2018 07:58:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 4ICUuokvgNFO; Thu, 30 Aug 2018 07:58:39 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::42d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 81A26130F41; Thu, 30 Aug 2018 07:58:39 -0700 (PDT)
Received: by with SMTP id b11-v6so4013617pfo.3; Thu, 30 Aug 2018 07:58:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=cLE8TtIC7KCI8SOvUMklfkoS6XRNvX1EVAU9lMU1i5o=; b=ZQt4PyGIqxRWSrWtUSecAaATAPDjjsWzGMLCD/ZAK6fZPk9c87u/mS1+1WDzt2by2S bWI2yculPYwucqH9SWtvdSAcdnAcXm/WmA0NY34Wb5iOMS0wlrARsEbDhM/LjSrS8JHf +NWlt8UySmqkA1NCteHkiAG6wMCRhcWenF85VEON5RieU6MuZfu8v1BRshy7qR1wG61a iApkAzHxtqQNfdDMSeWOnRXISDnedRUHM3H1N0Tf3ZFu0Lqf1YUaX6cEWV5sv2AEdTyW /DLrSZAVNyHU2ak1fxQtT+6qOjaezB62/J6SeWojtGSBJMnP7GW2qDmUQd1cVHSBcw5L cpnQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=cLE8TtIC7KCI8SOvUMklfkoS6XRNvX1EVAU9lMU1i5o=; b=MxpevapJbW8cCe+/VyHIUw3/xt/0gosib3n6S2WrsmX00SS6ng2lINvPkk2SXMQCNE GtVEyB60fbDol8ZCclNkGJmRKWP+uF0S6rEjE0zdSJReQcUUE4F5Z3WasDiZVDByUGUs Einq7C/3ggxGWUrxnWbBFPBiybNTIu58kiJj2fxSNKpH9vEogCl/uLnQQsg9xwO7cohx qI9v0PUDcCxzKvB+luNC2fa0g9Vdc/YaC2gRy2Pjs1PbTzkhO5pU7zpzXe4y+GYvt8uF FH/B7M7yTSZaius/1+0xgQooqrtDL903kZBk9YAzRz8KxG+XE/n9z12ypIvWzejPJ93Z kkGw==
X-Gm-Message-State: APzg51AGUFs1gdF2/L1hgWNhSqiSpr5GBrqfu/QkAx3xOz8HAzzjjVKF wx9Ns0VrZpexV0R66xlfTAO1vd0f
X-Google-Smtp-Source: ANB0VdZCjenD+Utk2oMkM+Xf7ERyQfDLkEMmfwGZCcOdrMxKcpw80FI6/MEYIPkTvoPCkmz5MNplRg==
X-Received: by 2002:a63:e056:: with SMTP id n22-v6mr9934628pgj.205.1535641119149; Thu, 30 Aug 2018 07:58:39 -0700 (PDT)
Received: from [] ([]) by with ESMTPSA id u9-v6sm13066581pfi.104.2018. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Aug 2018 07:58:38 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Dino Farinacci <>
In-Reply-To: <>
Date: Thu, 30 Aug 2018 07:58:37 -0700
Cc: Kyle Rose <>, IETF SecDir <>,, IETF Discussion Mailing List <>, " list" <>, Benjamin Kaduk <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <>
To: Luigi Iannone <>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <>
Subject: Re: [lisp] Secdir last call review of draft-ietf-lisp-rfc6830bis-15
X-Mailman-Version: 2.1.27
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, 30 Aug 2018 14:58:48 -0000

> Kyle, Dino,
> I fill like this discussion is going sideways w.r.t. the original 6830bis document.
> You started to discuss other documents and other solutions, which, while certainly interesting and important, belong to other threads and documents.

Well I think the security guys want to make sure LISP, holistically, is secure. So we have to present solutions that may not be in the data-plane. I agree though we should focus on data-plane security since that is what Kyle is reviewing.

> IMHO here are the few points that need to be clarified:
>> On 28 Aug 2018, at 23:48, Kyle Rose <> wrote:
>> Hi, Dino. I have additional responses inline.
>> > For the internet core (DFZ RIB) use-case, LISP proposes replacing BGP sessions
>> > and global eventually-consistent state sharing with a global control plane and
>> LISP *does not propse to eliminate BGP*, in fact it needs it so RLOC reachability across the network is available, or there would be no underlay for the LISP overlay.
>> The whole point of LISP is to create a routing overlay for the EID address space, the RIB of which is managed by a global mapping system, not BGP sessions. If control plane traffic managed by BGP (or static routes, or whatever networks use once the DFZ RIB is limited to entities in the core) continues to flow, that is of small comfort to end users trying to get data over the data plane. >From the perspective of end users, BGP is being replaced routing of the traffic that matters to them.
>> Maybe this is just splitting hairs: I certainly don't want to rathole on this point.
> @Kyle: can we consider this point closed?

From my standpoint, it should be.

> [trimmed]
>> > One area of concern, of which I have not been able to find discussion, is that
>> > of the implications of shared capacity for the control and data planes, and how
>> > this can allow a volumetric data plane attack to deny a router access to the
>> > global mapping system, slowly choking off service to uncached portions of the
>> Well yes, this happens with all our IETF protocols. It is a valid concern and there are many operational techniques in network infrastructure that *help* solve (but not eliminate) these problems.
>> I would like to see a discussion of whether and how the nature and scale of this problem differs from that of the status quo. BGP sessions and RIB push have properties that are well-established from decades of experience: surely LISP does not have exactly the same properties. The security considerations should make clear, for instance, how a loss of control plane connectivity differs from the loss of a BGP session, and how this impacts visibility and behavior of the data plane.
> I am not sure I understand the point. Isn’t this covered by RFC7835? Reference to that document isn’t sufficient?
> If not, can you clarify further?

And I am not sure this is relevant to the data-plane.

>> > I would also like clarification on what defines the separation between the
>> > control plane and data plane, and whether authentication itself is used to
>> A control-plane obtains information to store in a table. The data-plane uses that table. That is the definition in the simpliest form.
>> I mean specific to LISP, not generically. For instance, does "LISP Control-Plane signaling" include only valid messages, or valid + inauthentic (and presumably dropped) messages? Traditional attack traffic (e.g., a DDoS attack against a website) is part of the same data plane as all legitimate end user traffic; is attack traffic directed at control plane endpoints considered part of the control plane, or is it a third category of traffic? If the latter, then what does an operator need to do to ensure that control plane is always available?
> IMHO, these questions should be asked for in the 6833bis thread. Don’t you guys agree?

Yes, agree.


> Ciao
> L.
>> Kyle