[lisp] Stephen Farrell's No Objection on draft-ietf-lisp-impact-04: (with COMMENT)

"Stephen Farrell" <stephen.farrell@cs.tcd.ie> Thu, 22 October 2015 12:46 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: lisp@ietf.org
Delivered-To: lisp@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CFB01B36B2; Thu, 22 Oct 2015 05:46:52 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.6.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151022124652.30711.11416.idtracker@ietfa.amsl.com>
Date: Thu, 22 Oct 2015 05:46:52 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/z2cBMWNVco-puC3f3zLMDhggwWw>
Cc: draft-ietf-lisp-impact.all@ietf.org, lisp-chairs@ietf.org, draft-ietf-lisp-impact@ietf.org, lisp@ietf.org
Subject: [lisp] Stephen Farrell's No Objection on draft-ietf-lisp-impact-04: (with COMMENT)
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.15
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2015 12:46:52 -0000

Stephen Farrell has entered the following ballot position for
draft-ietf-lisp-impact-04: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-lisp-impact/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------


- section 3: "proven by several studies" without references is
bad - we don't want blatent assertion in RFCs so please add
some references. That could be done via forward pointers to
later in the document or just by adding the refs here as well
and explaining them more later. Or else delete the sentence as
being redundant.

- section 3, para starting "Results indicate...": Which
results? I can't tell from how it's writen.

- section 4: ConteXtream needs a reference as does the tier-1
operator (even if that has to be "private communication"at
least I'd know to go ask the authors if I care.

- I think you could note that as a map-and-encap scheme LISP
also offers the potential for encryption of traffic between
xTRs and reference the relevant lisp-crypto draft. That could
go where you add a mention of rfc 7258 if you do add that.
(In response to I think Spencer's comment.)

- As with Kathleen, I think the secdir review deserves a
substantive response. Please give it one.