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/ripe-atlas@ripe.net/
[atlas] [mat-wg] RIPE Atlas testing of reserved IPv4 addresses
- Previous message (by thread): [atlas] [mat-wg] RIPE Atlas testing of reserved IPv4 addresses
- Next message (by thread): [atlas] [mat-wg] RIPE Atlas testing of reserved IPv4 addresses
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Avamander
avamander at gmail.com
Tue Feb 16 18:40:16 CET 2021
If we keep in mind the fact that developer time is limited, the decision should boil down to if there are better places to spend the time on. If there are more important measurements, then that time should be spent there instead. That was my point. On Tue, Feb 16, 2021 at 6:41 PM Bengt Gördén <bengan at resilans.se> wrote: > On 2021-02-16 15:55, Avamander wrote: > > some may find it controversial, but I don't think any effort should be > spent > > at extending the life of IPv4. In this case, by extending the address > space. > > I don't agree. This is a measurement tool. Whatever people think about > extending > or not extending the lifetime of ipv4 is irrelevant. It shouldn't hinder > measurements of said networks. If there's networks out there that pass 0/8 > and > 240/4 it's VERY relevant to measure it. Just because you can't see it it > doesn't > mean it's not there. > > > -- > /bengan > > -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ripe-atlas/attachments/20210216/ac4962d4/attachment.html>
- Previous message (by thread): [atlas] [mat-wg] RIPE Atlas testing of reserved IPv4 addresses
- Next message (by thread): [atlas] [mat-wg] RIPE Atlas testing of reserved IPv4 addresses
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]