Hi,
> 
> I've decided to use NROffEdit for writing my CGEID draft (Cryptographically 
> Generated Endpoint IDentifiers).
> 
> While considering CGEIDs I got another idea:
> 
> Would it be possible to use LISP as routing protocol for mesh networks by 
> announcing the CGEIDs of neighbour-nodes as RLOCs of a node? It would be some 
> kind of onion routing without encryption.

I would think you would want RLOCs to continue to be Provider-Assigned 
addresses and thet CGEIDs are just like any other EID. That is, the CGEID's 
topological location could be found by doing a mapping database lookup.

But yes, I have seen use-cases where folks want tunnel-endpoints to be mobile. 
And if you want to find a new location of the tunnel end-point, then you assign 
the tunnel-endpoint an EID. So let me be more precise in my language. The 
requirement was to make a GRE tunnel mobile. So if you configured the ends of a 
GRE tunnel to be in EID-space, either end could move if those EIDs mapped to 
locators, and LISP encapsulation is performed to an xTR adjacent to the GRE 
end-point or co-located with the GRE end-point.

We have also see LISP use to make a routing protocol work over a wide-area 
network where multi-hop adjacencies were formed. cisco's EIGRP is doing this in 
some use-cases.

> The biggest problem of a node seems to be reaching the map-servers/-resolvers 
> when bootstrapping. Can a LISP tunnel router/mobile node run it's own 
> map-server/-resolver connecting directly to the Tier 1 map-server mesh or is 
> there some kind of authentication between the map-servers?

Yes, there are military applications that want to do this as well.

Dino

> 
>  
> Regards,
> 
> Renne
> 
>  
> -- 
> Best regards,
> 
> Rene Bartsch, B. Sc. Informatics
> 
> 
> 
> Current Bitcoin Exchange Rate: https://www.bitcoin.de/de/r/mwfngu
> 
> _______________________________________________
> lisp mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/lisp

_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp

Reply via email to