[routing-wg] 2019-08 Review Phase (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
- Previous message (by thread): [routing-wg] 2019-08 Review Phase (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
- Next message (by thread): [routing-wg] 2019-08 Review Phase (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Rohit travels & tours
rtat1981 at gmail.com
Sun Feb 23 16:01:05 CET 2020
Hi On Sun, Feb 23, 2020, 9:17 AM Jared Mauch <jared at puck.nether.net> wrote: > > > > On Feb 23, 2020, at 8:45 AM, Nick Hilliard <nick at foobar.org> wrote: > > > > JORDI PALET MARTINEZ via routing-wg wrote on 23/02/2020 13:06: > >> I don't think is objective to say that the proposal as asking the NCC > >> to "inject" invalids. > >> The proposal is providing the information of the invalids (in this > >> case unallocated/unassigned) by means of RPKI. > > > > Jordi, > > > > You're splitting hairs here. The end result is the same. > > I’m cornered about something like this as we’ve been down this road before > with bogon lists, etc and even though it’s well intentioned by smart > people(tm), the distributed legacy and cleanup has often taken years to > recover. > > - Jared > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ripe.net/ripe/mail/archives/routing-wg/attachments/20200223/a714f17e/attachment-0001.html>
- Previous message (by thread): [routing-wg] 2019-08 Review Phase (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
- Next message (by thread): [routing-wg] 2019-08 Review Phase (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]