# Five proposals for RIPE Atlas **URL:** \ **Category:** RIPE Atlas\ **Created:** [22 December 2022 11:58 UTC](https://forum.ripe.net/t/five-proposals-for-ripe-atlas/303 "2022-12-22T11:58:40Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![robertk](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.ripe.net/robertk/32/413_2.png) [@robertk](https://forum.ripe.net/u/robertk)\ **Post date:** [22 December 2022 11:58 UTC](https://forum.ripe.net/t/five-proposals-for-ripe-atlas/303/1 "2022-12-22T11:58:40Z")
I published a RIPE Labs article with five proposals for changes to RIPE Atlas. I’m interested to hear what you think. > **[Five Proposals for a Better RIPE Atlas](https://labs.ripe.net/author/kistel/five-proposals-for-a-better-ripe-atlas/)** > > RIPE Atlas is constantly evolving, with the development team changing implementation on a regular basis. When proposed changes relate to behaviour, community input can be very helpful in choosing the best way forward. In this article, we look at... The proposals are to: - Remove per-hop “late” packets from traceroute [LATE-PACKETS] - Measure well-known CDNs [CDN-HTTP] - Generic HTTP measurements [GENERIC-HTTP] - Add support for STARTTLS measurements [STARTTLS] - Remove support for non-public measurements [ONLY-PUBLIC] Pros and cons for each are listed in the article. Comments here or on the RIPE Atlas list ([ripe-atlas@ripe.net](mailto:ripe-atlas@ripe.net)) are welcome. ---
**Author:** ![shavitt](https://avatars.discourse-cdn.com/v4/letter/s/ecccb3/32.png) [@shavitt](https://forum.ripe.net/u/shavitt)\ **Post date:** [23 December 2022 11:41 UTC](https://forum.ripe.net/t/five-proposals-for-ripe-atlas/303/2 "2022-12-23T11:41:54Z")
About late packets. Why not simply report them in the traceroute results, like in this example: ![image](https://europe1.discourse-cdn.com/flex013/uploads/ripe/original/1X/c094a3a3548baf9b3ac893ee8d0ccf4fe571761d.png)