Re: [M3UA] Action on Receipt of ERROR

 
> I would say that there has to be a serious protocol feature 
> mismatch (or serious mis-implementation) for every DATA 
> message to elicit an ERROR response.

At a guess it is absolutely easy!
If you connect connect an ASP that conforms to rfc4666 to
an SGP that conforms to rfc3332 in loadshare, then the SGP
doesn't tell the 2nd (and subsequent) ASP the AS state.
This leads to the SGP sending DATA to the ASP in the wrong
state.

I think our code actually processes the data indications
(it routes received data using the routing label info,
without looking at any routing context), however it
won't send reponses.

We have a config option that changes the AS state when we
receive an 'asptm active ack' but haven't already seen
a 'mgmt notify' of the AS state.

	David