Hi Dino, Joel, Just as an FYI.
QUIC is a fully fledged transport in VPP’s host stack so yes, it can listen on any port. It’s based on quicly [1] and northbound, towards the app, it exposes an API similar to the one used by other transports, e.g., TCP, UDP, TLS. The VPP internal APIs are not POSIX compliant. Should also note that LISP in VPP today works only over UDP. Regards, Florin [1] https://github.com/h2o/quicly > On Mar 22, 2022, at 7:44 AM, Dino Farinacci <[email protected]> wrote: > >> Heard back from a QUIC expert. > > Thanks for the quick response. > >> As long as we do not want to use QUIC over HTTP, we can use whatever UDP >> port we want to carry QUIC. > > Okay, I don't think we need to run LISP over HTTP/QUIC. > >> I would note that since we may want to have the same node provide >> connectionless (UDP-based) LISP and connection orient (TCP or QUIC) LISP, it >> seems that if we want a well known UDP destination port it should be >> different from 4342. >> >> Also, when we use QUIC for LISP we do need to specify what the destination >> connection-ID (the QUIC internal ID) will be. There is a lot of flexibility >> on that. > > Right now we use port 4342 for both TCP and UDP. I say, we spec that we use a > connection-ID value of 4342 for QUIC. And we are done with this issue. > > Comments? > > Dino > > _______________________________________________ > lisp mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/lisp _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
