Friends, after all the useful input from you and some more thought we have concluded that introducing the RIPE handles this year is too ambitious. So it will be January. I see two alternatives: 1) We wait until the RIPE meeting in order to discuss all the possibilities and make a firm decision. This delays introduction well into February. Database exchange with the InterNIC is also delayed until then. 2) We introduce like planned in the first week(s) of January. In order to address concerns quick and easy assignment we will operate a server for real-time assignments. If this does not solve the expected problems we can decide about local assignements at the RIPE meeting. In order not to delay database exchange with the NIC we favour option 2. About the real-time server: It will run on a special TCP port accessible only to local IRs. The server will accept a person object with "nic-hdl: assign" and immediately echo back the person object with the NIC handle or an error message. We will provide a filter "assignhandle" to go with it so you can integrate it into your own software (we will often run it in vi/emacs). We will also provide the filter mentioned in the paper which adds handles to an existing database without handles. Does anyone have real problems with option 2? Daniel
I see two alternatives: About the real-time server: It will run on a special TCP port accessible only to local IRs. The server will accept a person object with "nic-hdl: assign" and immediately echo back the person object with the NIC handle or an error message. Perfect. Does anyone have real problems with option 2? Nope, but the very first week in January may well be very hectic for a lot of people, so I'd suggest to start no earlier than the second week. Piet
Daniel Karrenberg writes:
Friends,
after all the useful input from you and some more thought we have concluded that introducing the RIPE handles this year is too ambitious.
So it will be January.
I see two alternatives:
1) We wait until the RIPE meeting in order to discuss all the possibilities and make a firm decision. This delays introduction well into February. Database exchange with the InterNIC is also delayed until then.
2) We introduce like planned in the first week(s) of January. In order to address concerns quick and easy assignment we will operate a server for real-time assignments. If this does not solve the expected problems we can decide about local assignements at the RIPE meeting.
In order not to delay database exchange with the NIC we favour option 2.
About the real-time server: It will run on a special TCP port accessible only to local IRs. The server will accept a person object with "nic-hdl: assign" and immediately echo back the person object with the NIC handle or an error message. We will provide a filter "assignhandle" to go with it so you can integrate it into your own software (we will often run it in vi/emacs).
We will also provide the filter mentioned in the paper which adds handles to an existing database without handles.
Does anyone have real problems with option 2?
Daniel
With the above proposed server and tools I see option 2 as a feasible approach. Thank you Daniel! ---------- ---------- Antonio_Blasco Bonito E-Mail: bonito@nis.garr.it GARR - Network Information Service c=it;a=garr;p=garr;o=nis;s=bonito c/o CNUCE - Istituto del CNR Tel: +39 (50) 593246 Via S. Maria, 36 Telex: 500371 CNUCE I 56126 PISA Italy Fax: +39 (50) 904052 ---------- ----------
Option 2 looks fine to me, Daniel. At the same time, could we have some discussion of this service at the January meeting? Cheers. Mike
"Mike Norris" <mnorris@dalkey.hea.ie> writes:
Option 2 looks fine to me, Daniel. At the same time, could we have some discussion of this service at the January meeting?
Of course that is the intention. Daniel PS: Thanks for the new Limerick
participants (4)
-
bonito＠nis.garr.it -
Daniel Karrenberg -
Mike Norris -
Piet.Beertema＠EU.net