asXXX at ra.net & NIC Technical Contact Registrations

Andrew,

> You really need 2 different lists - one of folks authorized to make
> changes & the other of who should get email.

You're right.  The main question is how to map this onto RIPE-181;  the
second question is how to interface this with the InterNic.  Because of
the confusion about those, we haven't promoted those lists much yet.

As you noticed, for the moment (sort of as an experiment) we're just
taking the MAIL-FROM lines from the maintainer objects, and making those
into "asXXX at ra.net" lists.  This is going to break badly as soon as we
stop accepting NACRs, since lots of security-conscious ASs will immediately 
remove all MAIL-FROM lines from their maintainer objects and will replace
them with CRYPT-PW or PGP;  at that point our "asXXX" lists have nothing
in them.

In the long run, we should use the Internic's AS contact information for
this.  In the short run, that information isn't very accurate or useful.

There might be some combination of information from the RIPE objects
that would be a good source of data for these lists:  e.g. pick all the 
tech-c: NIC handles from the AS objects, and put those people in the
asXXX mail lists.  But how do we seed thoses lists?  Maybe something like
ask the Internic to take the NSFNET contact lists, and to insert those
names into the NIC AS contacts registrations?

Thoughts?

--Dale


> From asp at uunet.uu.net Fri Mar 17 11:49:08 1995
> Subject: asXXX at ra.net
> To: bmanning at ISI.EDU
> 
> I was checking out some of the asXXX at ra.net (or some such) lists.
> 
> You seem to be using the same list as those folks that are authorized
> to submit changes.
> 
> You really need 2 different lists - one of folks authorized to make
> changes & the other of who should get email.



-------- Logged at  Tue Mar 21 18:14:05 MET 1995  ---------