Re: [lisp] Adoption of draft-chiappa-lisp-architecture-01 anddraft-chiappa-lisp-introduction-01

"Flinck, Hannu (NSN - FI/Espoo)" <hannu.flinck@nsn.com> Thu, 23 August 2012 13:47 UTC

Return-Path: <hannu.flinck@nsn.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5CF921F85F4 for <lisp@ietfa.amsl.com>; Thu, 23 Aug 2012 06:47:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I8MahEqRHjQ2 for <lisp@ietfa.amsl.com>; Thu, 23 Aug 2012 06:47:24 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id C457121F85A5 for <lisp@ietf.org>; Thu, 23 Aug 2012 06:47:23 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q7NDlJMt031258 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 23 Aug 2012 15:47:20 +0200
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q7NDlGqO014028; Thu, 23 Aug 2012 15:47:19 +0200
Received: from FIESEXC008.nsn-intra.net ([10.159.0.16]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Thu, 23 Aug 2012 15:47:17 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 23 Aug 2012 16:47:17 +0300
Message-ID: <E6647B13E38E7C4E965285DCC22260AF015B19DA@FIESEXC008.nsn-intra.net>
In-Reply-To: <20120813133258.BB02C18C09F@mercury.lcs.mit.edu>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [lisp] Adoption of draft-chiappa-lisp-architecture-01 anddraft-chiappa-lisp-introduction-01
Thread-Index: Ac15WCx/MKo1ZH0rTZWOQz6LC3ZbAQH2akIw
References: <20120813133258.BB02C18C09F@mercury.lcs.mit.edu>
From: "Flinck, Hannu (NSN - FI/Espoo)" <hannu.flinck@nsn.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>, lisp@ietf.org
X-OriginalArrivalTime: 23 Aug 2012 13:47:17.0574 (UTC) FILETIME=[CF5B7660:01CD8135]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 2972
X-purgate-ID: 151667::1345729640-00006F5F-3FAFF59E/0-0/0-0
Subject: Re: [lisp] Adoption of draft-chiappa-lisp-architecture-01 anddraft-chiappa-lisp-introduction-01
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Thu, 23 Aug 2012 13:47:24 -0000

Hello Noel and others

These drafts were very interesting readings.  

I have some comments that you may consider:

draft-chiappa-lisp-introduction-01

Section economics

you mention here "maximizing" the cost-benefit ratio. I believe we
should minimize or optimize it.


Section 4. Initial applications

These may go a bit too far and some of the text maybe better positioned
in the architecture draft rather than in the intro document. This is
because that the base documents as such do not suffice for some of the
applications you describe here: Traffic engineering and mobility and
maybe IP version reciprocal traversal but needs extension on top of the
base documents. And these extensions are not yet WG draft even. 

Should we say something where in the network the LISP  nodes/ devices
are located (e.g. CPE, CE/PE etc)?

Maybe whole section 7 Design approach is better at home in the
architecture document.

Note that you use terms node and device interchangeable (editorial).

draft-chiappa-lisp-architecture-01

I was wondering if draft-ietf-lisp-eid-block-02.txt is worth mentioning
in the relationship of sections 5.2 and 5.3?

One editorial wording nit: "base station" is not a mobile ip term, and
in cellular networks it has a certain meaning  (@ radio level) that
doesn't match what is meant here either. Instead mobile IP talks about
"home agents" that know the original location.  


Thank you for the documents.

best regards
Hannu




-----Original Message-----
From: lisp-bounces@ietf.org [mailto:lisp-bounces@ietf.org] On Behalf Of
Noel Chiappa
Sent: Monday, August 13, 2012 4:33 PM
To: lisp@ietf.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [lisp] Adoption of draft-chiappa-lisp-architecture-01
anddraft-chiappa-lisp-introduction-01


    > From: Luigi Iannone <ggx@gigix.net>

    > I will send comments very soon.

Comments will be most useful (and I look forward to them - assuming
of course that that the WG decides to take these two up):.


One minor thing to note; as I indicated when I first announced them:

  http://www.ietf.org/mail-archive/web/lisp/current/msg03786.html

These are rough drafts (and the second one is only partially complete),
so as
I indicated in that message:

  we're not (yet) at the 'detailed editorial comments' stage - although
if
  anyone reads it, and has high-level comments (e.g. 'you ought to talk
about
  topic X', or 'it would be better if you talked about P before you get
to
  Q'), I would be most grateful for, and interested in, hearing things
like
  that.

I tend to fiddle with text details extensively, so at the detail level
there
will have been lots of changes before the next draft version. After
that,
then we'll be ready for the detailed editorial comments! :-)

	Noel
_______________________________________________
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp