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 ]
Joao Damas
Joao_Damas at isc.org
Wed Jun 13 09:36:23 CEST 2007
On 13 Jun 2007, at 09:08, Andy Davidson wrote: > > On 12 Jun 2007, at 22:23, Joao Damas wrote: > >>> I think we have a well defined policy on what to do when someone >>> needs some PI in order to run an Anycasted DNS service. We set >>> out a family of requirements based on geographic diversity, for >>> instance, that clearly states what should be in place when a >>> request for PI for DNS use is made. >> They could also state their case in this wg. Sounds far more >> reasonable. > > I disagree; its not reasonable for someone to have to state their > case for why they need resources on a -wg mailing list. A > sponsoring LIR should perform the function of deciding whether an > application is appropriate. Policy is dynamic. If the LIR can't determine whether a request fits current policy or if it doesn't but the LIR would like to evolve policy so that it does, then the discussion needs to take place in the wg. > > I'm simply suggesting that there's a hole in current policy (or is > there ? Does this resource requirement get covered by 'PI needed > to multihome'), that we can look to fill with this real world example. A real world example, needs a real world *specific* example, so provide details of the technical requirements for discussion. Does the proposed use actually work in the real world? Has it been tested, etc? People around here are reasonable. Everyone wants to get their business to work, but the frame for discussion is a technical one, not a marketing one. Joao Damas
- 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 ]