> Hi Dino. > > I'm not really asking about TTL processing for tunnels in > general... I'm asking specifically in the context of virtual network > service, where tenants are connecting to virtual networks expecting > either L2 or L3 service. What expectations to the TSes have when it > comes to TTL modification?
I think it is exactly the same case. > In the L2 case, tenatnts expect to be given service equivalent to an > L2 broadcast domain. I.e., nodes can talk directly to each other at > the L2 level using unicast/multicast. This is what we usually think of > as being attached to a shared "link". Right - but for a L2 service there is no TTL to decrement in the NVE since it forwards a packet based on a MAC header. > But what if the service being provided is L3? In this case TSes are > only sending IP packets, but all TSes are directly reachable (i.e., > without leaving the VN). What expectation do TSes in this type of > situation expect of the TTL processing? "Directly" needs to be defined above. If the two TSes are in the same subnet then it would behave as it does today (when 2 hosts are connected to hub - I don't say switch because I don't want to complicate the discussion). > Do they even care? If I am 10.0.0.1 in CA on subnet 10.0.0.0/8 and you are 10.0.0.2 in NY on subnet 10.0.0.0/8 and we are reachable via the overlay, I expect one line if output from traceroute. If you are 11.0.0.1 I expect at least 2 lines of output. Dino > > Thomas > _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
