Havard Eidnes <Havard.Eidnes@runit.sintef.no> writes: * 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 :-) * * Wow - as ever the pace of decision moves quicker than documentation and configuration. I tend to agree with you here but before we change the database config to make connect optional I guess we should get the okay from the chair who will be coordinating the new definitions for the objects. Also, we can take it a step further in that if the connect field is there it is LOCAL (something to add to the syntax checker ;-(). * - Havard --Tony.