Re: [Idr] I-D Action:draft-ietf-idr-advisory-00.txt

["Ilya Varlashkin" <Ilya.Varlashkin at de.easynet.net>]

Hello,

> This document proposes a new BGP message type, the Advisory 
> message, which can be used to convey advisory information to 
> a BGP speaker's peer.  A capability is used to ensure that 

The document proposes two sub-types (1&2) which appear to be very
similar in format but somewhat different in expected reaction of the
router. Is there sufficient need to separate on protocol level such
messages? From operator prospective I see value in making any message
visible among other neighbor-related information (in some sort of 'show'
command output) and any message may generate notification to caretaker
(e.g. via syslog or snmp trap). Could both sub-types be combined into
one and left upto operator to decide whether to log/trap them or not?

As for "standard set of advisory messages", it's probably good idea to
document them in a separate draft/rfc rather than leaving it up to
implementations to come up each with their own set of "standard
messages". The list could be settled by asking network operators to
submit their proposals, then have vendors say what's feasible or not.
Such list should not be too long, but should cover most typical
scenarios where advisory messages would be helpful.

Cheers,
iLya