Paul Kyzivat <pkyzi...@alum.mit.edu> writes: >> The larger system-design questions are worth considering. If the DNS >> for edge.test.com is adjusted to give higher priority to proxy2, doesn't >> that mean that the administrator *really wants* all new requests to go >> to proxy2 if possible? That would argue against reusing the TLS >> connection simply because its address/port is another target for the DNS >> name. > > That of course is sub-optimal. Do we really want clients maintaining > many connections to the same target, or making/breaking connections > rapidly? (Especially for TLS.) > > If the administrator really wants to move the traffic to a different > server he can always close existing connections.
I think the situation also argues that SRV records should rarely be updated to change the relative priorities of targets just as a load-balancing measure. A better way to use SRV records to dynamically shift load would be to keep the priorities of the targets equal but change the weight values. It's much less of a violation of RFC 2782 to select one target over another target of the same priority because you have a connection open to the first target. Dale _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
