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

"Wiley, Glen" <gwiley@verisign.com> Fri, 31 August 2012 14:16 UTC

Return-Path: <gwiley@verisign.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 7DA5821F8611 for <lisp@ietfa.amsl.com>; Fri, 31 Aug 2012 07:16:22 -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=[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 JF-NH4RfkaeB for <lisp@ietfa.amsl.com>; Fri, 31 Aug 2012 07:16:21 -0700 (PDT)
Received: from exprod6og113.obsmtp.com (exprod6og113.obsmtp.com [64.18.1.31]) by ietfa.amsl.com (Postfix) with ESMTP id 8B8F321F860E for <lisp@ietf.org>; Fri, 31 Aug 2012 07:16:19 -0700 (PDT)
Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob113.postini.com ([64.18.5.12]) with SMTP ID DSNKUEDHMlrstshpiBNj50SCfvD480zL4w38@postini.com; Fri, 31 Aug 2012 07:16:21 PDT
Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01.vcorp.ad.vrsn.com [10.173.152.255]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id q7VEGDMj029518 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 31 Aug 2012 10:16:15 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0318.001; Fri, 31 Aug 2012 10:16:04 -0400
From: "Wiley, Glen" <gwiley@verisign.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>, "lisp@ietf.org" <lisp@ietf.org>
Thread-Topic: [lisp] Adoption of draft-chiappa-lisp-architecture-01 and draft-chiappa-lisp-introduction-01
Thread-Index: AQHNh4MsF415waY9jkmN05M7yuMmwQ==
Date: Fri, 31 Aug 2012 14:16:12 +0000
Message-ID: <641EE49757824F4BBE5F863B22FDDBF2130EB5@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
In-Reply-To: <20120813133258.BB02C18C09F@mercury.lcs.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <42E5F4CAA121E24B8EA72516F0B4E95D@verisign.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [lisp] Adoption of draft-chiappa-lisp-architecture-01 and draft-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: Fri, 31 Aug 2012 14:16:22 -0000

The draft looks acceptable to me.  I have a few high level comments and
I'll throw in a few more detailed ones for convenience:


There needs to be a discussion of resilience to DDOS, particularly because
LISP is based on UDP it may create opportunities for reflector and
amplification attacks similar to what we see on large scale DNS resolver
footprints.  Were you planning on including this in the "Robustness"
discussion?  I think it warrants a separate section if you are amenable to
that idea.  I'd be happy to contribute some narrative to that point as
well.


A few more detailed nits:

Section 2: Is DFZ size still a main design driver or is it really more of
a question of finer grained routing with a side benefit of DFZ size
reductions?

Section 3.2: "one at each end" isn't really the case for LISP, "one near
each end" I think is a little closer to what you mean, especially since
you mention LISP being invisible on both ends.

Section 5: Does list really have three key name spaces (thinking DDT
nodes) rather than two?

Section 11.2.1: Might want to revise language around the DNS registry
example.  TLDs have different registries (although root of course is
unique).  In DNS you can't take your domain name to a different registry,
you can however take it to a different registrar.

--
Glen Wiley
Systems Architect
Verisign Inc.




On 8/13/12 9:32 AM, "Noel Chiappa" <jnc@mercury.lcs.mit.edu> wrote:

>
>    > 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