On 13/11/2008, at 11:16 AM, John G. Scudder wrote:
GROW folks,
I'll be presenting draft-scudder-bmp-01 ("BGP Monitoring Protocol")
at the meeting in Minneapolis. Long-time GROW fans may remember
that the WG requested to make the -00 version a WG document way back
in 2005. It turned out that there were some major implementation
hurdles with the draft as written and it became moribund and never
did get issued as draft-ietf-grow.
Fast forward to present, there's been significant renewed interest
so we've dusted off the draft and modified the mechanism to make it
more implementor-friendly. I'm hoping that the WG would still,
after the long hiatus, like to adopt the draft.
Since I missed the submission cutoff, a copy of the draft is
attached for those who'd like to (please!) look at it before the
meeting. Your comments are welcome before, during or after the
meeting.
AS the then-chair of the GROW WG that was requesting submission of
this draft as a WG document way back then, I'm really glad to see that
its finally seeing the light of day once more as its a potentially
very useful BGP monitoring tool. So I support this draft being adopted
as a WG document - its a potentially very useful mechanism.
I'm a little confused however by some of the details. It appears that
BMP is a method to tap into a peer session and the local BGP speaker
can be configured to send a copy of all received updates from a BGP
peer to a monitor point using BMP, including the time when these
updates were received by the local BGP speaker.
However in section 3 the text states: "If there are state changes in
the interim for that prefix, it is acceptable that the router generate
the final state of that prefix to the monitoring station. "
What I'm confused about is: what timestamp should be used in such a
case? And does this "final state" reflect the final state in the
logical Adj-RIB-In for this BGP peer, or the final state according to
the local Loc-RIB?
thanks,
Geoff
_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow
