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]/
[anti-abuse-wg] Re: Policy proposal: closing allocation/assignment window, was Policy disallowing spam from RIPE blocks
- Previous message (by thread): [anti-abuse-wg] Re: Policy proposal: closing allocation/assignment window, was Policy disallowing spam from RIPE blocks
- Next message (by thread): [anti-abuse-wg] Re: Policy proposal: closing allocation/assignment window, was Policy disallowing spam from RIPE blocks
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Suresh Ramasubramanian
ops.lists at gmail.com
Thu Mar 10 15:31:29 CET 2011
On Thu, Mar 10, 2011 at 7:59 PM, Michele Neylon :: Blacknight <michele at blacknight.ie> wrote: > A LIR should have the technical know-how etc., to manage requests etc., in a cost-effective manner > A lot of the organisations that take PI space probably don't .. PI space normally argues a specific need such as multihoming, or portability across ISPs. Any organization that has the technical knowhow to do this ... Any ISP can allocate a /24 to a customer with a T3 or a rack of servers - but does that space necessarily need to be PI? -- Suresh Ramasubramanian (ops.lists at gmail.com)
- Previous message (by thread): [anti-abuse-wg] Re: Policy proposal: closing allocation/assignment window, was Policy disallowing spam from RIPE blocks
- Next message (by thread): [anti-abuse-wg] Re: Policy proposal: closing allocation/assignment window, was Policy disallowing spam from RIPE blocks
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]