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] ripe-587, Temporary Internet Number Assignment Policies
- Previous message (by thread): [address-policy-wg] ripe-587, Temporary Internet Number Assignment Policies
- Next message (by thread): [address-policy-wg] ripe-587, Temporary Internet Number Assignment Policies
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Randy Bush
randy at psg.com
Wed Jan 26 18:35:04 CET 2022
>> for a research experiment, we wanted eight or a dozen routable, i.e. >> /24, prefixes which we would announce from various places in the >> topology. each /24 would have one pingable address, let's assume .42. > > This is a tough nut. > > I can totally see what you do, and understand what space you need, and > for which times. > > OTOH, I can totally see the NCC being worried about people claiming > "experiments! and I need a review!" and running their ISP for a year > on temporary space - and with the argument "I want a dozen routable > /24s", you can get quite some ISP work done. the current policy requires description, documentation, ... already. this point merely adds to the spec to allow the ncc to issue frags if a block is not needed. > have you enabled IPv6 on something today...? nope randy
- Previous message (by thread): [address-policy-wg] ripe-587, Temporary Internet Number Assignment Policies
- Next message (by thread): [address-policy-wg] ripe-587, Temporary Internet Number Assignment Policies
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]