Hi,
Before all, thanks for clarifying the anycast subject !
For TCP connections, or UDP with suspicious clients, it seems to me the
pb is quiet the same as for mobile node acces, hence why not use the
same solution ?
The anycast server (who knows it owns an anycats @) can play the role of
a mobile, using its anycats @ as Home-@, and one of its current @ as
Co@. By using the Home Address option the UDP client won't know the
difference, and if necessary (for TCP), it can also send Binding Update
options, to be sure to be the one and onlmy server speaking with this
client.
Then the client would not have to know wether the @ its using is anycast
or not.
Does it make sense or did I miss something ?
Best regards.
Alain.
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
