SPONSELL@AKRONVM.BITNET (Gary Sponseller) (02/28/90)
>> The mid-month release of a routing-table update, by the way, was >>discussed on this list prior to its occurrence and is consistent with >>last year's practice, also discussed on this list. >Correct, it was discussed on this list, but since the TECHREP/INFOREP/BIRREP >list were not operational then most people on this network do not know >what is going on. Additionally, I would like to re-iterate, once again, >my request that node contacts (the :contact tag) be included on the >TECHREP list or that the TECHREP list be renamed to NAD or some such >beast -- CONTACTs must know the same things a TECHREP knows. > >/mrg I think that the NADs are left out... They really have no list at all. NADS-L (or BIT-NADS or CONTACT-L) does not exist. The :contact. tag is there and denotes the NAD for each node. It appears that we have (at least) four authorized people per node: BIRREP, TECHREP, INFOREP and NAD. I really believed (maybe naively?) that as the respective tags in BITEARN NODES changed, so did the subscriptions to these lists -- except there is no NAD list. (Our subscriptions have been in the 3 current lists, correctly, for a long time.) Maintaining these could (should?) be part of UPDATE@BITNIC's function. It may be confusing to have both NADs and TECHREPs on the TECHREP list (someone is both and drops only one role, NAD may not be a technical person at all, etc.) But certainly there should be information going to NADs and certainly these lists must be up-to-date so every gets informed of the constant changes Bitnet and related networks are going through...