hmm. I'm not sure you're talking about the same thing.
DNS is a rendezvous protocol. I I want to open a session with <foo>,
I translate <foo>'s name to an adddress and open a TCP connection.
Having done so, the application doesn't need either the name or the
address as long as the session is stable. It uses its socket.
Now, if the session takes a hike, there are issues. If you're using
SCTP, those are relatively fixable (draft-ietf-tsvwg-addip-sctp); in
TCP, at least at this point, one closes and reopens the socket with a
new address. What is needed is knowledge of the new address, which in
the internet draft comes from the peer through the socket.
So in SCTP there actually is a solution, and DNS TTLs are not
relevant to the question.
Yes, if the name is retained and not re-translated on a session
failure even though the TTL has expired, that's a problem. It's a
different problem.
On Sep 13, 2007, at 10:43 PM, Tony Finch wrote:
On Thu, 13 Sep 2007, David Conrad wrote:
How do you renumber the IP address stored in the struct
sockaddr_in in a
long running critical application?
Applications that don't respect DNS TTLs are broken for many
reasons, not
just network renumbering.
Tony.
--
f.a.n.finch <dot(_at_)dotat(_dot_)at> http://dotat.at/
IRISH SEA: SOUTHERLY, BACKING NORTHEASTERLY FOR A TIME, 3 OR 4.
SLIGHT OR
MODERATE. SHOWERS. MODERATE OR GOOD, OCCASIONALLY POOR.
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf