Authors,
I apologize if this is a repeat of a prior comment I have given as I am
sometimes forgetful.
In your requirements section, you list:
"Monitor extensible RPKI data transport from various sources to routers,
including through RPKI-to-Router Protocol (RTR) [RFC8210
<https://www.rfc-editor.org/info/rfc8210>], BGP [RFC4271
<https://www.rfc-editor.org/info/rfc4271>], or static configurations;"
I believe there is significant good value in monitoring related BGP
state from external interactions like policy and RPKI within BMP. We
are seeing that within the recent TLV and related drafts as part of WG
feedback.
However, I have concerns for the more general requirement that other
protocol states such as RPKI-RTR itself get coverage in BMP. At the
most general level, this eventually turns into pressure for BMP to carry
everything BGP-related. :-)
There is an operational need to monitor the RPKI-RTR itself. You are
likely aware of various efforts to provide YANG modeling for RPKI_RTR
and also related streaming telemetry for state covered by similar
models. I would suggest that the details of the RPKI-RTR protocol
itself should be excluded from your requirements.
-- Jeff
_______________________________________________
GROW mailing list -- [email protected]
To unsubscribe send an email to [email protected]
