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] Re: PI for Not-DNS Anycast.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Galbavy
peter.galbavy at knowtion.net
Wed Jun 13 06:37:34 CEST 2007
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 ? I haven't been doing much in this world for a while, but I think that PI space is still the only thing that fulfills the requirement for organisations who wish to establish VPN (IPsec) connections between themselves (as a non BGP/LIR type company) and others. You cannot use PA space as that is not "yours" and cannot be in anyway guarenteed to be around longer than your contract with your ISP (if that) and 1918 space is no good as the RFC cleary states it is not for this kind of thing. Did anything ever come of "solving" this problem since I last mentioned is around 2001 ? First person who says that renumbering, especially between N independent large corporates is feasible should - and I have said this since the 90s - get off the drugs and enter the real world. Peter
- Previous message (by thread): [address-policy-wg] PI for Not-DNS Anycast.
- Next message (by thread): [address-policy-wg] Re: PI for Not-DNS Anycast.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]