Re: [lisp] VPNs and Initial Applications

xu cai <jeffreycai@gmail.com> Thu, 24 October 2013 02:56 UTC

Return-Path: <jeffreycai@gmail.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 DF9C921E8089 for <lisp@ietfa.amsl.com>; Wed, 23 Oct 2013 19:56:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ek7MAvWKYsHm for <lisp@ietfa.amsl.com>; Wed, 23 Oct 2013 19:56:50 -0700 (PDT)
Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id 1A0D411E80ED for <lisp@ietf.org>; Wed, 23 Oct 2013 19:56:50 -0700 (PDT)
Received: by mail-ie0-f177.google.com with SMTP id e14so2790001iej.8 for <lisp@ietf.org>; Wed, 23 Oct 2013 19:56:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=oQxk5bj2OiSXS8cK5q/ISKciACxrGGZ4I46uHc2RuUo=; b=SK845BMbdc+JDyb9PHDZbZxllcwvTRHPXFpRe/v1koc5a+Q1VZKPEIbMI5fCGF8m1K HrdU48QJDipLQQrFnHL/vXdxIPa7g8ekYBXWnDOWVbrQl4kKhRxXppu8w+rj3Kson7aC XOkM4rEED39S8heUUbzzK2wC6zmZrd0FwJdUkbYN2wgUhJqex3ThfEX87A3aI7jbYyAM gNEEuAS9/7B/oEknMgrdwP4TiGSyN/kClpOtKq8Jf37r3CVy38f52DrSBxDD79LVoMo4 6Acwn11id7lqaWfaD8Rx8Itl2YB20m+bD6OjeKmUsr0zPl8c7pOi/0R8maIoM1/Qgd8y pOYA==
MIME-Version: 1.0
X-Received: by 10.50.55.106 with SMTP id r10mr43795igp.45.1382583409519; Wed, 23 Oct 2013 19:56:49 -0700 (PDT)
Received: by 10.64.33.130 with HTTP; Wed, 23 Oct 2013 19:56:49 -0700 (PDT)
In-Reply-To: <20131023201717.A090318C1CF@mercury.lcs.mit.edu>
References: <20131023201717.A090318C1CF@mercury.lcs.mit.edu>
Date: Thu, 24 Oct 2013 10:56:49 +0800
Message-ID: <CABMOVYDm+-1wu_Gx=g=feYRQRNooB0dkTZPFoKmK9sHGg2zTng@mail.gmail.com>
From: xu cai <jeffreycai@gmail.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Content-Type: multipart/alternative; boundary="047d7b10ce43ff33c204e973c80b"
Cc: lisp@ietf.org
Subject: Re: [lisp] VPNs and Initial Applications
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, 24 Oct 2013 02:56:51 -0000

Hi Noel

I happen to see this email, quite interested in this topic, may I get a
copy of your initial version of the "intro document" ? what's the purpose
of the document, a new RFC draft ?

thanks a lot in advance.

Jeffrey Cai



On Thu, Oct 24, 2013 at 4:17 AM, Noel Chiappa <jnc@mercury.lcs.mit.edu>wrote:

> In the previous version of the Intro document, we had a sub-section (in the
> "Initial Applications" section) titled "Local Uses" which started like
> this:
>
>    LISP has a number of use cases which are within purely local
>    contexts, i.e. not in the larger Internet.  These fall into two
>    categories: uses seen on the Internet (above), but here on a private
>    (and usually small scale) setting; and applications which do not have
>    a direct analog in the larger Internet, and which apply only to local
>    deployments.
>
>    Among the former are multi-homing, IP version traversal, and support
>    of VPN's for segmentation and multi-tenancy (i.e. a spatially
>    separated private VPN whose components are joined together using the
>    public Internet as a backbone).
>
> As a result of the interim, we apparently decided to break out VPN's as a
> separate sub-section, because I know have a new sub-section:
>
>    Virtual Private Networks
>
>    This includes support of VPN's for segmentation and multi-tenancy
>    (i.e. a spatially separated private VPN whose components are joined
>    together using the public Internet as a backbone).
>
> and the cryptic note "L2 and L3".
>
>
> I'm really lost as to what the document should say/talk about in this
> sub-section, and I'm not sure what that "L2 and L3" should expand into
> (presumably it refers to both bridged VPNs at level 2, and also 'classic'
> VPNs at level 3).
>
> There doesn't seem to be a lot written about VPN support in LISP: there is
> one ID ("Layer 2 (L2) LISP Encapsulation Format"), but it mostly just gives
> the packet format; a quick Google search didn't turn up anything that
> useful
> either.
>
> Can people give me some idea what this sub-section should say? I don't need
> text, just a list of points to cover. Thanks!
>
>         Noel
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp
>



-- 
- jeffrey