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]/
[db-wg] Re: [address-policy-wg] Draft: "status:" re-evaluation
- Previous message (by thread): [db-wg] Re: [address-policy-wg] Draft: "status:" re-evaluation
- Next message (by thread): [db-wg] Re: [address-policy-wg] Draft: "status:" re-evaluation
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sebastian Abt
sabt at sabt.net
Wed Aug 13 19:05:43 CEST 2003
Hi, * Gert Doering <gert at space.net> wrote: > It's their suballocation, and their customer, not mine - how can I > judge how big *their* customer is going to be, and how much address > space they want? You won't judge. You give your customer's customer the allocation he needs (and the one that fits into your assignment window - or "sub- allocation window") as well as you give your customer the allocation he needs. > The whole point of suballocation is "give control to the people that > actually hand out the addresses" - flexibility, instead of buerocracy. Of course, and indeed, that's a "nice to have", but who controls the customer's customer assignments? In the end you're responsible for everything they do, because you are the one RIPE is going to contact in case of any trouble (at least that's what I'm reading in the draft). Erm, and what an assignment window do they have (or "sub-allocation window")? That are the questions confusing me. regards, sebastian -- whois: sabt-ripe - phone: +49 (0)174 3420738 email: sabt at sabt.net - pgp-pubkey: 0x3B046B48
- Previous message (by thread): [db-wg] Re: [address-policy-wg] Draft: "status:" re-evaluation
- Next message (by thread): [db-wg] Re: [address-policy-wg] Draft: "status:" re-evaluation
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]