IPv4 routing is not designed to use Anycast optimally, but it can significantly leverage the infrastructure for some applications. Anycast usage is at this moment limited to mostly short (onerequest-one-reply packet), connectionless exchanges of information. Domain Name Service (DNS) is a very good example. The exchange with DNS only takes two User Datagram Protocol (UDP) packages: request and answer. The next request can be sent to another server without any problem. No exchange of state is necessary. Some other good uses for Anycast are Network Time Protocol (NTP), Syslog (traps sent by devices to a management system), Rendezvous Point (RP) information in Protocol Independent Multicast Sparse Mode (PIM-SM) and export of flow information.
Transmission Control Protocol (TCP) needs complicated state-change mechanisms to make Anycast work. TCP was not designed to handle these state-change mechanisms, and is therefore, less suitable for use of Anycast.
Refer to: https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.116.6367&rep=rep1&type=pdf
Hope this help.
View more
x
convention:
Herediano
Created Oct 25, 2020 15:55:02 (0)(0) Thank you @DragonVN, that is pretty much what I was looking for.
IPv4 routing is not designed to use Anycast optimally, but it can significantly leverage the infrastructure for some applications. Anycast usage is at this moment limited to mostly short (onerequest-one-reply packet), connectionless exchanges of information. Domain Name Service (DNS) is a very good example. The exchange with DNS only takes two User Datagram Protocol (UDP) packages: request and answer. The next request can be sent to another server without any problem. No exchange of state is necessary. Some other good uses for Anycast are Network Time Protocol (NTP), Syslog (traps sent by devices to a management system), Rendezvous Point (RP) information in Protocol Independent Multicast Sparse Mode (PIM-SM) and export of flow information.
Transmission Control Protocol (TCP) needs complicated state-change mechanisms to make Anycast work. TCP was not designed to handle these state-change mechanisms, and is therefore, less suitable for use of Anycast.
Refer to: https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.116.6367&rep=rep1&type=pdf
Hope this help.
View more
x
convention:
Herediano
Created Oct 25, 2020 15:55:02 (0)(0) Thank you @DragonVN, that is pretty much what I was looking for.
Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
Politically sensitive content
Content concerning pornography, gambling, and drug abuse
Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."