RFC and Dynamic Reconnection

This protocol is complex; it proliferates control messages; it causes queues (to become associated with re-entrant procedures) that are artificially imposed via the protocol (remote AEN assignment); and discounts the situation where only controlling process "A" has knowledge that slave process "B" should be "rung out" in a dynamic reconnection.

The <ERR>, etc., are suggestions for inclusion as additions in the April 28th protocol specifications. The above criticism is, of course, not intended to affect modification of the RFC structure by April 28th, nor to reflect on those who planned it. We have not studied the problem. It is meant, however, to voice our concern about complexity and resulting response times. This is a difficult problem and it deserves more study after we have exercised the current RFC specifications. We hope to offer constructive suggestions with respect to the RFC in the future.

JFH:hs

---

Note: This RFC was put into machine readable form for entry into the online RFC archives by Mario Vitale 08/99.