... an overview
2019-07 - Montreal .CA
V0.04
aggregate {
inactive: route 130.129.0.0/16;
route 31.133.128.0/18;
route 31.130.224.0/20;
}
routing-options {
validation {
group rpki-servers {
session 31.130.229.4 { # Dragon Research Labs RPKI Toolkit
preference 100;
port 323;
}
}
policy-statement RPKI {
term whitelist {...}
term invalid {
from {
protocol bgp;
validation-database invalid;
}
then {
validation-state invalid;
community add RPKI_Invalid;
reject;
}
policy-statement RPKI {
term whitelist {
from {
protocol bgp;
prefix-list RPKI_Whitelist;
}
then {
validation-state valid;
community add RPKI_Whitelist;
next policy;
}
}
term invalid {
from {
protocol bgp;
validation-database invalid;
}
then {
validation-state invalid;
community add RPKI_Invalid;
reject;
}
}
term valid {
from {
protocol bgp;
validation-database valid;
}
then {
validation-state valid;
community add RPKI_Valid;
next policy;
}
}
term unknown {
from {
protocol bgp;
validation-database unknown;
}
then {
validation-state unknown;
community add RPKI_Unknown;
next policy;
}
}
/* This should not happen -- things should be valid, invalid or unknown */
term failed {
from protocol bgp;
then {
community add RPKI_Failure;
next policy;
}
}
}
A new switch to a fully provisioned switch in ~15 minutes (including a software upgrade).
Rooms are dynamic - this means we need to reconfigure things often and quickly
IETF participants are "weird"...
... no, really weird...
wkumari$ git push ssh: connect to host git.kumari.net port 22: Connection refused fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. wkumari$
You deserve a kitten now...