> Dino Farinacci <[email protected]> wrote: >>> Hi Dino, that an interesting discussion today. >>> But too short, and not really resulting in anything specific. > >> Yeah, maybe so Michael but I hope it fosters discussion, new ideas, and >> brings people together. > > Me too! > >>> I am a LISP enthusiast (both the language and the protocol.. haha). >>> I don't know that much about how LISP is deployed, operationally. > >> It is deployed in many niche application use-cases in "limited >> domains". The biggest success currently is in cisco's SDA >> product. Maybe someone on the list can talk a bit about it. > > If I wanted to deploy it among a few cooperating entities, I think that I > would need address space for the overlay. Where would I get that?
You would get a random address allocated out of 240.0.0.0/4 and so would I. We would register those EIDs to the mapping system so the dynamic RLOCs are bound to those EIDs. I would have to tell you my EID, so you can ping it and the system would connect us (even through NATs). It is much more plug-and-play than existing Kubernetes based systems. Don't get me wrong KB is great, but it is heavyweight, maybe more heavy weight than most people need. > >> Solving such problems have moderate importance but focusing on them >> takes our eye off what is important. > > I'm not sure what is important. > I care about universal deployment of IPv6, and what I see is that Enterprises > are way behind on this, and one of the pain points they see is that there > isn't address space that they easily get. Okay, then the example above uses fe::/8 and allocates random bits in the rest of the 120 bits. Or … those 120 bits can be a hash of your public key. Everything else stays the same. The mapping system maps IPv4 EIDs to NAT-translated RLOCs. > I think that we need to do something with getaddrinfo(). Your DNS names map to fe::/8 addresses. Apps only know about EIDs, nothing else. Then they can move and keep running. They don't even know they are moving. >>> It was an improvement, but we need to take it just a bit further. >>> What do you think? > >> I think what is imported is to ask what new network layer features we >> need to support so apps work better and are simpler to interface with >> the network. The two main features I see we need is: > >> o IP mobility (with shortest paths between the endpoints) >> o Low latency (which implies shortest paths between endpoints) > > I agree. Important. > But, to get this, we need apps to be able to learn what EID/IID/etc. to use > in order to get the service they need. The way they learn about addresses today is the same they would with an overlay. All an EID is in IPv4 is a 32-bit value. There is NO new semantic meaning to the app about such an address. Dino _______________________________________________ Int-area mailing list [email protected] https://www.ietf.org/mailman/listinfo/int-area
