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 <farina...@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 <g...@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 <farina...@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-dra...@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-annou...@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 _______________________________________________ lisp mailing list lisp@ietf.org https://www.ietf.org/mailman/listinfo/lisp
