Obsoleting "connect"

Hi,

if my memory serves me well, I think the RIPE DB working group concluded to
restrict the legal values for the "connect" field to only "LOCAL", and if
wider connectivity for a net has been established to not use this attribute
in the objects in the database.

However, this is somewhat at odds with the current definition of the
connect field in the inetnum template, where the attribute is mandatory.
So what do you put in an object which has wider connectivity than internal
to the "home" autonomous system?

My proposal to progress this decision (as mentioned at the end of the RIPE
meeting) is thus to initially demote the "connect" attribute from mandatory
to optional, and later add stricter checks in the RIPE database software
for the values of the connect attribute.  Currently updates missing the
connect field are being bounced (I know, I tried it while I was at the RIPE
meeting :-)


- Havard