This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/address-policy-wg@ripe.net/
[address-policy-wg] PI for Not-DNS Anycast.
- Previous message (by thread): [address-policy-wg] PI for Not-DNS Anycast.
- Next message (by thread): [address-policy-wg] PI for Not-DNS Anycast.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
s.steffann at computel.nl
Wed Jun 13 10:42:30 CEST 2007
Hi Andy, > > The problem is, noone came up with some concrete idea what that > > might be. You obviously don't have an idea about some concrete > > example either. > > Actually my customer wants to try to anycast streaming audio media. > It seems to work in the lab, We want to deploy in the wild now. Can you give more details of how this works with anycast? I am interested in examples of non-DNS anycast applications. In the past there have been questions about which protocols/applications other than DNS can benefit from anycasting, and you seem to be the first with a concrete example. Thanks, Sander.
- Previous message (by thread): [address-policy-wg] PI for Not-DNS Anycast.
- Next message (by thread): [address-policy-wg] PI for Not-DNS Anycast.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]