[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Idr] draft-scholl-idr-advisory



In message <21ef2c1c0907021108i75f70ee8we558325d4b8de22f at mail.gmail.com>
vijay gill writes:
[trimmed]
> >
> > I'm most likely not the best advocate for this draft since I'm somewhat lukewarm
> > about its benefit given the cost. However, allow me to bring up and analogy
> > with all the usual caveats inherent in anaologies. CLNS host info doesn't by
> > itself amount to much, but has shown itself to be of many time saving operational
> > uses. So to that extent, some facilities for having a limited free form text
> > to syslog command tied to BGP may be of more use than we can think of at the moment.
>  
> I disagree strongly with the operational reality of this draft. It may
> be useful for some folks who have the time to actually sync up and
> talk with another person on the far side of an _already_ operational
> BGP session. That corner case is not common enough to actually make
> this useful in my opinion. The real utility might be if the session
> was not established and in that case we fall back to OOB communication
> anyway.
>  
> /vijay
> >
> > -dorian

Vijay,

If you can get past the open exchange then a message can be sent and
logged before the first update and with a "btw- I think the reason this
session is flapping all day is ...".  If the IP address is wrong or
authentication fails or the session does not establish at all for some
other reason, then its a no go.

It does sound to me to be useful.  Since it can't pollute anything but
the syslogs, it also seems harmless.

Curtis