Re: [Sidrops] version negotiation

[Randy Bush <[e-mail]>]

>>> Now this changes the sematics of Error Code 4.  So Section 13 needs
>>> to be adjusted. Error code 4 should not be fatal but have special
>>> handling as described in Section 7. This is required because:
>>>    Errors which are considered fatal MUST cause the session to be
>>>    dropped, and the router MUST flush all data learned from that
>>>    cache.
>> 
>> i am less sure of this.  note that is the session which must be
>> dropped, not the transport.  and the session has not yet even been
>> established if we're still negotiating versions.
> 
> I pondered more about this. I think your reason of "the session is not
> yet established" does not matter here. What if the transport
> connection was lost but the session and cache is all fine. When the
> router starts a new connection and therefor MUST do the version
> negotiation. The moment an Code 4 error pdu is received the RTR MUST
> drop the database since Code 4 is a fatal error (it does not matter
> that the session is not yet up).
> 
> Because of this interaction between various MUST in the draft it is
> IMO necessary to make Error Code 4 non-fatal.

agree.  thanks.

i am about to push -12 with, i hope, all suggestions/corrections
addressed.

except i have left the ASPA AFI flags in for the moment; though making
clear in the document that they are likely to be removed.  i am still
ambivalent on this one, am waiting on alexander the ASPA architect, and
i may have some new data by the meeting.  yes, i think i know most
folk's opnions on this one; no need to repeat if your opinion has not
changed.  patience is a virtue, and the ASPA docs are still in flux so
nothing is final.

randy