Re: [sidr] NotFound vs Uninitialized

2013-03-14 Thread Andrew Chi
On 3/14/13 5:10 PM, Randy Bush wrote: NotFound: The global RPKI doesn't know this route, i.e., *nobody* knows. nope. a cache can not make such an absolute statement I thought someone might pick on that! I was trying to capture the intuition rather than the definition; apologies for being i

Re: [sidr] NotFound vs Uninitialized

2013-03-14 Thread Randy Bush
> NotFound: The global RPKI doesn't know this route, i.e., *nobody* > knows. nope. a cache can not make such an absolute statement randy ___ sidr mailing list sidr@ietf.org https://www.ietf.org/mailman/listinfo/sidr

Re: [sidr] NotFound vs Uninitialized

2013-03-14 Thread heasley
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

Re: [sidr] NotFound vs Uninitialized

2013-03-14 Thread Jac Kloots
On Thu, 14 Mar 2013, Murphy, Sandra wrote: what will an operator do differently for these two shades of grey? Good question. *Operators*, would you ever treat these differently? I thought Ruediger was saying that the need for this 4th state arose as his company was studying using RPKI.

Re: [sidr] NotFound vs Uninitialized

2013-03-14 Thread 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 t

Re: [sidr] NotFound vs Uninitialized

2013-03-14 Thread Murphy, Sandra
>> what will an operator do differently for these two shades of grey? > >Good question. *Operators*, would you ever treat these differently? I thought Ruediger was saying that the need for this 4th state arose as his company was studying using RPKI. Ruediger, was there a difficulty? a need not

Re: [sidr] NotFound vs Uninitialized

2013-03-14 Thread Andrew Chi
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*

Re: [sidr] NotFound vs Uninitialized

2013-03-14 Thread Borchert, Oliver
I prefer Undefined over Uninitialized and therefore use Undefined below. > > what will an operator do differently for these two shades of grey? > The "Undefined" state is most likely to change shortly after assigned. If processed as "NotFound" and selected but validated as "Invalid" it would h

Re: [sidr] NotFound vs Uninitialized

2013-03-14 Thread Montgomery, Douglas
I remember, and agree with the decision to not try to distinguish among various flavors of INVALID. I think this discussion is different. RFC6811 provides a complete 3 state taxonomy for the result of origin validation, but is based on some assumptions (e.g., reasonable access ("loose consist

Re: [sidr] NotFound vs Uninitialized

2013-03-14 Thread aservin
After talking to Oliver and the comments of Andy I think that it might valuable that fourth state. Trying to respond to Randy I thought that it may be useful to know if a route is unknown (prefix holder does not care about the prefix, i might not trust it) or "undefined" (i lost connectivi

Re: [sidr] NotFound vs Uninitialized

2013-03-14 Thread Randy Bush
what will an operator do differently for these two shades of grey? what is the trust difference? was this perhaps discussed extensively before? what did the security folk tell us in that discussion? randy ___ sidr mailing list sidr@ietf.org https://ww