On October 6, 2022 at 9:14:45 PM, Sharon Barkai wrote:
Sharon: Hi! ... > > So...are there specific work items that (a) talk about how to use > > LISP, or (b) should be added to the list (where the status can be > > determined later), or (c) should be taken off the list? > > > > In my opinion there are, specifically in application routing. Good wording can > open the charter just enough to include application design patterns which > leverage lisp w/o a flood of phrasing every application as a lisp draft. I prefer listing specific items, but if we can find the right (concise, specific, clear, etc.) wording then that may work too. As I said, I'll leave the details to Luigi and Padma. ;-) Thanks! Alvaro. > Drafts are a big overhead which take years and burden wgs, so such a balance > is important. > > Charter wording can open lisp-routing specifications for: > > - distributed multi-vendor eco sys apps > - leveraging next-gen mobile/green compute > - scattered all over but function as a network > > - w/o the traditional CSP/MSP concentration > - w/o impossible chatty centralized resolutions > - based on the strengths of lisp aggregation: > > o eid logical algorithmic flexible addressing > o mapping cached-(in)coherency balance > o mass multicast, channels as mainstream > > Each such generic factoring of application routing saves industry time and > money re-inventing wheels, figuring out proper layering, building wasteful > inefficient api integrations. > > I have in mind automotive/geospatial, network cyber-security/AI sampling coin, > and edge-iot / geo-distributed map-reduce, map using lisp-mapping, and reduce > to lisp multicast channels/eid-topics. _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
