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

Kyle Rose <> Fri, 14 September 2018 16:29 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id F2022130E5B for <>; Fri, 14 Sep 2018 09:29:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id QTZ-ANYorsI4 for <>; Fri, 14 Sep 2018 09:29:43 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::72b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7AD7B130E8C for <>; Fri, 14 Sep 2018 09:29:40 -0700 (PDT)
Received: by with SMTP id j7-v6so5460107qkd.13 for <>; Fri, 14 Sep 2018 09:29:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=b5c7FPOJ6pJCRorfhF09I7Tks+dLbalRHND+IhlYpbg=; b=GohL8Nm0NPVR1kazJCDKRby0T3wFwQa8rqSu+hiDzm/EB+1osiMl6VbA1YHmqMSkIh EZCI1KTBLXUpxpKRJpOPwymyayX8gGdx+dFkNnHMAP5tKGOwCz25fPg1w2O1DDMot2zv MQh7YnhJWMXoPYsiJlyCggYXbzItTbtjLYAYg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=b5c7FPOJ6pJCRorfhF09I7Tks+dLbalRHND+IhlYpbg=; b=C4FvMqwrJjlERNdQpRn3t4fZ0TZHyVsGbb5Q0NhiQb6cMJo2l8SQMbsdT7i5wQwP5x DSr2EgOUCkf+1u7mV2YRKIU5qRoFwjzFinVBIWRAFZaVOy3KTIRQi4OtQGmLtHfdjVpl BHsOBDCZXgbtKBNS2pJvdK+Ndik9fhdWkMAyDD8ACp0xn7n2bhzXHi9fdVovuT5CDAe3 09epsJUl7V9o6bWWoOFH5+1wo1sb9BKQUEargyMokPs/ox3AfmHZjRRKUiujX4iiy05K 4la1JDb0dI8N+wLYzeu4vIcssPDrm0Nso7xtdDq3Bt++4bThSKxqdEa+7YQLWeXVgxQ6 11Fg==
X-Gm-Message-State: APzg51Ba9hmnUEeHnQTwLMfn92Ctp4Z+x2BNymepXIPddT8DKsL/ztmk X9MBBJZDsO+KTkh7u57KE/1HUGDYj7wl1ZV9K1fzwQ==
X-Google-Smtp-Source: ANB0VdbZUkrdrYgIX4cbJ2qOOxm0EgMFTr3hDa8XG87ig3lcvVK4eEk9VSP/NLHsybd8++ZK9R5QscSCvce03cqBo5A=
X-Received: by 2002:a37:3492:: with SMTP id b140-v6mr8602943qka.355.1536942579133; Fri, 14 Sep 2018 09:29:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a0c:86ea:0:0:0:0:0 with HTTP; Fri, 14 Sep 2018 09:29:38 -0700 (PDT)
X-Originating-IP: [2604:6000:8a42:6905:1d06:646e:3613:148c]
In-Reply-To: <>
References: <> <> <> <> <> <> <> <> <> <> <>
From: Kyle Rose <>
Date: Fri, 14 Sep 2018 12:29:38 -0400
Message-ID: <>
Subject: Re: Secdir last call review of draft-ietf-lisp-rfc6830bis-15
Cc: Dino Farinacci <>, IETF SecDir <>, "" <>, IETF Discussion Mailing List <>, " list" <>, Benjamin Kaduk <>, =?UTF-8?Q?Mirja_K=C3=BChlewind?= <>
Content-Type: multipart/alternative; boundary="0000000000007841a40575d75408"
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 14 Sep 2018 16:29:55 -0000

My response is that while I suspect based on the conversation between
myself and Dino that LISP's security model probably adequately protects
mapping system integrity, my confidence in that judgment is low because the
information I need for a security review I can't find in the drafts without
reading every LISP-related document in detail, a time commitment I simply
can't justify. It's possible there's someone else in the security
directorate who knows more about the details of LISP and so would be able
to much more easily answer some of these questions with confidence; if so,
I would recommend that you ask them to take a look. I'm unwilling to say
"LGTM" simply because I can't find a problem in the time I've allocated.


On Tue, Sep 11, 2018 at 5:55 PM, BRUNGARD, DEBORAH A <> wrote:

> Thanks much Kyle for your comments and Dino for resolving!
> Cutting to the end where Dino asked for help-
> -----Original Message-----
> From: Dino Farinacci <>
> Sent: Tuesday, September 11, 2018 2:40 PM
> To: Kyle Rose <>
> Cc: IETF SecDir <>rg>;;
> IETF Discussion Mailing List <>rg>; list <
>>gt;; Benjamin Kaduk <>du>; Mirja Kühlewind <
> Subject: Re: Secdir last call review of draft-ietf-lisp-rfc6830bis-15
> > What I might recommend is either an augmentation of, or a new document
> analogous to (and informationally referencing),
> draft-ietf-lisp-introduction that covers the expected security properties
> of the overall design and the requirements for each of the subcomponents in
> a way that someone can understand without referring to any document other
> than the high-level architecture itself. draft-ietf-lisp-introduction is
> actually quite good at getting the general point of LISP across to someone
> new; I want to see something similar for LISP's security model. I think
> that's going to be better than inserting clarifying text here or there.
> I've actually read enough of this stuff at this point that I'm not sure I
> can enumerate exactly what's missing where. The threat model document could
> potentially be folded into that, but it has to start by painting a picture
> of the security that someone new to LISP can quickly understand.
> I’ll yield to the WG to respond to this.
> Dino
> [deborah]
> It's difficult to do *one* overview document on an evolving technology,
> especially if the intention is to provide reference to other documents
> which are also evolving. Lisp-intro is already having its problems and it
> is not published yet.
> As Mark Nottingham noted in his "How to Read an RFC" blog, when reading
> RFCs, for better or worse and the resulting frustration, it is "necessary
> to read not only the relevant text but also anything that it references":
> I'd suggest a wiki would be a better tool to capture this "overview"
> informational material. Not only can the format be easier on the eye, it
> can be a shared effort and timely updated. Similar to Benoit's work on his
> YANG tree dependencies, it would be helpful if a working group provided a
> working group tree of documents and it could even reference other working
> group documents.