[lisp] Alia Atlas' No Objection on draft-ietf-lisp-introduction-13: (with COMMENT)

"Alia Atlas" <akatlas@gmail.com> Wed, 15 April 2015 14:32 UTC

Return-Path: <akatlas@gmail.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B42E91B35AD; Wed, 15 Apr 2015 07:32:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.898
X-Spam-Level:
X-Spam-Status: No, score=-101.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id onV2d4Y67lgM; Wed, 15 Apr 2015 07:32:40 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 577BE1B359A; Wed, 15 Apr 2015 07:32:40 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Alia Atlas" <akatlas@gmail.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150415143240.23573.92682.idtracker@ietfa.amsl.com>
Date: Wed, 15 Apr 2015 07:32:40 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/vfdGlwGXAgYpFGHQACADsaclIVw>
Cc: lisp-chairs@ietf.org, lisp@ietf.org
Subject: [lisp] Alia Atlas' No Objection on draft-ietf-lisp-introduction-13: (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: <http://www.ietf.org/mail-archive/web/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: Wed, 15 Apr 2015 14:32:41 -0000

Alia Atlas has entered the following ballot position for
draft-ietf-lisp-introduction-13: 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 http://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:
http://datatracker.ietf.org/doc/draft-ietf-lisp-introduction/



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

Thanks for addressing my discuss and comments.


I support Adrian's discuss.  In a similar vein:

In Sec 3.2: Please either remove the claim of "Such LISP capable
routers, in most cases, only require a software upgrade." or explain
how you can justify the need to add and remove new encapsulations and
handle the various flag triggers and caching at line rate.  There is
no need for such marketing in this document.

1) Sec 1, second paragraph:
   "LISP creates two separate namespaces, EIDs (End-host IDentifiers)
and
   RLOCs (Routing LOCators), both are typically syntactically identical
   to the current IPv4 and IPv6 addresses."
   
   What does "typically" mean?  As far as I'm aware, they are
   syntactically identical.  This is reiterated in Sec 3.2; are you just
   trying to preserve the point of architectural freedom?  I've found
the
   third instance of insisting that the EID or RLOC now is only
"typically" 
   an IPv4 or IPv6 address. Please lose "typically".  Minorly, the ,
   before both should be a ;.

2) top paragraph of p.4:
  "The initial motivation in the LISP effort is to be found in the
   routing scalability problem [RFC4984], where, if LISP is completely
   deployed, the Internet core is populated with RLOCs while Traffic
   Engineering mechanisms are pushed to the Mapping System."

   Instead of "LISP is completely deployed" to "LISP were to be
   completely deployed" - making it subjunctive.  

3) Last paragraph in Sec 1:
   "This document describes the LISP architecture, its main
   operational mechanisms as its design rationale."

   I think you mean 

   "This document describes the LISP architecture and its main
   operational mechanisms as well as its design rationale."

4) In Sec 3.1, second paragraph:
   "Locator/Identifier split: By decoupling the overloaded semantics
      of the current IP addresses the Internet core can be assigned
      identity meaningful addresses and hence, can use aggregation to
      scale."
   I assume that you mean "topologically meaningful addresses" instead
   of "identity meaningful addresses".