Hi Bert,
Many thx for your comment .. I was not able to stay at the IETF till the
SIDR session.
If that is the case the draft-ymbk-bgp-origin-validation-mib is just
completely not ready for adoption until it contains bare minimum which
will allow operators to use it.
It would be insane to list 1 million of valid prefixes as opposed to
little fraction of them being in question. Whoever authored that draft
needs to develop a bit more real network operational experience :)
Best regards,
R.
During the discussion at the SIDR WG session at IETF81 we
found that the bgpVRTValid attribute in that table makes no
sense, because we do not have that info. These are ALL
validated ROAs (or better validated prefixes) as I understand
it.
Bert
On 8/5/11 8:09 AM, Robert Raszuk wrote:
Hi,
Just looking at draft-ymbk-bgp-origin-validation-mib may I ask what
would be the root OID string to start SNMP tree walk (or set the trap)
to list all INVALID or NOT_FOUND BGP entries ?
Rgs,
R.
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr
