Re: [lisp] Moving forward with lisp-nexagon

Rotem Tamir <rotemtamir@getnexar.com> Tue, 04 August 2020 17:41 UTC

Return-Path: <rotemtamir@getnexar.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 D26A53A0DCA for <lisp@ietfa.amsl.com>; Tue, 4 Aug 2020 10:41:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=getnexar.com
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 dR0nOyRdvpCR for <lisp@ietfa.amsl.com>; Tue, 4 Aug 2020 10:41:03 -0700 (PDT)
Received: from mail-qk1-x735.google.com (mail-qk1-x735.google.com [IPv6:2607:f8b0:4864:20::735]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B80A3A0DCB for <lisp@ietf.org>; Tue, 4 Aug 2020 10:41:03 -0700 (PDT)
Received: by mail-qk1-x735.google.com with SMTP id d14so39145629qke.13 for <lisp@ietf.org>; Tue, 04 Aug 2020 10:41:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=getnexar.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=A+sEH7OzTZEDB61EJriVDBCWwou3kDALcT2+bFGHRy4=; b=QCi4hqWwxzoGzGY8WRVlj4iB++XJ8XbQ9g/VaN1V8qBouwJ8BzvmMTcsUsAQMJAWSB sCno48SpNxtRdCEj6Bu+Mc0vChwXQe+e25eeBed/OlmBNBkj7hv0QmwbpS5kbcJzJxjs U75ELogFH5WiOcAg+nwT9Na7n+RlUy7QYBPnA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=A+sEH7OzTZEDB61EJriVDBCWwou3kDALcT2+bFGHRy4=; b=ojijkDqzqVIyeRYlJtNwgJVcl6mjxzzn2U3cGNGgISghCPxpSoNvUDvU4cXtyWOsdm AKAFDyjyTK8UClX9kfy6T5DRLDAeNYagMJNEnUQWoK9oxilOs/pv4jroD+Xd1Ewb5+H5 aYcEkl3KK4NNezd67KGXMhosOkCv713zvuo7PwmkFbN8mjCILvY82/oAOQH++gneXcf8 Xfc8F1I80g3anhxtZibRGT+u4gH9dJQadNA9PHBjV7BvocwSGxw/GjPgwcIY7nm8zsXz xjowxtcrwuUVjekdvWsK1OcKH9WLgf6BTa2XIa2KCV9bkZEHZ7nr0fCfSowk2x6ifSzO MTRw==
X-Gm-Message-State: AOAM532xO+hO4yfW5ml25tOiYQ8xtWm8AAtopeblB85CRg+OVXSpRmbY ksmqxNcZDMZIHEpJo9JOAYvxWfEEL+GhILjzvvTWg3T5nXA=
X-Google-Smtp-Source: ABdhPJxjZ7MvBIh4lhX4ezBp3msulG3/4LzppC5+pC6bBhv4C91EYJfKHnPsJ0wKlfxxpHalYbHs4JsExWB/BR4hcK0=
X-Received: by 2002:a37:9bca:: with SMTP id d193mr21185613qke.131.1596562861614; Tue, 04 Aug 2020 10:41:01 -0700 (PDT)
MIME-Version: 1.0
References: <mailman.348.1596554267.7280.lisp@ietf.org>
In-Reply-To: <mailman.348.1596554267.7280.lisp@ietf.org>
From: Rotem Tamir <rotemtamir@getnexar.com>
Date: Tue, 4 Aug 2020 20:40:50 +0300
Message-ID: <CALu8Y5YK3AHJy2FmdBuTD1J=uz_rsDy2AKoE1s=1jqUNtxbv0Q@mail.gmail.com>
To: lisp@ietf.org
Content-Type: multipart/alternative; boundary="0000000000003a81b005ac10c293"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/Wmlp6ylMyz0YJ7Y9KbcMOjxKeew>
Subject: Re: [lisp] Moving forward with lisp-nexagon
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 04 Aug 2020 17:41:06 -0000

Hi Sharon,

As a person coming from a non networking background, having worked on web
backend and data pipeline problems for many years I wanted to say that
working on this standard has been quite an eye opening experience.

I have not even heard of LISP before this work (when you first approached
me with this I thought you were referring to the programming language), and
I did struggle with the idea for a while. But looking at it now from an
system architecture perspective it is a brilliantly simple and scalable
approach to building a massive network of real-time geo spatial
communication.

Had we not gone with this approach we would have created yet another
version of the wheel, another proprietary  black box protocol.

These are very exciting times to be in the AI/vision/automotive field and I
really think we have a solid foundation to build upon.

So yes, I join the others in saying  I’m really looking forward to it
become a proper RFC,

Thanks for your work on this !!

R

On Tue, 4 Aug 2020 at 18:18 <lisp-request@ietf.org> wrote:

> Send lisp mailing list submissions to
>         lisp@ietf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://www.ietf.org/mailman/listinfo/lisp
> or, via email, send a message with subject or body 'help' to
>         lisp-request@ietf.org
>
> You can reach the person managing the list at
>         lisp-owner@ietf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of lisp digest..."
>
>
> Today's Topics:
>
>    1. I-D Action: draft-ietf-lisp-vpn-06.txt (internet-drafts@ietf.org)
>    2. Re: Moving forward with lisp-nexagon (Lori Jakab (lojakab))
>    3. Re: Moving forward with lisp-nexagon (Fabio Maino (fmaino))
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 03 Aug 2020 15:38:14 -0700
> From: internet-drafts@ietf.org
> To: <i-d-announce@ietf.org>
> Cc: lisp@ietf.org
> Subject: [lisp] I-D Action: draft-ietf-lisp-vpn-06.txt
> Message-ID: <159649429407.9381.18270622230431003594@ietfa.amsl.com>
> Content-Type: text/plain; charset="utf-8"
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Locator/ID Separation Protocol WG of the
> IETF.
>
>         Title           : LISP Virtual Private Networks (VPNs)
>         Authors         : Victor Moreno
>                           Dino Farinacci
>         Filename        : draft-ietf-lisp-vpn-06.txt
>         Pages           : 17
>         Date            : 2020-08-03
>
> Abstract:
>    This document describes the use of the Locator/ID Separation Protocol
>    (LISP) to create Virtual Private Networks (VPNs).  LISP is used to
>    provide segmentation in both the LISP data plane and control plane.
>    These VPNs can be created over the top of the Internet or over
>    private transport networks, and can be implemented by Enterprises or
>    Service Providers.  The goal of these VPNs is to leverage the
>    characteristics of LISP - routing scalability, simply expressed
>    Ingress site TE Policy, IP Address Family traversal, and mobility, in
>    ways that provide value to network operators.
>
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-lisp-vpn/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-lisp-vpn-06
> https://datatracker.ietf.org/doc/html/draft-ietf-lisp-vpn-06
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-lisp-vpn-06
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 4 Aug 2020 10:03:01 +0000
> From: "Lori Jakab (lojakab)" <lojakab@cisco.com>
> To: Sharon Barkai <sharon.barkai=40getnexar.com@dmarc.ietf.org>
> Cc: "lisp@ietf.org list" <lisp@ietf.org>
> Subject: Re: [lisp] Moving forward with lisp-nexagon
> Message-ID: <F0930CF4-FEAB-43C7-877C-B3394CE394EF@cisco.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi Sharon,
>
> I think this draft addresses some really interesting use cases, so I would
> like to see it advanced.
>
> -Lori
>
> > On Aug 2, 2020, at 6:44 PM, Sharon Barkai <sharon.barkai=
> 40getnexar.com@dmarc.ietf.org> wrote:
> >
> > We have presented the nexagon
> >  https://tools.ietf.org/html/draft-ietf-lisp-nexagon-04? <
> https://tools.ietf.org/html/draft-ietf-lisp-nexagon-04>
> > work at several LISP WG sessions.  We have made significant improvements
> to the work over that time in AAA, security, privacy, and grammar thanks to
> prominent non author wg members.
> >
> > This ID can help show what can be done with lisp mapped
> addressable-states and brokered mp2mp channels by simply using standard
> lisp ucast/mcast interfaces.
> >
> > ID can also help iot / street-processing specs evolve from sending
> things to a ?server?. Show an interoperable extendible paradigm, and
> actually interoperate and extend themed-channels with enterprise EID
> ?MIBs?.
> >
> > Before asking the chairs for formal WG adoption as authors, would like
> to know if folks are interested in seeing this advanced, and willing to
> help move it forward.
> >
> > Thank you.
> >
> > --szb
> > Cell: +972.53.2470068
> > WhatsApp: +1.650.492.0794
> > _______________________________________________
> > lisp mailing list
> > lisp@ietf.org
> > https://www.ietf.org/mailman/listinfo/lisp
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://mailarchive.ietf.org/arch/browse/lisp/attachments/20200804/02e1c68e/attachment.htm
> >
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: smime.p7s
> Type: application/pkcs7-signature
> Size: 3013 bytes
> Desc: not available
> URL: <
> https://mailarchive.ietf.org/arch/browse/lisp/attachments/20200804/02e1c68e/attachment.p7s
> >
>
> ------------------------------
>
> Message: 3
> Date: Tue, 4 Aug 2020 15:17:35 +0000
> From: "Fabio Maino (fmaino)" <fmaino@cisco.com>
> To: Sharon Barkai <sharon.barkai=40getnexar.com@dmarc.ietf.org>rg>,
>         "lisp@ietf.org list" <lisp@ietf.org>
> Subject: Re: [lisp] Moving forward with lisp-nexagon
> Message-ID: <9E1D2E74-EB6A-4F42-81FB-45314D88029E@cisco.com>
> Content-Type: text/plain; charset="utf-8"
>
> It?s indeed a very interesting use case and application for the LISP
> protocol. As an author, I would like to see the WG involved with this topic.
>
> Thanks,
> Fabio
>
> From: lisp <lisp-bounces@ietf.org> on behalf of Sharon Barkai
> <sharon.barkai=40getnexar.com@dmarc.ietf.org>
> Date: Sunday, August 2, 2020 at 9:45 AM
> To: "lisp@ietf.org list" <lisp@ietf.org>
> Subject: [lisp] Moving forward with lisp-nexagon
>
> We have presented the nexagon
>  https://tools.ietf.org/html/draft-ietf-lisp-nexagon-04 <
> https://tools.ietf.org/html/draft-ietf-lisp-nexagon-04>
> work at several LISP WG sessions.  We have made significant improvements
> to the work over that time in AAA, security, privacy, and grammar thanks to
> prominent non author wg members.
>
>
> This ID can help show what can be done with lisp mapped addressable-states
> and brokered mp2mp channels by simply using standard lisp ucast/mcast
> interfaces.
>
>
> ID can also help iot / street-processing specs evolve from sending things
> to a ?server?. Show an interoperable extendible paradigm, and actually
> interoperate and extend themed-channels with enterprise EID  ?MIBs?.
>
>
> Before asking the chairs for formal WG adoption as authors, would like to
> know if folks are interested in seeing this advanced, and willing to help
> move it forward.
>
>
> Thank you.
>
> --szb
> Cell: +972.53.2470068
> WhatsApp: +1.650.492.0794
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://mailarchive.ietf.org/arch/browse/lisp/attachments/20200804/1ae462dc/attachment.htm
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp
>
>
> ------------------------------
>
> End of lisp Digest, Vol 141, Issue 2
> ************************************
>