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/[email protected]/
[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 ]
Andy Davidson
andy at nosignal.org
Tue Jun 12 23:59:57 CEST 2007
On 12 Jun 2007, at 22:54, Sascha Lenz wrote: > Andy Davidson wrote: >> What if a company wants to try to deploy an anycasted production >> service for something which is not DNS ? It could be a >> proprietary protocol, or something standard like http. Is the >> community view that they should just deaggregate some of their PA >> - which I don't like the sound of - or apply for PI in the normal >> way, and pretend anycast isn't necessarily involved ? > 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. Andy
- 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 ]