misleading use of the connect: field in inetnum: object

• Previous message (by thread): misleading use of the connect: field in inetnum: object
• Next message (by thread): misleading use of the connect: field in inetnum: object

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Daniel Karrenberg Daniel.Karrenberg at ripe.net
Tue Sep 7 18:58:31 CEST 1993

Wilfried and others,

the real problem with the "connect" attribute is that it still is the
badly defined kludge it has been from the start.  I can say so because I
invented it.  Today we have a well defined and agreed way of specifying
the information you want: It is called ripe-81 by the document fans and
"The Routing Registry" by afficionados.

In my opinion we should put our efforts in getting the RR populated
rather than trying to specify how to use an un-specifyable kludge. 

The original plan was to keep connect alive with the only legal value of
LOCAL.  Maybe we shouldn't even do this. An item for discussion at the RIPE
meeting! 

Daniel

• Previous message (by thread): misleading use of the connect: field in inetnum: object
• Next message (by thread): misleading use of the connect: field in inetnum: object

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]