> VPP is the whole stack in this case, L2 to L7, so just after ip-local > processing is done and packet is handed to UDP port 4342 handler, one could > try to infer if the packet is QUIC or LISP. Not saying it’s easy or fast :-)
That is what I wanted to avoid, because if a QUIC packet with port 4342 is sent to a old system, then the LISP code will think its an invalid packet type. And you can't determine capability because you can't send UDP 4342 packets. ;-) > This can potentially work only because LISP, UDP and QUIC are all implemented > within VPP, i.e., same process. So this probably cannot be generalized. Yes, Joel and I determined that. QUIC has to run in the LISP process. This is a pity architecturally. I think we should use the connection-id API, as Joel mentioned. Cleaner. Dino _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
