Re: [lisp] Call for Adoption: draft-farinacci-lisp-name-encoding-15.txt

Sharon <sbarkai@gmail.com> Fri, 05 August 2022 17:30 UTC

Return-Path: <sbarkai@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 1E595C14F607 for <lisp@ietfa.amsl.com>; Fri, 5 Aug 2022 10:30:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EEqvUO3Me4rh for <lisp@ietfa.amsl.com>; Fri, 5 Aug 2022 10:30:29 -0700 (PDT)
Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47EE1C14CF0F for <lisp@ietf.org>; Fri, 5 Aug 2022 10:30:29 -0700 (PDT)
Received: by mail-wr1-x42a.google.com with SMTP id z12so3949188wrs.9 for <lisp@ietf.org>; Fri, 05 Aug 2022 10:30:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:content-transfer-encoding:from:to:cc; bh=5YkLsceI2srypuF0b63VOCLPz02UDlNq/3Ke0wViC7c=; b=fdCuHnkeC6sWHZREq+hESb6Z2UIElmE1YvA7LYyks7mlJ9D6SPSO3Cv63twT1cnW1D fYUwVM/SfEShfag7MvgJBl51LUP4eU2zaAKQWf/2+nQhx03EFTRfHVSYRMYQNGcqHluf Sg4F4ykS8fDsuwqK3Kcgfx9lAREPn1MmLnJhEReJKfTNXajx44gxWMEpe5b9KFVzbaHR r7qKXYpCWzmwnm6RoCjcosZ8jv5FLBfJjGD6yl00pptgKk7x2U2MLhzC3/2MACzw2zpC yZpsRRH78ZbTQ7gzZVySagLzkbPXRd1tDGQEZHTADO0A6WKXqmmXwe5zp4v43Ez2ZbyV v7CA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:content-transfer-encoding:x-gm-message-state:from:to :cc; bh=5YkLsceI2srypuF0b63VOCLPz02UDlNq/3Ke0wViC7c=; b=yVKwrNV/zUDUw7KFkfgcyOf9VCDU6gQsV6Gm0JWqS6LrZRaVzQfDSlQsj6tN+Wm2uP KGwSXpT/dbj/P4aJyU0YEAFhuaNZs2XFikq7pY/oSoqnA/X1nxKK4QSBbAgcGhdKuq42 50gq6wkgEIPBKj7VYsz/x9d3/NIkBvWdNKfoGUdqIgsQ4UZc8iaz9AlSjmGcYcEnS2Xy HWCVCF6NGoaLzEE/fXGbVb+/JHzkranQ9tPm+0gc1+WOeEeiR/Ahw+G7yAoVjpgfI8P4 rwrI4QZ2UDH9kSw40ZsvTw5MqhdN2ReYNmNXZLM2+viCvHf7p5OdfADI0cc/es2XjRSu hJQw==
X-Gm-Message-State: ACgBeo2vfVoYZAsWe053h5FHKbHHafqaf963bfualChvaOdXcg2KfiGm GC++lhpnsCaOmWHWu/Kt3vhtHTKx9A==
X-Google-Smtp-Source: AA6agR6rGtABlfIURx0uWGOy6fII8ccSBAXOKX+UkbuNC190O/21zPvDkIEIMXWiciyR8YHOF5uMDA==
X-Received: by 2002:a05:6000:1082:b0:220:5d1c:698 with SMTP id y2-20020a056000108200b002205d1c0698mr4605780wrw.284.1659720627672; Fri, 05 Aug 2022 10:30:27 -0700 (PDT)
Received: from smtpclient.apple ([2a0d:6fc2:4a91:6500:8cc:d01e:c404:202a]) by smtp.gmail.com with ESMTPSA id o5-20020a056000010500b0021f0af83142sm4314229wrx.91.2022.08.05.10.30.26 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 05 Aug 2022 10:30:27 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
From: Sharon <sbarkai@gmail.com>
In-Reply-To: <447A03ED-B53D-48B5-842A-D733B7D8610A@gmail.com>
Date: Fri, 5 Aug 2022 20:30:25 +0300
Cc: Luigi Iannone <ggx@gigix.net>, "lisp@ietf.org list" <lisp@ietf.org>
Message-Id: <BAFB63EB-14AE-4303-83C6-AA82F5EEEB2B@gmail.com>
References: <447A03ED-B53D-48B5-842A-D733B7D8610A@gmail.com>
To: Dino Farinacci <farinacci@gmail.com>
X-Mailer: iPhone Mail (19G71)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/F3GvGpixia4xFThVN6OZAb36eLo>
Subject: Re: [lisp] Call for Adoption: draft-farinacci-lisp-name-encoding-15.txt
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 05 Aug 2022 17:30:31 -0000

