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] An interesting policy question
- Previous message (by thread): [address-policy-wg] An interesting policy question
- Next message (by thread): [address-policy-wg] An interesting policy question
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Lu Heng
h.lu at anytimechinese.com
Thu Dec 3 20:56:04 CET 2015
Hi Gert: I am asking a very specific question to an very specific service example here, the only way to be more specific would be naming people. If you read my last Email, I have tried my best to ask that very specific question. *So the bottom line is, what does *need* mean? Does it means the whole package of justification material(so including everything submitted during the evaluation process for the assignment, including but not limit to the upstream's contract, location of the server, etc), or does it means the *service* was provided, LIR can free justify it's own infrastructure(e.g. move server from DC A to DC B to improve speed) to provide same service to the same customer group?* *Because if *need* includes whole package of justification material, then by definition, change any thing in that package(for example, location of the server, upstream provider), would request NCC approval for the assignment again therefore effectively requested NCC to manage all the infrastructure adjustment by it's members(assure the LIR do not have assignment window), because the need has changed.* Sorry about my English that I can not put it in one sentence, and needed example to help explain, but my question are very very specific and not for the beer time. On Thu, Dec 3, 2015 at 8:51 PM, Gert Doering <gert at space.net> wrote: > Hi, > > On Thu, Dec 03, 2015 at 08:33:22PM +0100, Lu Heng wrote: > > Yes, for old folks here, things seems obvious, but I believe we still > need > > to have next generation people here to participate the discussion, if we > do > > not understand where we ware coming from, how we understand the way to > > develop future? > > I do not think that this is particularily relevant here. The status > "we have plenty of IPv4 but need to ensure fairness between different > ISPs' customers" will not come back - and IPv6 is significantly different > that not much can be learned by IPv4's restrictive policies. > > If you have a specific question, you're welcome to ask. > > But generic "what if... and can you remember the good old times?" stuff > are just noise to most of the participants of the list - so, discuss this > at a beer with others who are interested, but not here. > > > As I have explained in my last Email, understanding of some key element > in > > our past policy will help us going future with our current policy > > development. > > Not in this vagueness. > > Gert Doering > -- APWG chair > -- > have you enabled IPv6 on something today...? > > SpaceNet AG Vorstand: Sebastian v. Bomhard > Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann > D-80807 Muenchen HRB: 136055 (AG Muenchen) > Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 > -- -- Kind regards. Lu -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/address-policy-wg/attachments/20151203/bd7c6b1a/attachment.html>
- Previous message (by thread): [address-policy-wg] An interesting policy question
- Next message (by thread): [address-policy-wg] An interesting policy question
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]