Thu, Mar 14, 2013 at 02:02:13PM -0400, Montgomery, Douglas: > Not an ops person - so take with a grain of salt - but imagine a world N > years from now where I only accept routes that have VALID origins. All > others routes are dropped. > > Imagine a net/power/nature event that both reboots my routers and all of the > caches that I speak too. If may prefer to reboot the routing system without > validation, until enough infrastructure is up to begin validation.
or your validation server is remote - within a prefix that will not be accepted because it is NotFound/Undefined? > dougm > -- > Doug Montgomery - Manager Internet and Scalable Systems Research Group / ITL > / NIST > ________________________________________ > From: [email protected] [[email protected]] On Behalf Of Andrew Chi > [[email protected]] > Sent: Thursday, March 14, 2013 1:16 PM > To: [email protected] > Subject: Re: [sidr] NotFound vs Uninitialized > > On 3/14/13 6:55 AM, Randy Bush wrote: > > what will an operator do differently for these two shades of grey? > > Good question. *Operators*, would you ever treat these differently? > > > what is the trust difference? > > NotFound: The global RPKI doesn't know this route, i.e., *nobody* knows. > Undefined: *I* don't know what the RPKI says about this route. > _______________________________________________ > sidr mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/sidr > _______________________________________________ > sidr mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/sidr _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