Support as well.

Name based routing supports a wide range of use-cases and association between clients and services that does not stall for DNS, avoids mass client-cache incoherency by concentrating mappings in-network, using well defined, interoperable and optimized lisp mapping system. 

It can further illustrate the use of virtual layer3 to distribute applications elastically, with built-in privacy protections, without the need to re-define these mechanisms per application.

From the other side of the spectrum, name based routing shows the advantage of overlay in supporting application routing vs complex and risky underlay routing and NAT changes.

Would very much like to see also a name based routing use-case clause added to the list of activities in the charter. Informational specs  which can be replicated by example and illustrate how and why name based routing can be used.

  

--szb
Cell: +972.53.2470068
WhatsApp: +1.650.492.0794

> On Aug 5, 2022, at 19:57, Dino Farinacci <farinacci@gmail.com> wrote:
> 
> I support (since I requested) this document as a working group document.
> 
> Dino
> 
>> On Aug 5, 2022, at 11:22 AM, Luigi Iannone <ggx@gigix.net> wrote:
>> 
>> Hi All,
>> 
>> The authors of the lisp-name-encoding draft (see below) have requested working group adoption for this document.
>> 
>> This email starts a three weeks call for working group adoption of this document.
>> 
>> Please respond, positively or negatively.  Silence does NOT mean consent.  
>> Please include explanation / motivation / reasoning for your view.
>> 
>> Thank you,
>> 
>> Luigi & Joel
>> 
>>>> On 24 Jul 2022, at 17:17, Dino Farinacci <farinacci@gmail.com> wrote:
>>> 
>>> We have made changes to -15 to address Joel's comments. Thanks to Marc and Joel for their participation and cooperation.
>>> 
>>> I would like to, at this time, request for this draft to be a working group document. I will present the status and changes to -15 at the LISP WG.
>>> 
>>> Cheers,
>>> Dino
>>> 
>>>> Begin forwarded message:
>>>> 
>>>> From: internet-drafts@ietf.org
>>>> Subject: [lisp] I-D Action: draft-farinacci-lisp-name-encoding-15.txt
>>>> Date: July 24, 2022 at 8:15:25 AM PDT
>>>> To: <i-d-announce@ietf.org>
>>>> Cc: lisp@ietf.org
>>>> Reply-To: lisp@ietf.org
>>>> 
>>>> 
>>>> 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 Distinguished Name Encoding
>>>>       Author          : Dino Farinacci
>>>> Filename        : draft-farinacci-lisp-name-encoding-15.txt
>>>> Pages           : 9
>>>> Date            : 2022-07-24
>>>> 
>>>> Abstract:
>>>>  This draft defines how to use the AFI=17 Distinguished Names in LISP.
>>>> 
>>>> 
>>>> The IETF datatracker status page for this draft is:
>>>> https://datatracker.ietf.org/doc/draft-farinacci-lisp-name-encoding/
>>>> 
>>>> There is also an htmlized version available at:
>>>> https://datatracker.ietf.org/doc/html/draft-farinacci-lisp-name-encoding-15
>>>> 
>>>> A diff from the previous version is available at:
>>>> https://www.ietf.org/rfcdiff?url2=draft-farinacci-lisp-name-encoding-15
>>>> 
>>>> 
>>>> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
>>>> 
>>>> 
>>>> _______________________________________________
>>>> lisp mailing list
>>>> lisp@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/lisp
>>> 
>>> _______________________________________________
>>> lisp mailing list
>>> lisp@ietf.org
>>> https://www.ietf.org/mailman/listinfo/lisp
>> 
> 
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp