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

Ronald Bonica <rbonica@juniper.net> Thu, 06 September 2012 02:28 UTC

Return-Path: <rbonica@juniper.net>
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 064AA21F8540 for <lisp@ietfa.amsl.com>; Wed, 5 Sep 2012 19:28:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.539
X-Spam-Level:
X-Spam-Status: No, score=-106.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 JdIzQapQ4V7C for <lisp@ietfa.amsl.com>; Wed, 5 Sep 2012 19:27:59 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by ietfa.amsl.com (Postfix) with ESMTP id A1F9D21F84D8 for <lisp@ietf.org>; Wed, 5 Sep 2012 19:27:58 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKUEgKLJjN63XwUsdjTd23DO+PcWnbY/3l@postini.com; Wed, 05 Sep 2012 19:27:58 PDT
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 5 Sep 2012 19:23:12 -0700
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by p-cldfe02-hq.jnpr.net (172.24.192.60) with Microsoft SMTP Server (TLS) id 14.1.355.2; Wed, 5 Sep 2012 19:23:12 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Wed, 5 Sep 2012 22:23:11 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>, "lisp@ietf.org" <lisp@ietf.org>
Date: Wed, 05 Sep 2012 22:23:10 -0400
Thread-Topic: [lisp] Adoption of draft-chiappa-lisp-architecture-01 and draft-chiappa-lisp-introduction-01
Thread-Index: Ac2LaVkDn0CmPqTiRpmtimxsKK1asgAazycA
Message-ID: <13205C286662DE4387D9AF3AC30EF456D782F2F7B7@EMBX01-WF.jnpr.net>
References: <20120905132121.2135C18C0C6@mercury.lcs.mit.edu>
In-Reply-To: <20120905132121.2135C18C0C6@mercury.lcs.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
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: Thu, 06 Sep 2012 02:28:00 -0000

Hi Noel,

You're right. The introduction document contains references to Section 5.1.1 of the architecture document. Section 5.1.1 of the architecture document talks about exactly the issue that I raised.

So, we are fine as is.

                    Ron

> 
> The "Architectural Perspective" document contains a fairly extensive
> discussion of this issue ("5.1. LISP EIDs").
> 
> There is a warning cross-reference to that discussion in the
> "Introduction"
> document ("3. LISP Overview"), although I do note that that warning is
> not replicated immediately below when the term EID is introduced ("3.1.
> Basic Approach").
> 
> Would people like to see me add an additional warning (and cross-
> reference) at the point at which the term 'EID' is introduced? I don't
> know if it's important enough to disturb the flow of the text, but I
> don't have any significant objection to so doing if it's important
> enough.