%% You should probably cite draft-ietf-quic-load-balancers-19 instead of this revision. @techreport{ietf-quic-load-balancers-02, number = {draft-ietf-quic-load-balancers-02}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-quic-load-balancers/02/}, author = {Martin Duke and Nick Banks}, title = {{QUIC-LB: Generating Routable QUIC Connection IDs}}, pagetotal = 27, year = 2020, month = mar, day = 9, abstract = {QUIC connection IDs allow continuation of connections across address/ port 4-tuple changes, and can store routing information for stateless or low-state load balancers. They also can prevent linkability of connections across deliberate address migration through the use of protected communications between client and server. This creates issues for load-balancing intermediaries. This specification standardizes methods for encoding routing information given a small set of configuration parameters. This framework also enables offload of other QUIC functions to trusted intermediaries, given the explicit cooperation of the QUIC server.}, }