[routing-wg] Delay in publishing RPKI objects
- Previous message (by thread): [routing-wg] Delay in publishing RPKI objects
- Next message (by thread): [routing-wg] Delay in publishing RPKI objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Randy Bush
randy at psg.com
Thu Feb 18 01:37:29 CET 2021
> To refresh the stack, can you give me an instance please? > > > then you need to fix operational deployment. > > Thats work-in-progress. We were hoping to move on a process design to > get there, while we finish that deployment. Almost all children NOT in > hosted, are RRDP active. I would be very surprised if the majority > use case now, is not RRDP active. > > > then you can measure the net to be sure everybody is serving rrdp properly. > > That sounds like a fine activity for somebody ELSE to do, to me. see our imc 2020 paper >> but we have had this discussion before. > > Yea, I know, but the problem is we've arrived at needing to boost > resiliency against scale, and rsync is a really poor fit for the > problem because of the fact most CDN choices are tuned for HTTP and > not arbitrary TCP protocols. your emergency due to lack of planning and action does not motivate me randy
- Previous message (by thread): [routing-wg] Delay in publishing RPKI objects
- Next message (by thread): [routing-wg] Delay in publishing RPKI objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]